IP and name domain not found

[stuke]

I have a network using a single Windows 2000 Server (AD integrated DC
running DHCP, DNS). It has two NIC’s for redundancy (192.168.0.10 and
192.168.0.20), both are static and set to use the following DNS
servers, 192.168.0.10 and 192.168.0.20 and an ADSL router (192.168.0.1)
as the default gateway.

The server is not being found properly by name. I think this is
preventing some clients accessing the domain.

At one point I gave a network card on the server an automatically
assigned IP and it received the 192.168.0.50 address (presumably from
itself). I then changed it back to the static 192.168.0.10.

Today, when I pinged the server from a command line (ping server) it
lets me know that it thinks the server is at 192.168.0.50 but it does
not actually reach the server and the request times out.

Now, I know that this is because the server is actually at 192.168.0.10
and .20 (not .50)!
However I can not work out where the client is getting 192.168.0.50;
because the client is using a static address of 192.168.0.70 with
192.168.0.10 as the preferred DNS and 192.168.0.20 as and alternate DNS
server. The default gateway is the ADSL router (192.168.0.1).
I can ping 192.168.0.10 and get a normal response.

I have tried to flush the dns (ipconfig -flushdns) on both the server
and clients.
My servers ip address is pointed to by nds and all the clients and the
server have static IP addresses with the servers IP address set as the
preferred DNS in the TCP/IP properties.
I can see no record of the old 192.168.0.50 address anywhere on the
server, and none of the clients have a static link to 192.168.0.50

I can browse to the server using explorer \\server
but I cant ping server

Any ideas???

Thanks,

 

[Doug Sherman [MVP]]

Some observations:

1. Having two adapters with different addresses on the same subnet is a bad
idea which will cause multiple problems, especially on a domain controller -
you should disable one of these adapters.

2. Check the DNS console - there is probably a host or resource record for
192.168.0.50. Delete any such record, and restart the netlogon service on
the DC - check Event Viewer for errors.

3. If "all the clients and the server have static IP addresses", there is
no obvious need for DHCP.

Doug Sherman
MCSE, MCSA, MCP+I, MVP