This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.
Solved
Slow connection to share folder on new pc
Posted on 2013-01-07
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.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
5 Comments
Active 3 days ago
Run a ping and see how long it takes to reply
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.
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.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
When you start your Windows 10 PC and got an "Operating system not found" error or just saw "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing. You will be panic as there are no back…
The Windows functions GetTickCount and timeGetTime retrieve the number of milliseconds since the system was started. However, the value is stored in a DWORD, which means that it wraps around to zero every 49.7 days. This article shows how to solve t…
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface.
This will be demonstrated using Windows 7 operating system.
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"!
Step 1: Open a new google tab
Step 2: Go to the left hand upper corn…
Suggested Courses
Course of the Month11 days, 10 hours left to enroll
636 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.