Re: XP DNS problem

<kleinbottle5@xxxxxxxx> wrote in message news:1168539518.983985.73880@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We have a local network of 70 mixed Windows PC workstations. Some are
NT4, some Win2000 and 6 are XP(Pro). The DHCP is serviced by an NT4
server.

The 6 XP workstations over the last few months sporadically (every 2
weeks on avg.) seem to lose connection with the outside world. The DNS
setting in the XP client is being set to 192.168.0.1.
But our DNS is really 198.x.y.z . Our internal network is a C class
(193.1.1.xxx). The problem is fixed by doing a "IPCONFIG /RENEW" or
restarting the client.

This is setup correctly in our DHCP server, has been working for years
and continues to work for all the other Windows clients. We have the
DHCP turned off on the router although it also has the
198.x.y.z setup in it.

We check frequently (dhcpfind.exe) to see if there is another DHCP
service popping up in our network - but can't seem to find any.

We've noticed also that the occurrences don't seem to be related to the
lease renewals on the IP addresses.

Only the XP machines seem to suffer this problem.

Anyone hear of an XP bug relating to this?

Thanks in advance for any thoughts.
Wayne


I've never heard of dhcpfind.exe, but if there is a rogue DHCP server on the network and some machines are picking up bad configs from it, the way to identify it is to go to a machine which HAS picked up a bad config, and then look at the connection properties. ( or do an ipconfig /all at the command prompt. )

This should reveal the IP address of the DHCP server that provided the bad configuration which is in use. Then track down that machine and investigate it.

It could be a PC which is occasionally connected to the LAN which has some Internet Connection Sharing software running, for example.

--
Ron




.

Relevant Pages

  • adding a printer FIX
    ... server 2003 enterprise machine: IIS, mail and File server- and now partial ... internal XP machines ... the printers were not on the server itself. ... 4.Remote into the server again and run the new connection wizard select make ...
    (microsoft.public.windows.server.networking)
  • Re: Adding Printer FIX
    ... server 2003 enterprise machine: IIS, mail and File server- and now partial ... internal XP machines PRO ... the printers were not on the server itself. ... without a physical connection to the server and no SCSI cards need be added. ...
    (microsoft.public.windows.server.networking)
  • Adding Printer FIX
    ... server 2003 enterprise machine: IIS, mail and File server- and now partial ... internal XP machines PRO ... the printers were not on the server itself. ... without a physical connection to the server and no SCSI cards need be added. ...
    (microsoft.public.windows.server.networking)
  • Re: Adding Printer FIX
    ... > print server. ... > 2 internal XP machines PRO ... > network was just fine all printers shared and accessible. ... > without a physical connection to the server and no SCSI cards need be added. ...
    (microsoft.public.windows.server.networking)
  • Re: Installing SBS2k3 CEICW Network Error
    ... DHCP Server 192.168.0.1-254. ... Internal NIC gets 192.168.16.2 from SBS2k3 DHCP server. ... Boot SBS2k3 from CD1 in CD-ROM and start install. ... > Leave the box talking about a single network connection unchecked, ...
    (microsoft.public.windows.server.sbs)