WINS Issue

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

I have 2 WINS servers in our environment for legacy OS (Win9x, NT). At one
of our remote sites, users are unable to connect to a Windows 9x box using
its computer name. I sniffed the network traffic and determined that the
following error is being returned: "Requested Name Does not exist." I
received the same error when i used the nblookup tool from MS. I also
queried the 2 WINS servers and was not able to find a record for the PC in
question.

How can I determine why the record for the PC no longer exists? What can I
do to correct the situation?

thanks

Jeff
 
Jeff,

what kind of network are you running? Windows 2000
Servers? DHCP/Static IPs?

Regards,
Miguel B.
 
Miguel,

Sorry I did not include those details in my original post:

Windows 2000 Active Directory
One domain with 2 domain controllers (both at our main site)
Domain controllers are both also WINS servers
The issue is happening at a remote site that connects via a dedicated WAN
link back to our main location
All clients use DHCP server that is also at our main location

Hope that gives you the details you need.

Thanks,

Jeff
 
Is the DHCP server one of the Windows 2000 Server?

Is DHCP providing all TCP/IP settings or just the IP
Address and Gateway?

How are the sites connected via that dedicated WAN link?
any VPN appliance?

Are there any servers at the site?

Are you able to ping the machine and W2K servers by
hostname and IP address?


Regards,

Miguel B.
 
The Win9x box is configured to register with Wins - correct? If so, have you
tried restarting the Win9x box to see if it reregisters with Wins?

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Miguel,

See my answers below:
Is the DHCP server one of the Windows 2000 Server?
Click to expand...

No. The DHCP server is a separate server. Actually it is a UX server
running Cisco Network Registrar. The DHCP server is located at our main
site. However, in the case of the remote sites, they are getting their DHCP
addresses from the Cisco router that is on site.
Is DHCP providing all TCP/IP settings or just the IP
Address and Gateway?
Click to expand...

DHCP is giving out all TCP/IP settings including the correct WINS server
addresses.
How are the sites connected via that dedicated WAN link?
any VPN appliance?
Click to expand...

The sites are connected via a managed VPN (managed by our service provider)
Are there any servers at the site?
Click to expand...

No, not at this time. Users authenticate at the DCs at our main site.
Are you able to ping the machine and W2K servers by
hostname and IP address?
Click to expand...

Because of how our WAN is set up, we are not able to resolve names of PCs at
the remote sites. However, I am able to ping the PC by IP address.

Thanks,

Jeff
 
The box has been rebooted. After further investigation, I determined that
this Win9x box as well as one other Win98 PC at this site are not getting
the proper TCP/IP information.

The WINS server address that they are getting is an old one that is not in
service any more. Also the subnet mask is not correct. We verified that
the DHCP server on the router is giving out the proper information (W2K PCs
are getting the correct TCP/IP info).

Is there something in Win9x that causes the old info to stick?

Thanks,

Jeff
 
Jeff,

Try releasing all TCP/IP information by typying IPCONFIG /RELEASE_ALL
and then reboot the machine.

I've also noticed that some NICs tend to not refresh correctly when the
machine is restarted. Try shutting down the machine completely to see if
that helps.

Regards,

Miguel B
 
Back
Top