asked on
Slow connection to share folder on new pc
i replaced an old workstation and copied over the folders that were being shared. after copying them over to the new pc i shared the folder. I then mapped the other computers to this share.
When opent he share it takes a really long time to load the contect of the share and then when we open a word file, make changes to it and save it, it takes a really long time.
This is what we have in the environemnt:
"server"
optiplex3010 win 7 64-bit - \\computername\beth
This where a ll compiters are mapped to.
When opent he share it takes a really long time to load the contect of the share and then when we open a word file, make changes to it and save it, it takes a really long time.
This is what we have in the environemnt:
"server"
optiplex3010 win 7 64-bit - \\computername\beth
This where a ll compiters are mapped to.
Wireless NetworkingWindows 7
Last Comment
dscla
ASKER
pings are normal. I noticed that if we open a .pdf .docx or .xlsx file speeds are fine.if we open a .doc file file opens up really slow.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ping x.x.x.x -l 65500
-l (small letter L)
C:\Users\Computer>ping 172.16.57.25 -l 1000
Pinging 172.16.57.25 with 1000 bytes of data:
Reply from 172.16.57.25: bytes=1000 time=3ms TTL=64
Reply from 172.16.57.25: bytes=1000 time=2ms TTL=64
Reply from 172.16.57.25: bytes=1000 time=2ms TTL=64
Reply from 172.16.57.25: bytes=1000 time=2ms TTL=64
Average response time for 32 bytes should be 1ms
C:\Users\Computer>ping 172.16.57.25 -l 1000
Pinging 172.16.57.25 with 1000 bytes of data:
Reply from 172.16.57.25: bytes=1000 time=3ms TTL=64
Reply from 172.16.57.25: bytes=1000 time=2ms TTL=64
Reply from 172.16.57.25: bytes=1000 time=2ms TTL=64
Reply from 172.16.57.25: bytes=1000 time=2ms TTL=64
If not, try resetting the NIC on the computer
This was from another solution in Experts Exchange (I don't remember the actual link)
1: Make sure NIC drivers are up to date and that you only one active NIC.
2: On Nic from admin command run the following:
netsh int ip set global taskoffload=disabled
netsh int tcp set global congestion=none
netsh int tcp set global autotuning=disabled
netsh int tcp set global rss=disabled
4: Remove all ghost network cards:
Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
.At a command prompt, type the following command , and then press ENTER:
set devmgr_show_nonpresent_dev
Type the following command a command prompt, and then press ENTER:
start devmgmt.msc
Show hidden devices in menu
Uninstall all greyed out NIC cards.
5: In advanced NIC properties make sure your server NIC is first in line.