Joining Domain on a different Subnet

[shertz]

Hi,

I'm using Enteo to depoy Windows XP to our client computers. In the last weeks, we changed our network design and now I'm unable run unattended Windows XP installations. He is does not join the domain. According to this article I already edited the lmhosts.sam-file (respectively lmhosts.sa_). After that, I'm able to join the domain manually, but he still don't do this during unattended install. When I assign an IP-address from the same subnet to the client, everything is working fine. Is it possible, that during unnatedned installation of Windows XP the entrys in lmhosts are ignored. Is there any (better) way to let the client know about the domain controller?

Example configuration:

PDC: 10.0.90.20 (Hostname: XXS020)

Client: 10.1.71.190 (DHCP)

Domain: XX.com

lmhosts.sam:

10.0.90.20 XXS020 #PRE #DOM:XX.com
10.0.90.20 "XX.com		 \0x1b" #PRE

Edit:

I'll attach the content of the NetSetup.log, but it just says NO_SUCH_DOMAIN (it's the 0x54b):

11/27 15:00:12 -----------------------------------------------------------------
11/27 15:00:12 NetpValidateName: checking to see if 'ARBEITSGRUPPE' is valid as type 2 name
11/27 15:00:12 NetpCheckNetBiosNameNotInUse: for 'ARBEITSGRUPPE' returned: 0x858
11/27 15:00:12 NetpCheckNetBiosNameNotInUse for 'ARBEITSGRUPPE' [ Workgroup as MACHINE]  returned 0x858
11/27 15:00:12 NetpValidateName: name 'ARBEITSGRUPPE' is valid for type 2
11/27 15:00:12 -----------------------------------------------------------------
11/27 15:00:12 NetpValidateName: checking to see if 'ARBEITSGRUPPE' is valid as type 2 name
11/27 15:00:12 NetpCheckNetBiosNameNotInUse: for 'ARBEITSGRUPPE' returned: 0x858
11/27 15:00:12 NetpCheckNetBiosNameNotInUse for 'ARBEITSGRUPPE' [ Workgroup as MACHINE]  returned 0x858
11/27 15:00:12 NetpValidateName: name 'ARBEITSGRUPPE' is valid for type 2
11/27 15:00:13 -----------------------------------------------------------------
11/27 15:00:13 NetpValidateName: checking to see if 'ARBEITSGRUPPE' is valid as type 2 name
11/27 15:00:13 NetpCheckNetBiosNameNotInUse: for 'ARBEITSGRUPPE' returned: 0x858
11/27 15:00:13 NetpCheckNetBiosNameNotInUse for 'ARBEITSGRUPPE' [ Workgroup as MACHINE]  returned 0x858
11/27 15:00:13 NetpValidateName: name 'ARBEITSGRUPPE' is valid for type 2
11/27 15:00:13 -----------------------------------------------------------------
11/27 15:00:13 NetpDoDomainJoin
11/27 15:00:13 NetpMachineValidToJoin: 'XX9650M'
11/27 15:00:13 NetpGetLsaPrimaryDomain: status: 0x0
11/27 15:00:13 NetpMachineValidToJoin: status: 0x0
11/27 15:00:13 NetpJoinWorkgroup: joining computer 'XX9650M' to workgroup 'ARBEITSGRUPPE'
11/27 15:00:13 NetpValidateName: checking to see if 'ARBEITSGRUPPE' is valid as type 2 name
11/27 15:00:13 NetpCheckNetBiosNameNotInUse: for 'ARBEITSGRUPPE' returned: 0x858
11/27 15:00:13 NetpCheckNetBiosNameNotInUse for 'ARBEITSGRUPPE' [ Workgroup as MACHINE]  returned 0x858
11/27 15:00:13 NetpValidateName: name 'ARBEITSGRUPPE' is valid for type 2
11/27 15:00:13 NetpSetLsaPrimaryDomain: for 'ARBEITSGRUPPE' status: 0x0
11/27 15:00:13 NetpControlServices: open service 'NETLOGON' failed: 0x424
11/27 15:00:13 NetpJoinWorkgroup: status:  0x0
11/27 15:00:13 NetpDoDomainJoin: status: 0x0
11/27 15:01:04 -----------------------------------------------------------------
11/27 15:01:04 NetpValidateName: checking to see if 'XX9650M' is valid as type 1 name
11/27 15:01:07 NetpCheckNetBiosNameNotInUse for 'XX9650M' [MACHINE] returned 0x0
11/27 15:01:07 NetpValidateName: name 'XX9650M' is valid for type 1
11/27 15:01:23 -----------------------------------------------------------------
11/27 15:01:23 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:01:26 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:01:26 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:01:36 -----------------------------------------------------------------
11/27 15:01:36 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:01:38 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:01:38 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:01:48 -----------------------------------------------------------------
11/27 15:01:48 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:01:50 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:01:50 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:02:00 -----------------------------------------------------------------
11/27 15:02:00 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:02:02 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:02:02 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:02:13 -----------------------------------------------------------------
11/27 15:02:13 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:02:15 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:02:15 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:02:25 -----------------------------------------------------------------
11/27 15:02:25 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:02:27 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:02:27 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:02:37 -----------------------------------------------------------------
11/27 15:02:37 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:02:39 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:02:39 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
11/27 15:02:49 -----------------------------------------------------------------
11/27 15:02:49 NetpValidateName: checking to see if 'xx' is valid as type 3 name
11/27 15:02:52 NetpCheckDomainNameIsValid for xx returned 0x54b
11/27 15:02:52 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
12/01 15:36:31 -----------------------------------------------------------------
12/01 15:36:31 NetpValidateName: checking to see if 'xx' is valid as type 3 name
12/01 15:36:31 NetpCheckDomainNameIsValid for xx returned 0x54b
12/01 15:36:31 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
12/01 15:37:23 -----------------------------------------------------------------
12/01 15:37:23 NetpValidateName: checking to see if 'xx' is valid as type 3 name
12/01 15:37:23 NetpCheckDomainNameIsValid for xx returned 0x54b
12/01 15:37:23 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x54b
12/01 15:37:27 -----------------------------------------------------------------
12/01 15:37:27 NetpValidateName: checking to see if 'xx' is valid as type 3 name
12/01 15:37:27 NetpCheckDomainNameIsValid [ Exists ] for 'xx' returned 0x0
12/01 15:37:27 NetpValidateName: name 'xx' is valid for type 3

