What happens if you use the entire FQDN? Also, check the 'Advanced' tab in 'Remote Access' to confirm that you have completed that tab, especially the 'Domain name'.
What happens if you use the entire FQDN? Also, check the 'Advanced' tab in 'Remote Access' to confirm that you have completed that tab, especially the 'Domain name'.
Cheers - Bob
I ran into so issues earlier this week after the post but the domain is no longer activce becuase useing markonsolutions.com (or domain) would screw up the dns records and not allow any traffice to our proper website
Still sorting that bad boy out
I'll have to get back to you on the full name resolves test
I understand you have some other issues before you can get back to this so consider this background info at this point.
Looking at the readout I didn't see what I needed. It looked like you did an nslookup on one of the servers in the domain & not the domain.
When I do a nslookup on a test domain, I see the following.
C:\Documents and Settings\Drew.TEST>nslookup test.local
Server: dc1.test.local
Address:
Name: test.local
Addresses: , ,
C:\Documents and Settings\Drew.TEST>
I've sanitized my results but what I get when I query the domain itself is a list of IP's of the various domain controllers.
In general though, it looks like your DNS resolution for that domain was failing. To join a domain, the PC in question must have full DNS resolution of the domain. Without that, it will not work.
