Windows Forum

Ask something
Discussion Locked

NetBIOS name resolution problems

0 helpful
17 replies

by networker4

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm having a problem with NetBIOS name resolution on Windows 95. Here's the situation:

1. NT DHCP server giving out the following configuration values:

a) IP address
b) Default Gateway
c) DNS server addresses
d) DNS domain name
e) WINS server addresses

2. Client configured to obtain an IP address automatically, DNS disabled (or enabled with only a host name specified, no domain name specified), and the "Use DHCP for WINS resolution" box checked in the WINS config.

The problem: Windows 95 will not resolve NetBIOS names using DNS. My NT servers are all entered into the DNS. WINS is used only to resolve group (i.e. NT domain) names. If I enter the (mycorp.com) domain name into the DNS config, NetBIOS names will resolve. I'm implementing DNS name resolution on approximately 5000 PCs, and I really want to avoid this. Due to a recent acquisition, the domain name may change in the near future and I don't want to have to go back and touch each PC again.

More info: When I say NetBIOS names, I mean that if I try to map a drive using a UNC of \\server\sharename, or if I do something like "net view \\server" windows reports that the server is not found. However, if I "ping server", the name is resolved and the server responds. Winipcfg reports all of the correct entries. The host name and the domain name are there. As long as I explicitly entable DNS and enter a host name the "NetBIOS resolution uses DNS" box is checked. If I leave DNS disabled thebox is not checked. Windows 98 behaves differently, correctly resolving NetBIOS names even though DNS is disabled. I have surfed the Microsoft support site and found no reference to this problem. I've installed winsock 2, the DUN 1.3 update, etc. Nothing seems to resolve this problem.

Any ideas?

17 replies

by james a bailey

Do you have Netbui installed? In Network Properties make sure you have Netbui installed. If not install it. Then in the Properties of netbui, make it your default protocol on the 98 machines. It will be a check box in the Advanced tab.

by shanghai sam

Netbeui is not an option. This is an IP network, and I don't want netbeui broadcasting on it. Also, there are several remote LANS, separated by routers. Netbeui doesn't route.

by mphoffar

Sounds like wins is resolving addresses correctly, just not DNS.

I guess a good way to test this would be to try to hit an address with a fully qualified domain name, like \\server1.somedomain.com instead of just \\server1. if it hits, then all your probobly need to do is add in a domain suffix on the DNS tab.

Good luck to you

Mark

by shanghai sam

But my point is that I don't want to have to enter a domain suffix in DNS. This is a parameter that is distributed with the DHCP options, so the client is aware of it. DNS does, in fact, resolve the names - just not when the name is a NetBIOS application such as mapping a drive. By the way, using a FQDN as the host name in a UNC doesn't seem to work with 95 like it does with NT.

by mphoffar

That's true about the 95 not acting the same way as NT does. Only way I can remember to work around that with the winsock2 was to hit the server with \\server. instead of using \\server (without a period). This was the last resoltion I remember from the mskb (Q227120).

Another article I use on occasion is Q158474. Basically reg entries for specific NetBIOS and TCP/IP functions. Has good info in it, but not sure if there's anything there that'll help you or not

Mark

by networker4

I've seen the knowledge base article on the TCP/IP parameters. Unfortunately, here doesn't seem to be a "fix NetBios name resolution parameter". I hadn't seen the Q227120 article. It claims to apply to 98, not 95. And it doesn't seem to work on 95. Thanks for the info, Mark.

by milky

Correct me if I am wrong, but my understanding of DNS is domain name resolution and WINS is computer name resolution. SO why would you want DNS to resolve the NetBIOS names if its WINS job to perform that task?

by shanghai sam

I'm not sure what you mean when you say "DNS is domain name resolution". DNS resolves host names to IP addresses. When using NetBios over TCP/IP, WINS resolution accomplishes essentially the same thing. If you look at the Microsoft documentation on the name resolution process it claims that DNS will be queried for NetBios Name resolution. That's why when you run WINIPCFG, there is a check box that says whether or not the client is configured to use DNS for NetBios Name resolution. See article Q172218 - this only tells a small part of the story. For a more complete look at how this is supposed to happen, see the NT Networking Resource Guide, chapter 6. The bottom line is, I don't want to have to maintain both lists!

by rvkempen

You might want to install a wins node type in the dhcp server, in your situation I would set it to 0x8 (Hybris Node)
(first ask your wins server, if that does not help do a broadcast)
In your dns config I would look at the resolve dns addresses using wins, and ofcourse the reverse settings should be checked (resolving computer names giving ip addresses)
Take in mind that a dns entry is checked before a netbios entry, so it's always a good idea to have your dns set up right.

Good Luck

Ron.

by mad max

It is a failing of 95 and as far as I can see you have two alternatives.. Upgrade all 95 clients to 98 or specify the domain information on the 95 machines and then use a login script to modify the entry at a later date.

by lanwanman352

First, consider upgrading from Windows 95 to Windows 98 or later operating system.

Microsoft Windows clients use different methods of host name to IP address resolution. The sequence of methods is different than the sequence used to resolve NetBIOS names to IP addresses.

When Windows 95 tries to resolve a NetBIOS name using a NetBIOS name server, it first checks a Windows Internet Name Service (WINS) server, and then checks a DNS server (compare this order when reviewing the Microsoft Knowledge Base articles listed below).

When using Windows 95 and DNS, one should use a WINS server for NetBIOS name resolution. Under most circumstances, the default resolution order does not need to be changed. However, to overcome the problems with your Windows 95 clients, changes will have to be made. The following Microsoft Knowledge Base articles should help in your decisions.

Q172218
Microsoft TCP/IP Host Name Resolution Order

Q119493
NetBIOS over TCP/IP Name Resolution and WINS
Q170619
Windows 95 ServiceProvider Priority Values
Not Applied

Q171567
Windows NT 4.0 ServiceProvider Priority Values Not Applied

Q139270
How to Change Name Resolution Order on Windows 95 and Windows

Q119372
Setting the Name Resolution Search Order for TCP/IP-32

File Names: tcpimp2.exe (Tcpimp2.doc zipped) at:

ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/

Titled: Microsoft Windows NT 3.5/3.51/4.0: TCP/IP Implementation Details TCP/IP Protocol Stack and Services, Version 2.0

This discussion is closed to new replies.