Edited December 1, 2009 by shertz

[genu]

Check your name resolution. check if your dns/wins/dhcp options settings are correct and everything is working properly.

btw: NetBIOS is *NOT* route-able .... only in conjunction with a wins server.

[MrJinje]

Have you tried moving one of your DC's to the new subnet.

Otherwise, here is a troubleshooting guide from Technet

If your network crosses multiple subnets, you must configure these additional options:

• Name resolution method (WINS, DNS, Lmhosts or Hosts files)

•Default gateway

•Verify that the correct domain or workgroup name is specified. Check the Workgroup and Domain fields for incorrectly entered names.

•Attempt to ping the domain controller by name, using the NetBIOS (that is, DomainController1) or fully qualified DNS name (that is, DomainController1.domain1.reskit.com). If unsuccessful, attempt to ping the domain controller by IP address.

•If the attempt to ping the domain controller by name was not successful and DNS and/or WINS is used for name resolution, verify the IP addresses of the name servers. Attempt to ping the domain controller by name again.

•If the attempt to ping the domain controller by name is unsuccessful and the Windows 2000 Professional–based client is in the same subnet as the domain controller, check the client's IP address.

•If the Windows 2000 Professional–based computer is in a different subnet than the domain controller, confirm that the you have specified the correct default gateway(s).

•If Routing Information Protocol (RIP)–enabled routers are used in the network, install RIP support.

Edited December 17, 2009 by MrJinje