Topic: Problems joining domain from other subnets

[n0lqu]

Running SME Server 6.5 on a network with several router-connected networks.  We can join Windows XP clients to the domain when they are on the same physical network as the server, however clients on other subnets get:

The following error occurred attempting to join the domain "DOMNAME":

The specified domain either does not exist or could not be contacted.

If we temporarily switch a client to the same subnet as the server, we can join the domain without problems, and then after switching it back to its proper subnet and IP address everything works, people can sign on to the network, access resources, etc.  So it's only the domain joining piece that's not working.

What is happening during the "join domain" process that is not finding our domain server and what can I do to assist it?

Things I've tried include:

* An LMHOSTS file on the client computer (

c:\windows\system32\drivers\etc\lmhosts) with a line like:

Code: [Select]

192.168.2.4 domserver1 #PRE #DOM:DOMNAME[/list]

* We're running a separate DNS server rather than the one in SME and I've added the following lines to it:

Code: [Select]

domserver1                     A            192.168.2.4
_ldap._tcp.pdc._msdcs.DOMNAME. SRV  0 0 389 domserver1
_ldap._tcp.dc._msdcs.DOMNAME.  SRV  0 0 389 domserver1
_ldap._tcp.DOMNAME.            SRV  0 0 389 domserver1
[/list]
Any help from someone more familiar with what's supposed to happen on where to look to see why it's not happening would be appreciated!

[Franco]

You seem to be having different issues here, one being the routing and the other the fact that you're using a different DNS.
I had the same situation when using different subnets and the way I got around was to create an aliases of the eth0 card and set my clients on this second subnet to use this second IP as gateway. This resolved my problem, but I'm not sure about the different DNS.

[n0lqu]

You seem to be having different issues here, one being the routing and the other the fact that you're using a different DNS.
I had the same situation when using different subnets and the way I got around was to create an aliases of the eth0 card and set my clients on this second subnet to use this second IP as gateway. This resolved my problem, but I'm not sure about the different DNS.

I don't know that I have any routing problems -- everything works once we get past the Joining the Domain problem.  Using a different DNS could well be the reason, however, so the question is how can I find out for sure what piece of the communication process isn't working and how do I fix our get around it?  Do I need to add some other entries to the DNS, or are there settings on the XP client side to assist in getting the domain joining to work?

Thanks for your post, hopefully you or someone else will have some additional ideas!

[Franco]

When you create a new subnet do the firewall rules apply to them? That's what I mean by the routing problem, and that's why I mentioned the IP aliases. One other thing, on the client XP I'm used to "Enable Netbios over TCP/IP".