re: domain controller could not be contacted
Sunday, September 28, 2008 at 5:57 pm
Windows Server 2003 Annoyances Discussion Forum
Posted by appleoddity
(2369 messages posted)
The nslookup is functioning as normal.
This is basically saying (and if you see a problem with this then you have a clue)
that your primary DNS server is 192.168.2.10 and your secondary server is 192.168.2.1
as configured on the machine you ran the nslookup on. It is also saying that it
can not do a reverse IP lookup of these two addresses, thus telling you they are
non-existent domains. (Common, and nothing to even consider) It then tells you
that according to the DNS server at 192.168.2.10 the host 'exodus' is at 192.168.2.10.
Also, it is showing you that your primary DNS suffix is server607.com which is obviously
your internal domain name. Therefore, exodus.server607.com resolves to 192.168.2.10.
If you ran this command from genesis2, then I see nothing wrong with it, unless I
am missing something. However, I am assuming that 192.168.2.1 is your router or
gateway. This means that your secondary DNS server entry is invalid, because if
the primary fails, the secondary will not provide the proper information because
it is not a DNS server that is integrated with AD. The only DNS server configured
on Genesis2 should be the primary DNS server of 192.168.2.10. Actually, it should
be the only DNS server configured on every machine on the domain.
When you join your domain, you should be telling it you want to join the server607.com
domain. If anything I have told you does not match up with what you know, then there
is something configured wrong.
I would like for you to provide the output of the 'ipconfig /all' command on both
genesis2, and exodus so I can verify your settings.
|
All messages in this thread [show all]
 | | |  | re: domain controller could not be contacted (appleoddity: Sun, Sep 28, 2008, 5:57 pm) |
| |
| |
| |
Return to the Windows Server 2003 Discussion Forum
|
|
