Hi –
I have just changed my PDC from Ubuntu to SuSE and am having a problem that I also had with Ubuntu and can’t remember the solution.
My PDC works fine – in part. Shares appear, etc. However workstations cannot join the domain. I get the message that a suitable Active Directory Domain Controller can’t be found. Not surprising – I set up the PDC as a SAMBA PDC, not as an Active Directory controller.
Does anybody know the workaround either to get windows to recognize that I’m looking for a SAMBA PDC, not an AD DC or to set up the PDC as an AD DC?
Thanks for your help.
On Thu May 6 2010 10:16 am, peteclapham wrote:
>
> Hi –
>
> I have just changed my PDC from Ubuntu to SuSE and am having a problem
> that I also had with Ubuntu and can’t remember the solution.
>
> My PDC works fine – in part. Shares appear, etc. However
> workstations cannot join the domain. I get the message that a suitable
> Active Directory Domain Controller can’t be found. Not surprising – I
> set up the PDC as a SAMBA PDC, not as an Active Directory controller.
>
> Does anybody know the workaround either to get windows to recognize
> that I’m looking for a SAMBA PDC, not an AD DC or to set up the PDC as
> an AD DC?
>
> Thanks for your help.
>
petechapham;
What flavor(s) of Windows is(are) being run on the clients?
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Running Windows-7. There are two registry changes that have to be made in Windows in order to connect, and they’ve been made. The Windows side of the system worked with Ubuntu, but not with SuSE.
I suspect that I either have to initiate DNS or WINS on the Primary Domain Controller (which I’d rather not do) to register the domain name as a Netbios name, but that might not be the problem.
A related (I think) problem. I have two other servers in the system, one of which has been running OpenSuSE for some time, the other of which I changed when I moved from Ubuntu to OpenSuSE last week. When I try to access a share on either I get the message that “There are currently no logon servers to service the logon request.” This despite the fact that one of the servers worked fine with Ubuntu.
Indeed, when I go to the Samba Server icon in YaST the machine is clearly labeled a PDC, but it is not a member of the domain and won’t connect to it.
On Mon May 10 2010 09:46 am, peteclapham wrote:
>
> A related (I think) problem. I have two other servers in the system,
> one of which has been running OpenSuSE for some time, the other of which
> I changed when I moved from Ubuntu to OpenSuSE last week. When I try to
> access a share on either I get the message that “There are currently no
> logon servers to service the logon request.” This despite the fact that
> one of the servers worked fine with Ubuntu.
>
> Indeed, when I go to the Samba Server icon in YaST the machine is
> clearly labeled a PDC, but it is not a member of the domain and won’t
> connect to it.
>
peteclapham;
I assume you have followed this link:
http://wiki.samba.org/index.php/Windows7
There are a number of erroneous suggestions on the Web. The above should be
definitive.
Since you imply that this is an existent domain, did you preserve the domain
SID when you changed the PDC from Ubuntu to OpenSuse? You should check your
domain SID on all the Linux machines with the command:
net getdomainsid
The PDC and member servers/BDCs should all have the same Domain SID. You might
want to check. We have always joined the PDC with the net command. It might
help to look at “man net” for the facilities it provides for SIDs and Domain
membership.
It might help if you posted the contents of the [global] section of
your /etc/samba/smb.conf; sans any sensitive data such as public IPs or
domain names. (use substitute values)
If you have more than one subnet, WINS or DNS is required. You can dish out
the WINS server’s IP with dhcpd.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Thanks to venzkep for his suggestions. I found the answer, however, and it is very different from what I would have thought – and it gives some pause to people changing from one distro to another.
The problem was a firewall configuration problem. Having used several distributions of Linux, as well as Solaris, OS/2, and various versions of Windows, I had never run into a NetBIOS server. All of the systems used NetBIOS for the sort of network I’m running, and it was just there. Evidently with SuSE there is a NetBIOS server, and one has to open the port in the firewall to serve it. Once I discovered that, it appears to work fine. 
On Wed May 12 2010 09:26 am, peteclapham wrote:
>
> Thanks to venzkep for his suggestions. I found the answer, however, and
> it is very different from what I would have thought – and it gives some
> pause to people changing from one distro to another.
>
> The problem was a firewall configuration problem. Having used several
> distributions of Linux, as well as Solaris, OS/2, and various versions
> of Windows, I had never run into a NetBIOS server. All of the systems
> used NetBIOS for the sort of network I’m running, and it was just there.
> Evidently with SuSE there is a NetBIOS server, and one has to open the
> port in the firewall to serve it. Once I discovered that, it appears to
> work fine.
>
peteclapham;
Glad you got it sorted out. Soon after my last post I thought that I should
have mentioned the firewall issue. Sorry I didn’t tumble to it sooner.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
These are the ports that probably should be open on the PDC
Check these
88 UDP
389 UDP
464 UDP
464 TCP
On Thu May 13 2010 01:06 am, Mr Squiggle wrote:
>
> These are the ports that probably should be open on the PDC
> Check these
> 88 UDP
> 389 UDP
> 464 UDP
> 464 TCP
>
>
Huh!
The following ports are used:
TCP: 135,139 & 445 used by smbd
UDP: 137 & 138 used by nmbd
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
On Thu May 13 2010 05:33 pm, PV wrote:
> On Thu May 13 2010 01:06 am, Mr Squiggle wrote:
>
>>
>> These are the ports that probably should be open on the PDC
>> Check these
>> 88 UDP
>> 389 UDP
>> 464 UDP
>> 464 TCP
>>
>>
> Huh!
>
> The following ports are used:
>
> TCP: 135,139 & 445 used by smbd
> UDP: 137 & 138 used by nmbd
>
> See:
>
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/securing-samba.html#firewallports
Addenda:
The ports mentioned by Mr. squiggle are only needed on the ldap server with
kerberos.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
That’s why I deleted the post within a few minutes after posting.
I was heading toward a firewall issue and then reread the post and realised your configuration was not relevant to my post and deleted.
The firewall assumption was correct just not the ports.
On Thu May 13 2010 07:36 pm, Mr Squiggle wrote:
>
> That’s why I deleted the post within a few minutes after posting.
> I was heading toward a firewall issue and then reread the post and
> realised your configuration was not relevant to my post and deleted.
>
> The firewall assumption was correct just not the ports.
>
>
Mr. Squiggle;
Once a post makes it to the nntp server, the nntp users see it regardless of
edits or deletes. Chalk this up to the problems involved in allowing edits on
the web side. My apologies.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green