Slow Name Reslution

[setupen]

After applying the NW Client (any version) we see that the ping "server name" has a delay before it starts and before it hands over the command line again but if you pping the IP – Address it works fast. We tried to change the note type, add a wins server, go from DHCP to fixed IP, using LMHosts, Hosts but nothing will work. When we uninstall the NW Client everything is fast again.

Any ideas?

//Peter Eriksson

 

[TheLad]

What version of the NetWare Client are you using and on what OS? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[setupen]

Any version on the client side starting with 4.80 up to 4.83SP1. We are running NetWare 5.1.

 

[fitzdr]

Check your bindings on the workstation. The MS client should not be binding to IPX/SPX. The same goes for File and Print Services.

If you bind these clients to IPX/SPX for windows clients then you will be waiting for every request to complete this includes trying to find a Windows server running IPX/SPX.

If this is the problem then you will see it reaccuring if you make any major changes to your network settings.

 

[setupen]

The installation is done "IP Only / remove IPX if exist". The only protocol in use is IP.

 

[seancane]

How solid is your SLP rollout? How do you roll SLP information for the clients? Try to disable antivirus just as a test. Symantec and NW Client did not get alonmg well atall, although it was supposed to be resolved in 4.83. Many other components can be tweaked if it is W2K?

Does it happen if you ping by name a non-netware device?

Seancane

 

[setupen]

I would say that the SLP rollout is very solid. All clients receives SLP information through pinpointed devices brought out through DHCP. Disable or uninstall of Antivirus didn't help. Yes we are running W2K. The machine we are trying to access is a W2K Server in a workgroup and we do not aim for a AD as a test. The strange part is that when we uninstall the NW Client everything is working fine.

 

[Provogeek]

Try this one for a giggle; go into your network properties and click on the ADVANCED - Advanced Settings menu option .. Choose the Provider Order tab and make the Microsoft Windows Network the first Network Provider.

Brent Schmidt CNE, Network +
Senior Network Engineer
KIS Computer Center -

http://www.kiscc.com

East Bay, California; USA

 

[setupen]

Tried that earlier with no success....