Discussion Locked

Name Resolution

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an NT Server that has Microsoft Proxy 2.0. My clients connection to the server is extremely slow with some applications. When I ping the server IP address it comes back instantly. When I ping the server name, it comes back extremely slow. Theclients IP addresses are static. We have DNS and Wins. Three clients to this but one is fine, however all the settings are the same. I gave gone through my settings with a fine tooth comb and dont seem to be able to find the problem. Any ideas?

9 replies

by marnus

You don't mention what type of clients you are using, but I had a similar problem and the solution might just help you.

In your TCP/IP settings in your Network Properties, go to the WINS tab.
There should be an option "Enable DNS for Windows Resolution". Check that it is selected.

I think the problem with the apps is that some are trying to connect with a computer name, while others are probably connecting to the IP address. You can always add the server's IP address and name in the hosts file of the client and test it, should my suggestion not be of any value.

by spydergst1

You may have considered this already but, Be sure the Domain in the DNS configuration are the same on both the server and the client side. Also set the DNS sevice search order and the DNS suffix search order. Be sure the server has a DNS entry for the DNS domain. Verify how the router or switch is configured. If it is set for 100 Mb full duplex then set the server to 100 full. Auto sensing media speed and duplex settings for the nic is not very efficient. It works but , it does always auto sense correctly.

by rogued,mcse

One thought would be check to see if the one machine that is not having latency issues is configured with a LMHOSTS file. Also, check the baseline of your WINS server in Performance monitor. The only other thought is make sure your physical network is correct for all machines. Hope this helps

by networkmunchkin

I had similar performance issues with Proxy 2.0 as well.
My solution was to have all client apps resolve the proxy server by IP address rather than by hostname. Anywhere in client software that I had to specify the proxy I would input http://nnn.nnn.nnn.nnn:80 rather than http://hostname:80.
I also specified on the proxy server to have clients resolve by IP.

That may be an option you can consider, though other reasons my prevent it. It did clear up my resolution time problem though.

by zharia

I thank you all for your replies and actually solved the problem by doing the opposite of all of the above. My clients are Win 95/98. My proxy was set to resolve by IP address. My DNS was enabled with assigned IP addresses and relevant gateway and Wins was also enabled. My cards are 100 full duplex and set to auto sensing. What I did was change the order of the nic cards on my server so that the internal nic was read first, I think it was possible because I had it the other way around it was going out and searching for the name. Second I disabled DNS altogether and it made a whopping difference in speed. My proxy now does my name resolution and when I ping the server it comes back instantly. You learn something every day:)

This discussion is closed to new replies.