Delayed network access with Windows Server 2003 - long network response time

From: Jürgen Rudolph (rud_at_parsytec.de)
Date: 03/29/04


Date: Mon, 29 Mar 2004 16:29:32 +0200


Dear community,

after we had switched the server OS from Windows NT4 Server (SP6a)
to Windows Server 2003 (Standard), we detect sometimes a delay of
about 8 seconds during file access over network.
This effect happens every 6th to 44th access using UNC network path
(e.g. "type \\172.17.1.1\temp\test.txt" on W2k3 Server with IP
172.17.1.100).

The descibed problem is requested to Microsoft Support (Germany) as
"SRQ040319600680 Performance Problem".

For network access the IP address is used to avoid name resolving
problems, but DNS is configured properly too (nslookup.exe answering
is correct and the MS Tool netdiag.exe does not detect an error).

The "Client" computer sharing "temp" have one of the OS Windows XP
Professional or Windows XP Embedded and is member of the w2k3-servers
domain.

The network access from "Client" to W2k3 Server is delayed too (about
same incidence) but the average delay is only 1 or 2 seconds.

The network access from "Clients" to "Clients" are not delayed!

After I mapped the "Clients" shares to a drive letter on W2k3 server
("net use * \\172.17.1.xx\temp"), there are no more delayed network
accesses using the UNC path moreover (not the drive letter!).

During the delayed network access no more network accesses (to other
"Clients") are possible. These are also delayed for the same time.

During the delayd network access TCP network traffic works fine (VNC,
RemoteDesktop, netio,...).

Experiments with Windows 2000 Server instead of Windows Server 2003
did not show any delay in network access.

Microsoft KnowledgeBase Articles 328890 and 815230 (TcpAckFrequency)
did not solve the behavior.

I have attached a batch file (measure_net_access.bat) which creates
a small text file in the share "temp" of a client pc (must be set
in the batch file) and measure the time for reading this file
countinously.
The measured times are loged in files named like the client name.
Thes logs can be imported to Excel and e.g. displayed as x-y-graph.

Please, can anyone confirm this behaviour of the network access W2k3<-->XP ?

Thanks in advance,
   Juergen






Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: random lockouts
    ... >> I've got a network with several Windows 2000 Servers and ... >> about 150 Windows 98 clients. ... >This problem occurs because the Windows 2000-based server ... >because the session that is reused is against a DFS ...
    (microsoft.public.win2000.security)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)