djmagicb
asked on
TREE or Server can not be found after Upgrading on XPSP2
Hello,
i am using a Novell Netware 6 on the server and recently upgrade all the computer clients from Windows XP to Windows XP SP2.
The Novell Netware client version running on the desktop machines is v4.91 SP2.
Novell client installation was done with the option IP only. The firewall has been disabled in Windows XP.
The problem is that after starting the Windows it take around 5-10 minutes to login. The message displayed is "TREE or Server can not be found"
Sometimes i have to restart the client pc 7-8 times and wait each time up to 6-10 minutes to login.
On the Novell knowledge base advice to upgrade the Netware client which was not useful.
Any ideea on how to troubleshoot ?
i am using a Novell Netware 6 on the server and recently upgrade all the computer clients from Windows XP to Windows XP SP2.
The Novell Netware client version running on the desktop machines is v4.91 SP2.
Novell client installation was done with the option IP only. The firewall has been disabled in Windows XP.
The problem is that after starting the Windows it take around 5-10 minutes to login. The message displayed is "TREE or Server can not be found"
Sometimes i have to restart the client pc 7-8 times and wait each time up to 6-10 minutes to login.
On the Novell knowledge base advice to upgrade the Netware client which was not useful.
Any ideea on how to troubleshoot ?
Did you have the 4.91 client already installed prior to updating to XP SP2?
Have you applied any post-4.91SP2 patches to the client? There are several, enough to make an update-pack.
Go to http://support.novell.com/cgi-bin/search/searchtid.cgi?/2973629.htm
You may want to go to http://support.novell.com/filefinder/month/index.html and look for any new client patches that may refer to your problem, as well
As pgm554 said, if you have NMAS installed and don't use NMAS login methods, it can slow things down considerably, but you would've noticed slow logins prior to XPSP2 if you had it installed, too. Just for kicks, uninstall NMAS (if you don't use it) and set "use NMAS" to "no" in the client32 properties, advanced login tab.
There are other things XPSP2 has going against it besides the firewall, too. Check all of your services and make sure nothing you don't need is enabled.
Also, in Windows Explorer, Tools, Folder Options, View tab, make sure "automatically search for network files and printers" is off, as well as "simple file sharing."
Also, regarding the XP firewall, don't just turn it "off" in the Security Center. Disable the firewall service in the Services control panel.
Have you applied any post-4.91SP2 patches to the client? There are several, enough to make an update-pack.
Go to http://support.novell.com/cgi-bin/search/searchtid.cgi?/2973629.htm
You may want to go to http://support.novell.com/filefinder/month/index.html and look for any new client patches that may refer to your problem, as well
As pgm554 said, if you have NMAS installed and don't use NMAS login methods, it can slow things down considerably, but you would've noticed slow logins prior to XPSP2 if you had it installed, too. Just for kicks, uninstall NMAS (if you don't use it) and set "use NMAS" to "no" in the client32 properties, advanced login tab.
There are other things XPSP2 has going against it besides the firewall, too. Check all of your services and make sure nothing you don't need is enabled.
Also, in Windows Explorer, Tools, Folder Options, View tab, make sure "automatically search for network files and printers" is off, as well as "simple file sharing."
Also, regarding the XP firewall, don't just turn it "off" in the Security Center. Disable the firewall service in the Services control panel.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Good call, floyd99. Had the same issue when I started using wireless with 802.1x WPA-1 - somehow the NetWare servers got into bad address cache and those PC's experienced the tree/server not found thing, and setting it to zero fixed it.
i'll never forget about that setting.. because I spent 2 full days at a site an hour and a half drive away at a coastal town in the middle of nowhere trying to fix it before classes on the monday... I tried so many things. What was weird is it only happened on the PC's that had been recently re-imaged with a newer ghost image. What caused the server to be placed in the bad cache I still don't know, but we've pushed out a reg setting to disable it on every PC across the network.... don't even know (or care) what the bad cache does.
It's supposed to speed things up - non-responding IP addresses don't get retried while they're in the cache.
There's a similar setting for bad server name cache that it also might help to disable.
There's a similar setting for bad server name cache that it also might help to disable.
ASKER
Thanks guys. it works perfectly
No NMAS?
If you installed NMAS on the client piece,it can bog things down.