8 replies
by cedmison
A couple of different thoughts here.
First, Are you using direct drive letter mappings, or UNC mappings, suggest using drive letter mappings. Also, are those drive mappings made from a server based login script or from each individual workstation, recommend login script to ensure commonality from user to user.
Second, Might want to check in your
-> network neighborhood -> Client for Microsoft Networks -> Logon and Restore network connections. This is of course assuming that you are utilizing a domain.
Hope this helps.
by mbaldwin
by msgtray
This is just a possibility so don't get bent if it's not the answer (Some people expect that everyone in this community has a crystal-ball). If you are running a mixed environment, check your binding order on the clients. If NWLink is first in binding, the redirector will have to time-out on IPX before it stepps to IP. You can change the binding on the client to test the access, or you can add NWLink to the server. Binding order is not as critical on the server as it will respond with the protocol that it receives the request with. (Win9x binding is set with checkmark for default protocol)
Give it a shot, hope you solve your problem.
Ray
by jay allen
There are a lot of probably causes:
1. Which server is performing login authenication and mapping the resources? Remember that a resource request needs to be authenicated before being used. This would cause to iniatilization to become slower.
2. How are the resources being accessed and are each server using the exact network configurations? Large organizations may have a mixture of 10/100 ethernets and various configutations.
3.Also if I am not mistaken, IPX is faster than TCP/IP. If possible use just IP. However, IP by itself is non-routable but provides a speed boost in smaller networks.
by mbaldwin
by mbaldwin
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending