Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I hope someone can help with an issue am having.
I would like to know why Windows NT/2000 worsktations on my company's novell network have trouble accessing shares from one another. The workstations have Novell Client 4.7 or 4.8 installed. When trying to access shares on any workstation and from one NT server, it takes about 30 to 40 seconds to access a directory. If you need to go through sub directories it will take even longer as it has to wait about 30 secs on each sub directory. This does not seem to affect Win9X machines with Novel Clients (I forgot the versions). If I remove the Client from an NT machine, accessing a share on another machine is quick. The shares are usually accessed through network neighborhood or with a UNC path in the run command.
Any suggestions?

Your cabling probably is not good enough
or there are too many cross-cables around.
Also different manufacturers ethernet
cards causes such problems.First close full-duplex enviroment ,change
to half duplex .If not OK ,use
10mbit connection speed on computers .You will see everything will be fine !

goto http:\\support.novell.com/cgi-bin/search/searchtid/cgi?/10052031.htm
It is caused by Novell treating the connection as a request for as NDS "object". The fix is to change the network access order to use Microsoft networking first. On my win2000 box I had client32 4.71 and client for microsoft networking second on my LAN connection properties. I uninstalled client fro microsoft and rebooted and reinstalled it. It then appeared first under properties. The Novell client login screen still came up first but it would then access the UNC share with microsoft networking first and connect quickly.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |