re: domain controller could not be contacted
Sunday, September 28, 2008 at 6:45 pm
Windows Server 2003 Annoyances Discussion Forum
Posted by DjJeffRush
(8 messages posted)
OK, here is the info you asked for:
IPCONFIG FROM EXODUS:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : exodus
Primary DNS Suffix . . . . . . . : server607.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : server607.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 82558-based Integrated Ethernet
with Wake on LAN
Physical Address. . . . . . . . . : 00-90-27-F1-09-F3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
IPCONFIG from Genesis2
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : genesis2
Primary DNS Suffix . . . . . . . : server607.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : server607.com
Ethernet adapter Local Area Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC 3C905B-TX)
Physical Address. . . . . . . . . : 00-50-04-6C-6B-75
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.10
I think I might be getting a clue here, but I want to hear your opinion first.
(Thank you so much by the way!)
On Sunday, September 28, 2008 at 5:57 pm, appleoddity wrote:
>
>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 (DjJeffRush: Sun, Sep 28, 2008, 6:45 pm) |
| |
| |
| |
Return to the Windows Server 2003 Discussion Forum
|
|
