RE: shared networkdrives slow
- From: v-robeli@xxxxxxxxxxxxxxxxxxxx (Robert Li [MSFT])
- Date: Thu, 08 Feb 2007 06:42:03 GMT
Hi,
Thanks for posting in our newsgroup.
From your description, I know that you suffer a very slow connection speedcopying files from Windows XP client to share fold on the SBS 2003. If I am
off-base, please don¡¯t hesitate to let me know.
Please let me know the following information so that we can understand your
situation more clearly:
1. Does the issue occur when you copy a big file or a small one? If you
copy a big file such as 1GB, that will really need some time and cost much
system resource.
2. When you copy a same file to a Windows XP client, does the same problem
occur?
3. Do your SBS server and Windows XP clients locate in the same location?
4. Does the problem occur on all clients or some of them?
Please take the following steps to narrow down this issue:
Step 1: This problem occurs because server message block (SMB) write
operations to a domain controller that is running Windows 2000 or Windows
Server 2003 may experience a delay of up to 200 milliseconds between file
copies.
1. Start Registry Editor on the server.
2. Locate and click the following key in the registry, where Adapter GUID
is the globally unique identifier (GUID) for the network adapter that
connects to the clients:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interf
aces\Adapter GUID
3. On the Edit menu, click Add Value, and then add the following registry
value:
Value name: TcpDelAckTicks
Data type: REG_DWORD
Value data: You can set this value to a range from 0 to 6. The default
setting is 2 (200 milliseconds).
4. Quit Registry Editor.
5. Restart Windows for this change to take effect.
For more information, please refer to:
Slow network performance occurs if you copy files to a domain controller
that is running Windows 2000 or Windows Server 2003
http://support.microsoft.com/kb/321098/
Step 2: This problem may be caused by the architectural behavior of the
Windows Sockets API and Afd.sys.
1. Start Registry Editor on the server.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interf
aces\<Interface GUID>
3. On the Edit menu, point to New, and then click DWORD Value.
4. Name the new value TcpAckFrequency, and assign it a value of 1.
5. Quit Registry Editor.
6. Restart Windows for this change to take effect.
For more information, please refer to:
Slow performance occurs when you copy data to a TCP server by using a
Windows Sockets API program
http://support.microsoft.com/kb/823764/
If the problem still exists, please help me collect the following for
further research:
Please run Network Monitor on the client computer to capture the network
trafic between the client and Windows server 2003. If possible, please
network the two computers with a hub and also shut down other computers on
the network.
1. Go to ftp://ftp.microsoft.com/PSS/Tools/NetMon/ to download the
netmon2.zip in Internet Explorer. Double-click the netmon2.zip file to
extract the files. The password is "trace".
2. Run the qfesetup.EXE and follow the wizard to install the network
monitor.
3. Click Start->Programs->Administrative Tools->Network analysis
Tools->Network Monitor. You are asked to choose an interface. Network
Monitor will capture some packets which pass through this interface. Since
all interfaces are listed as their MAC addresses, it may be difficult for
us to choose a proper interface. You can run the command "ipconfig /all"
under the Command Prompt. This command will list all MAC addresses of all
interfaces. Choose a proper interface. If you need to change an interface,
please choose the "Captures" menu and the "Networks" menu in Network
Monitor.
4. Configure the buffer settings. Choose the "Capture" menu and the "Buffer
Settings" menu. Since we need to capture network packets for a while, I
suggest that you configure large buffer settings, such as 30 MB.
5. Turn on Network Monitor to begin capture.
6. Try to reproduce this problem by copying a file from the client computer
to the SBS 2003. HINT: It is not necessary to copy a large file. If this
problem can be reproduced by copying a file in small size, it is better to
use this file.
7. Switch to Network Monitor after the file is copied to the server. Choose
Capture->"Stop and View" to stop capturing network packets. Click File ->
Save As to save it to a .cap file.
8. Compress the .cap file by right-clicking on the file and select Send To
-> Compressed (Zipped) Folder.
Please send the information to v-robeli@xxxxxxxxxxxxx with subject:37774415
-shared networkdrives slow.
If you need further assistance, please don¡¯t hesitate to let me know.
Best regards,
Robert Li(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
<Thread-Topic: shared networkdrives slow
<thread-index: AcdLE4TOaD8jgJ4wSCuooRw21ZNTfA==
<X-WBNR-Posting-Host: 207.46.198.15
<From: =?Utf-8?B?cm9zdGll?= <rostie@xxxxxxxxxxxxxxxxxxxxxxxxx>
<Subject: shared networkdrives slow
<Date: Wed, 7 Feb 2007 15:56:00 -0800
<Lines: 17
<Message-ID: <F883F8C6-CE5D-4B74-92E0-C2B5B273F8D7@xxxxxxxxxxxxx>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
<Newsgroups: microsoft.public.windows.server.sbs
<Path: TK2MSFTNGHUB02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:15615
<NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<Hey all,
<
<im already a month struggeling to fix this problem. i installed a brand
new
<server with SBS 2003 standard edition mainly for use as a file server.
made 6
<XP workstations join the domain by using the connectcomputer tool. and
since
<then those computers suffer with a very slow connection speed when they
copy
<files to the server shared disk. and this slow copying gets the
workstations
<processor busy 100%.
<
<when i check the server the file is long saved to the shared disk. but the
<workstation is still unavailable.
<
<can someone help me out?
<
<ive been through some posts about this but all this didnt change my
problem.
<ive tried setting the NIC's of both the workstations and the server to 100
<f/d no change. i hooked on another switch no change.
<
.
- Prev by Date: Error: Microsoft Shared Fax Driver not Installed
- Next by Date: RE: Google Desktop Search does not work on client desktops in sbs 2003
- Previous by thread: Error: Microsoft Shared Fax Driver not Installed
- Next by thread: RE: Google Desktop Search does not work on client desktops in sbs 2003
- Index(es):
Relevant Pages
|
