Server 2003 Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have 1 Windows 2003 (SP1) server in the mix of 16 servers. All others are
W2K and a mix of SP3 and SP4. The Windows 2003 server (file server) is
noticabley slower when accessing via a mapped drive. The 2003 is an
application server, with no other roles.

For example, selecting START > RUN and acessing one of my W2K servers (i.e.
typing g:\) and instantly I get the drive contents. This is the same with all
the 2000 servers. With the 2003 server typing p:\, and it takes a couple of
seconds to see anything. When browsing folder contents on the 2003 server, a
folder with many files can take 5-6 seconds to display while explorer shows
"searching for items" on the window status.

I have disabled SMB signing, optimized provider order in network advanced
settings, and disbled auditing.

Any ideas? I have heard that SMB was changed in 2003. That is why I fcussed
on SMB as a possible solution. Anyway...any ideas would be appreciated.
 
Stop using mapped drives and start using UNC Paths. Mapped drives are a
thing of the past.
 
We get the very same performance when accessing the share via UNC. Whether I
agree with you or not about mapped vs UNC (I would argue that UNC requires
has more name resolution overhead), the fact remains that many applications
do not support UNC partially or at all.

I did, however, found my solution. The issue is described in KB328890.
Adding a
TcpAckFrequency variable on the XP SP2 workstations dramtically sped up
performance. Apparently in XP and 2003 changes were made in TCPIP that delays
TCP acknowledgements to reduce network traffic. The reg setting forces XP to
acknoweledge every packet. Big difference.
 
Peter said:
We get the very same performance when accessing the share via UNC. Whether
I
agree with you or not about mapped vs UNC (I would argue that UNC requires
has more name resolution overhead),
Click to expand...

That name resolution doesn't amount to anything noticable when compared to
the overhead of a mapped drive that maintains a constant connection (till it
times out, and often won't reconnect properly). It can also be elminated by
using the IP# in the UNC path.
the fact remains that many applications do not support UNC partially or at
all.
Click to expand...

Yes, in that case you are stuck with the mapped drive,...but you should
limit mapped drives to only such cases. Keep in mind that it is just the
opposite with Applications that run as a "service",...they can't use mapped
drives,...only UNC paths.
I did, however, found my solution. The issue is described in KB328890.
Adding a
TcpAckFrequency variable on the XP SP2 workstations dramtically sped up
performance. Apparently in XP and 2003 changes were made in TCPIP that
delays
TCP acknowledgements to reduce network traffic. The reg setting forces XP
to
acknoweledge every packet. Big difference.
Click to expand...

That's fine, no problem, and you should do that in places where you are
forced to use mapped drives,...but you should work to eliminated them
wherever possible.
 
Back
Top