win2k share slow

[slam]

winxp machine: system is 2.8 ghz p4, w 10/100 nic on switched network.


I've tweaked the registry setting to speed up xp connectiong to shares as per bills sticky, but I still have to wait 30-60 seconds before a shared drive on win2k server opens. What else do I need to look for.

[BipolarBill]

How fast are transfers once connected? Are all other factors in place (workgroup, logon account)?

Try replacing the Ethernet cable.

[slam]

haven't tested more than 3 machines but each one has the issue. After the first connection its up to speed.
example.
open program, go to mapped drive open first doc. wait 60 seconds, open 2nd doc wait 1 second, 3rd 1 second etc. close program, open program , wait 1 second for opening next doc.

2nd scenario
boot computer
manually go to mycomputer
open mapped drive wait 60 seconds
go to program
open doc wait 1 second.

I'll double check workgroup.
doubt its all the cables. was fine before with win98. no change other than new pcs with xp
if user doesn't have account I get IPC$ password prompt.

[Midknyte]

what protocols are you using in the network? tcpip? netbeui?

[BipolarBill]

Are all firewalls deactivated? How about the native XP firewalls?

http://www.duxcw.com/faq/win/xp/firewall.htm

[slam]

tcp/ip ipx/spx
I'll check the xp firewall

[Midknyte]

why are you running ipx/spx? are you using novell netware?

are you using a domain or just a workgroup?

[BipolarBill]

Really - IPX is not a standard protocol in XP. It must be installed deliberately unless this is an upgrade. In that case, you should uninstall it.

[slam]

I'm on a Novell network that is why it's there.

[slam]

no domain in 2k, just a workgroup and shared drive. The network users are logged into novell and accessing a 2k application server.

[Midknyte]

I'm not a novell admin, but did you add the gateway services for netware on the win2k server? Just guessing here.

[rraehal]

We had the same issue with IPX/SPX (from Microsoft) on our network when we accessed novell servers. You can install the Novell Client from Novell to help speed things up, but then TCP/IP access is slowed down to MS servers. We finally eliminated Netware and use Windows Servers and TCP/IP now.

What version of Novell are you using? If you have version 4 or newer you can install TCP/IP. In version 4 it is an option. In version 5 and 6 it is standard.

[slam]

We are using 5.x and I'm thinking its using the both protocol option. Can I drop ipx? what would happen. ?

[BipolarBill]

Novell 5 supports TCP/IP, doesn't it?

[slam]

winxp firewall is not enabled.
I looked at two different machines. one has ipx/spx and the other does not but they both have lag. Both have novell client installed however one is 4.83 the other 4.90sp1 .

[slam]

3 machines
novell 4.83 client with spx
timed machine 1 60 seconds removed ipx timed 13 seconds
better

machine 2
novell 4.90x client no spx
didn't time just removed client and timed with 4.83 and spx removed
10 seconds

machine 3
4.90x client no spx
timed 10 seconds

still not good enough need more help

[rraehal]

AT least we were able to determine that the client weas causing part of the slow down.

I am not sure where to go next. I know my mapped drive K: takes 6+ seconds to open. My other drives take 1-3 seconds. In my case it is because of the volume of files on my K drive - 670 objects in the root of the volume. My other drives have 12 to 18 objects in the root of the mapped volume. Maybe this is where you should look next.

Maybe the lag is going to be part of accessing Novell from Windows due to authentication the first time you access the volumes.

[slam]

My cd didn't have latest service pack on it. Now running 4.90sp3 and I've got the following results
test 1 , 2 seconds
test 2 , 5 seconds
test 3, 1 second.

I think this should be satisfactory. Especially compared to the 60 second worst case test we had.

thanks for all your suggestions.