The KN8164V features HD resolution of 1920 x 1200, FIPS 140-2 with level 1 security standards and virtual media transmissions at twice the speed. Built for reliability, the KN series provides local console and remote over IP access, ensuring 24/7 availability to all servers.
COURSE of the MONTH
8 days, 14 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
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
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
For Sennheiser, comfort, quality and security are high priority areas. This paper addresses the security of Bluetooth technology and the supplementary security that Sennheiser’s Contact Center and Office (CC&O) headsets provide.
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
This Micro Tutorial will teach you how to the overview of Microsoft Security Essentials. This is a free anti-virus software that guards your PC against viruses, spyware, worms, and other malicious software.
This will be demonstrated using Windows…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually.
After setting up a router, find the network security…
Suggested Courses
Course of the Month8 days, 14 hours left to enroll
765 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.