Re: Slow copying files from Server to Client
- From: v-robeli@xxxxxxxxxxxxxxxxxxxx (Robert Li [MSFT])
- Date: Mon, 13 Aug 2007 07:46:21 GMT
Hello Kevin,
Thanks for posting in our newsgroup and also for Larry's input.
I am sorry for the delay due to the weekend.
From your description, I know that copying files is very slow from SBSserver to client workstation. If that's not right, please don't hesitate to
let me know.
Please let me know the following to make the situation more clearly:
1. Do you have issue copying files to each workstations or some specific
ones?
2. What's the service pack level of your SBS server?
3. What's the operation system of the problematic workstation?
4. What important change did you made before the problem first occurred?
Please on my research, please take the following steps to narrow down this
issue:
Step1: The problem can be caused by hardware switch. Please take the
following test:
Take a cross over cable and attach the laptop directly to the server's
internal NIC, can the problem be reproduced? If not, the problem is caused
by hardware switch. Please contact the hardware manufacture for more help.
Step 2: Please make a clean boot on both workstation and SBS server to make
sure the problem is not caused third party software:
1. Click Start->Run...->type msconfig and press Enter.
2. Click Services tab and select Hide All Microsoft Services and Disable
All third party Services.
3. Click Startup tab and Disable All startup items.
4. Click OK and choose Restart.
5. After reboot, check whether the problem still occurs.
6. If there are no more problems, please use the above steps to enable
services and startup items one by one in order to figure out the root cause
of this issue.
Step 3: please disable the SMB signing for a test purpose
1. On the SBS server, run "gpmc.msc" and make sure the following policies
(10 in total) are all 'Disable' (instead of 'Not defined') in BOTH 'Default
Domain Security Policy' and 'Default Domain Controller Security Policy':
NOTE: The polices are under 'Windows Settings' -> 'Security Settings' ->
'Local Policies' -> 'Security Options'.
1) Microsoft network client: Digitally sign communications (always):
Disabled
2) Microsoft network client: Digitally sign communications (if server
agrees): Disabled
3) Microsoft network server: Digitally sign communications (always):
Disabled
*** For 'Default Domain Controller Security Policy' was previously enabled
4) Microsoft network server: Digitally sign communications (if client
agrees): Disabled
*** For 'Default Domain Controller Security Policy' was previously enabled
5) Network security: LAN Manager authentication level: Send LM & NTLM - use
NTLMv2 session security if negotiated
*** For 'Default Domain Controller Security Policy' was previously 'Send
NTLM response only'
B. Restart the DC and client computer to take effect.
Step 4: If you have Windows 2003 SP2 installed, please disable RSS and
Checksum offload settings. You can find the detail steps in
http://blogs.technet.com/sbs/archive/2007/03/19/vpn-securenat-nat-and-outloo
k-clients-not-working-after-installing-windows-service-pack-2-in-sbs-2003-pr
emium.aspx
More info:
Windows 2003 service pack 2 known issues on Small Business Server 2003
http://support.microsoft.com/?id=555912
If the problem persists, please help me collect the following for further
research:
1. Run Network Monitor on the SBS server to capture the network trafic
between the client and SBS 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 on the server.
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 (for example a 1MB big
file) from the SBS server to client computer.
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.
NOTE: Please let me know the IP address of the client and the server.
2. MPS-Report on SBS server
1) Download MPSreport_network from
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE
2) Run MPSRPT_NETWORK.exe on the server box.
3) The tool will automatically collect the information. This procedure will
take 10~15 minutes.
4) Open Windows Explorer, navigate to the folder:
%SystemRoot%\MPSReports\Network\Reports\Cab\
5) Send the .cab file directly to v-robeli@xxxxxxxxxxxxx with subject:
40138778-Slow copying files from Server to Client.
I am looking forward to hear from you.
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.
--------------------
<From: "Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com>
<References: <EAD3F597-10F0-4EB7-94CD-9B28C53C4E33@xxxxxxxxxxxxx>
<Subject: Re: Slow copying files from Server to Client
<Date: Fri, 10 Aug 2007 08:42:07 -0400
<Lines: 35
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
<X-RFC2646: Format=Flowed; Original
<Message-ID: <#N#2Uu02HHA.4476@xxxxxxxxxxxxxxxxxxxx>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: pool-71-101-190-120.tampfl.dsl-w.verizon.net
71.101.190.120
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:55721
<X-Tomcat-NG: microsoft.public.windows.server.sbs
<
<Hi Kevin:
<
<You did not say if all workstations are affected?
<
<Possible fixes:
<
<Network Cards.. drivers and speed settings. This can sometimes be cured
by
<setting all the nics to the same speed and duplex setting rather that auto.
<
<SMB Signing
<
<Anti Virus
<
<Drive Failing on Server or other storage sub system issues.
<
<and of course, the ever popular:
<
<You may experience network-related problems after you install Windows
Server
<2003 SP2 or the Scalable Networking Pack on a Windows Small Business Server
<2003-based computer that has an advanced network adapter
<http://support.microsoft.com/kb/936594/en-us
<
<Larry
<
<"Kevin" <Kevin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
<news:EAD3F597-10F0-4EB7-94CD-9B28C53C4E33@xxxxxxxxxxxxxxxx
<> There seems to be an issue copying files from
<> server to client. Client to client is fine @ about 95Mbps, Client
<> to server is also 95Mbps but server to client is like 20Kbps. There
<> is something wrong. We have tried the latest NIC drivers, etc.
<>
<> Any Ideas?
<> Kevin
<
<
<
.
- References:
- Re: Slow copying files from Server to Client
- From: Larry Struckmeyer
- Re: Slow copying files from Server to Client
- Prev by Date: RE: Access Permissions
- Next by Date: RE: SBS 2003 with Multiple Sites
- Previous by thread: Re: Slow copying files from Server to Client
- Next by thread: Re: Fail in replication between new Win2k3 Std and SBS2K3 with TP
- Index(es):
Relevant Pages
|
