Windows Forum

Ask something
Discussion Locked

Slow name resolution

0 helpful
10 replies

by oakie

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am administering an NT 4.0 domain with 50 NT 4.0 clients 1 pdc sp6a running DHCP and WINS, 1 member server NT4 sp6a running SQL 7.0. I'm having an intermittent issue with name resolution of the SQL server. From the client machines I can ping theIP address of the SQL server and get an instant response, but if I ping the computer name either it gets name resolution immediately, or there is a 15 second delay after you press enter before there is a response. After a minute or two it will go back to immediate name resolution. I have tried recreating the wins database, but the problem continues. Any ideas would be helpful. Thanks

10 replies

by maxwell edison

A new feature of SQL Server 7.0, dynamic name resolution, resolves object names at runtime. Perhaps that's where you should look for a possible resolution.

Maxwell

by ksmith

Oakie,

On your DHCP server did you set the WINS/NBT Node Type? Generally, you want it set to Hybrid (0x8).

This will change the order that the workstation will try to resolve netbios names to IP addresses.

by oakie

Thanks for the thought, Yes the DHCP points to the WINS server and it is in Hybrid mode.

by graham marwood

Check the load on the wins server and the load on your network. Check the PC's are only getting the tcp config from wins and that someond hasn't added any static addresses i.e. wins pointing to the wrong address

by oakie

The machine and network loads are fine, the clients are definately getting addresses via wins and the only static mappings are the ones that I have added. Because the name resolution problem is intermittent I don't think that is an issue. Thanks for the ideas.

by shmaltz

Make sure NETBuei is not installed on any of the machines. Also moniter the Event log on the SQL server for any problems with browser.
Also, you didn't mention if this is only when you try to ping? or, also when you browse and try to view the resources available on the SQL machine?
If it's only when you try to ping by name. then I can tell you that in what I saw in windows is that it will sometimes (when and why I dont know) resolve a name slower when you try to ping then when you connect directly to the resource even if when you connect directly you are using the host name and not the IP address

by oakie

The machines all run only TCP/IP. The SQL Server event log is clean. When this symptom occurs the the application that runs on named pipes also slows. Thanks for the response.

This discussion is closed to new replies.