Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I had a little network glitch and since then one of my servers shows up wrong at some workstations when typing in \\server\.

Example:

On workstationA I go to Explorer and and type \\server\ and it brings me to our copier at 192.168.2.101. \\server.company.local\ gets me to the right place at 192.168.2.252.

Ping with server pings 192.168.2.252 - same correct result with ping server.company.com nslookup also shows correct result with both. reverse lookup by ip is correct also.

I flush the DNS on the workstation and the error still occurs. reboot same result.

At that point I give up and start remapping the shares to \\server.company.local\share just to get the user back working...

DNS Server has correct entries for that server. Can access the server via \\server\ on dns server, all looks fine.

Eventually the workstation figures it out by itself and \\server\ works again but my life wouldn't be as stressful if I had a clue what happened or how to fix it myself.

Thanks for your time looking and answering.

share|improve this question
    
what does this command return when run from a command prompt on Workstation A? nbtstat -an servername –  Tatas Jul 1 '11 at 16:05
    
@Tatas - I wish I had a failing workstation right now :) - I posted after the last one magically fixed itself after I remapped a bunch of shares manually. I will brush up on WINS and certainly check out nbtstat results along with flushing that cache to see if it solves upper problem. –  Jimmy Jul 3 '11 at 17:06
    
nbtstat -an server returns: C:\Documents and Settings\alice>nbtstat -an server Local Area Connection: Node IpAddress: [192.168.2.54] Scope Id: [] NetBIOS Remote Machine Name Table Name Type Status --------------------------------------------- SERVER <00> UNIQUE Registered MCO <00> GROUP Registered MCO <1E> GROUP Registered MAC Address = 00-0C-29-7F-15-17 –  Jimmy Jul 5 '11 at 13:25

2 Answers 2

up vote 1 down vote accepted

Try disabling NetBIOS name resolution.

Network adapter properties -> TCP/IP properties -> Advanced -> WINS tab -> Disable NetBIOS over TCP/IP

enter image description here

Strip out any WINS config, too, and make sure you aren't getting a WINS server configured by DHCP.

share|improve this answer
    
Man that is scary. Are you that certain that he doesn't have a dependent service that cares about NetBIOS. That could be some seriously bad advice for some networks. –  Mark Jul 1 '11 at 17:11
    
@Mark He's doing the name resolution from a workstation, not a server. So no, I'm not too terribly worried about the consequences of making that change on the workstation. –  Shane Madden Jul 1 '11 at 17:12
    
Disabling netbios over TCPIP did the trick. –  Jimmy Jul 5 '11 at 13:31

You're possibly confusing WINS and DNS.

\server\share

uses a WINS entry which holds the NETBIOS name to IP mapping

\server.company.local\share

uses a DNS entry which holds the FQDN (Fully Qualified Domain Name) to IP mapping

If you're running a local WINS server, you'll want to rectify the issue you have with the server's netbios name entry. You can manually modify the record, or just delete it and run the following command from the command prompt on your server.

nbtstat -RR

If you're not running a WINS service on your network, then you can disable it as the other answer has described. WINS is a legacy windows service that would store and serve up NETBIOS names on your network. DNS is a domain name resolution service that stores and serves up records which hold the FQDN (Fully Qualified Domain Names, such as www.microsoft.com) to IP mapping, or vice versa. There are other records that it can host, but these are the main two that most people need to know about.

share|improve this answer
    
A single-name entry can be resolved via DNS search suffix, WINS is not necessarily used in all situations. –  Shane Madden Jul 1 '11 at 17:18
1  
Agreed. It could be possible that the search suffixes are different on these hosts. It's why I added the comment above to see what gets returned from an NBTSTAT. –  Tatas Jul 1 '11 at 19:38
    
Completely missed that! Good point. –  Shane Madden Jul 1 '11 at 19:50
    
NP. It's hard to troubleshoot these things when you have no idea what someone elses network is like. –  Tatas Jul 1 '11 at 20:00
    
nbtstat -RR does nothing :( –  Jimmy Jul 5 '11 at 13:28

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.