Windows sbs 2003 slow network

From Word or from double-clicking on the file from a folder view? Thanks for the suggestion. There is only the one network drive on this computer. Opening a K Word doc from the server by double-clicking in Explorer took 23 seconds. Still way too long. Other thoughts? Thanks, -Steph. Sunius Distinguished. Dec 19, 0 19, What about copying the file to your own hard drive?

How long does that take? Sunius :. Sorry for stupid question, but do the workgroups match? The only time I have seen slow network files open like this took weeks to find the fix, and it was a network drive that was mapped that was no longer connected. There is no old drive stuck in the system? If you go to "Disconnect Network drives", does anything show up? This was a nasty thing to track down, in my case it was a user who was opening a VPN connection to another site, mapped a network drive to it, and disconnected.

Whenever she tried to open a document, Office would scan all her drives, and get stuck on the disconnected drive till it timed out. But when he is not connected, those drives do not show in My Computer on his office PC. I guess I am still mystified that the delay is most pronounced with Word files.

I was thinking that Word was using the network folder for its temporary files instead of a local folder. Do you know how to ensure that local folders are used for Word's temporary files? It's not the temp files, it's the Open file process that is the issue. The drive may not show up in My Computer, go to Disconnect network drive option and see if there is anything listed there.

This may be the issue, it sounds a lot like what I worked on, and the fix was to disconnect the drives before shutting off the VPN session. If the issue is on the office PC, need to check it there.

Should be in the Tools menu in any folder window. Although I don't know the exact location in 7 offhand. Try OpenOffice, see if that opens faster. Or a different version of Office if you have a copy to use.

Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Small Business Server. Read Sticky Post at the top of the forum. Sign in to vote. Any suggestions are appreciated. Friday, January 27, AM. It's really wired though it is normally looking for a file called, wdmaud. It is also sometimes looking for files with random file names. This is all happening during the open process. It is also happening on both Windows 7 computers and Windows XP computers.

Also for reference I've ran the trace on the same computers communicating with a 08R2 server and do not see any Object Not Found issues. I'm waiting on Microsoft's response but I was wondering if anyone has seem anything like this. I've also come across some articles that say SMB Signing could be the issue. Any opinions on if disabling this on my SBS server is a good idea and could help with my performance issues?

To continue this discussion, please ask a new question. You can also detect this by running a capture using Wireshark as it will show all the checksum failures if this is the case.

Thank you The Matt for your suggestion. I've disabled Checksum Offloading on the server and I am still seeing a lot of Checksum errors when I run wireshark on the troubled client machine. I have a feeling this could be the problem, or something with offloading as I read this is common with Broadcom NIC's.

Or has the server been rebooted? In working with Microsoft on the issue, they had me run some network traces using Microsoft Network Monitor. In reading these traces I've found that for some reason the clients on the remote network are looking for some files that aren't there during the opening of the file process, specifically I'm seeing Object Not Found in the trace.

It's really wired though it is normally looking for a file called, wdmaud. It is also sometimes looking for files with random file names.

This is all happening during the open process.