issues with adding workstation to our domain.

[rasczak]

I am having issues with AD. I can’t seem to add a workstation to the domain. The workstation is located in a different subnet. I am able to ping, just unable to join. Any ideas?

i have added the host (A) records and PTR records in DNS. I am able to resolve them in nslookup, however i am having a fit joining the darn thing.

network

wksta 192.168.1.1 ------tunnel------- 192.168.10.1 router 192.168.250.1 ------- 192.168.250.100 DC

i hope this makes some sense. i'm in a tight bind time wise. anything will help.

 

[bruceb]

Look here first: http://technet.microsoft.com/en-us/library/cc976452.aspx

And maybe also here: http://support.microsoft.com/kb/251335

 

[rasczak]

Look here first: http://technet.microsoft.com/en-us/library/cc976452.aspx

And maybe also here: http://support.microsoft.com/kb/251335

No go, I had already added a computer account in that fashion and still was unable to get the computer to join. The issue is DNS related after much searching.

nslookup domain

server.domain can't find domain: non existent domain.

 

[StormSide]

manually add the AD DNS server IP to the workstation. Or set up the DHCP server to give
out the AD DNS server IP

 

[rasczak]

manually add the AD DNS server IP to the workstation. Or set up the DHCP server to give
out the AD DNS server IP

using static ip's. dns authoritative already added as primary. i am now seeing the issue on my domain controller/dns server

 

[RebateMonger]

nslookup domain

server.domain can't find domain: non existent domain.

Is that the EXACT message you are getting from NSLookup, or are you paraphrasing the message? I don't mean the domain name "domain" or the server name "server.domain", but I mean the other words, "can't find domain: non existent domain".

 

[rasczak]

Is that the EXACT message you are getting from NSLookup, or are you paraphrasing the message? I don't mean the domain name "domain" or the server name "server.domain", but I mean the other words, "can't find domain: non existent domain".

this is correct. it is a weird issue to say the least.

 

[rasczak]

found the fix. i needed to add a couple of lines to the lmhosts file.

http://support.microsoft.com/kb/180094

hope this fix helps someone out there.

 

[RebateMonger]

n.m.