csalerno
asked on
Slow performance bewteen Windows 7 64 and Server 2003
I have a networked Windows 7 64 desktop workstation on a Gigabyte network connection with a Dell SC 1430 Server 2003 which is the Domain Controller. The server simply provides file & print services as well as a SQL Server 2008 R2 instance. Starting about two months ago, performance thru my SQL Client app and File Explorer has been terrible. I have search the internet until blue and the few things I have found, have not affected the performance either way. I have a Windows 7 x86 Laptop that connects to the same network on a 10/100 nic and there is not a performance problem.
I have tried:
- Disabling the Background intelligent transfer service
- netsh interface tcp set global autotuninglevel=disabled
- Disabling the IPV6 interface
- Turning off the LLMNR protocol via the GPEdit.msc
I did see a couple of notes out there of some people just reinstalling Windows 7 and the problem went away until the Windows Update brought the install up to date.
Anyone have any ideas on how to fix this?
I have tried:
- Disabling the Background intelligent transfer service
- netsh interface tcp set global autotuninglevel=disabled
- Disabling the IPV6 interface
- Turning off the LLMNR protocol via the GPEdit.msc
I did see a couple of notes out there of some people just reinstalling Windows 7 and the problem went away until the Windows Update brought the install up to date.
Anyone have any ideas on how to fix this?
ASKER
Checked both the Desktop Windows 7 64 and Server nic, both are up to date and set to Auto on the Duplex. Didn't see a setting on the Linksys EA2700.
Linksys EA2700 should be auto by default.
I would down load iperf and set it up and test connections just to eliminate infrastructure.
http://www.wlanpros.com/wp-content/uploads/2011/02/How-to-Guide-on-JPerf-and-IPerf1.pdf
http://sourceforge.net/projects/iperf/
http://sourceforge.net/projects/jperf/
Post results.
I would down load iperf and set it up and test connections just to eliminate infrastructure.
http://www.wlanpros.com/wp-content/uploads/2011/02/How-to-Guide-on-JPerf-and-IPerf1.pdf
http://sourceforge.net/projects/iperf/
http://sourceforge.net/projects/jperf/
Post results.
ASKER
Is there any "already compiled" versions of this?
Pretty simple
Copy iperf into it's own directory
open up command line in windows and change to that directory
To set up one as server
iperf -s then enter
To set up one as client
iperf -c (the iperf server IP address)
It will then give you speed of the connections.
Copy and paste it into this thread.
Copy iperf into it's own directory
open up command line in windows and change to that directory
To set up one as server
iperf -s then enter
To set up one as client
iperf -c (the iperf server IP address)
It will then give you speed of the connections.
Copy and paste it into this thread.
ASKER
It has to be built. Don't have a C development environment. Will take a while.
ASKER
Don't have the compiler for this project. This does not look like an option unless you can direct me to the application exe.
ASKER
I finally found a compiled version of the program and ran from my client and got the following:
H:\iPerf\jperf-2.0.2\bin>i perf -c 192.168.2.107
connect failed: Connection refused
192.168.2.107 is the ip of my Server 2003
H:\iPerf\jperf-2.0.2\bin>i
connect failed: Connection refused
192.168.2.107 is the ip of my Server 2003
ASKER
OK, I figured it out. here is what I got from the default config. Let me know if you need further configuration.
bin/iperf.exe -c 192.168.2.107 -P 1 -i 1 -p 5001 -f k -t 10
-------------------------- ---------- ---------- ---------- ----
Client connecting to 192.168.2.107, TCP port 5001
TCP window size: 8.00 KByte (default)
-------------------------- ---------- ---------- ---------- ----
[156] local 192.168.2.116 port 5323 connected with 192.168.2.107 port 5001
[ ID] Interval Transfer Bandwidth
[156] 0.0- 1.0 sec 48.0 KBytes 393 Kbits/sec
[156] 1.0- 2.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 2.0- 3.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 3.0- 4.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 4.0- 5.0 sec 8.00 KBytes 65.5 Kbits/sec
[156] 5.0- 6.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 6.0- 7.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 7.0- 8.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 8.0- 9.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 9.0-10.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 10.0-11.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 11.0-12.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 12.0-13.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 13.0-14.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 0.0-14.0 sec 64.0 KBytes 37.4 Kbits/sec
bin/iperf.exe -c 192.168.2.107 -P 1 -i 1 -p 5001 -f k -t 10
--------------------------
Client connecting to 192.168.2.107, TCP port 5001
TCP window size: 8.00 KByte (default)
--------------------------
[156] local 192.168.2.116 port 5323 connected with 192.168.2.107 port 5001
[ ID] Interval Transfer Bandwidth
[156] 0.0- 1.0 sec 48.0 KBytes 393 Kbits/sec
[156] 1.0- 2.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 2.0- 3.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 3.0- 4.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 4.0- 5.0 sec 8.00 KBytes 65.5 Kbits/sec
[156] 5.0- 6.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 6.0- 7.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 7.0- 8.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 8.0- 9.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 9.0-10.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 10.0-11.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 11.0-12.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 12.0-13.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 13.0-14.0 sec 0.00 KBytes 0.00 Kbits/sec
[156] 0.0-14.0 sec 64.0 KBytes 37.4 Kbits/sec
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It came back with:
C2S Throughput Test FAILED!
running 10s inbound test (server to client) Protocol Error
Does that narrow it down?
C2S Throughput Test FAILED!
running 10s inbound test (server to client) Protocol Error
Does that narrow it down?
I would run the ndt test on all of the affected units and see if the fail in the same way.
If they do ,then you know it's either the router or ISP.
Also ,in the statistics tab,post those results.
Want to make sure there are no wiring issues.
If they do ,then you know it's either the router or ISP.
Also ,in the statistics tab,post those results.
Want to make sure there are no wiring issues.
ASKER
the screen doesn't allow me to copy\paste even though it states to copy use CTRL C.
What NDT test are you referring too?
What NDT test are you referring too?
That's a java security thing these days.
Can you use the snipping tool in W7 to copy and paste the messages?
Can you use the snipping tool in W7 to copy and paste the messages?
ASKER
The 7 box looks fine.
What about the server 2003 box?
What about the server 2003 box?
ASKER
Attached.
Server-Stats.GIF
Server-Stats.GIF
ASKER
Whoa!
Looks like a bad duplex thing on the W7.
Note the up and down speed of the server is around 5 megabits and the outbound speed on the W7 is 205 k and about 5 megabits down..
Are you running SDSL?
Something not right there.
Looks like a bad duplex thing on the W7.
Note the up and down speed of the server is around 5 megabits and the outbound speed on the W7 is 205 k and about 5 megabits down..
Are you running SDSL?
Something not right there.
ASKER
Not sure about the SDSL, where would I check to find out?
ASKER
I'm using Time-Warner business class internet service, but my problem is strictly on the LAN side.
DSL comes in a number of flavors when it comes to the internet ,
Asymmetric DSL is cheaper,but is faster down than it is up .
Symmetric DSL is the same speed up and down.
Usually more expensive
When I saw the first W7 capture I thought it was ADSL 384 up and 5 down.
But the server shows same up and down,so something is misconfigured.
Asymmetric DSL is cheaper,but is faster down than it is up .
Symmetric DSL is the same speed up and down.
Usually more expensive
When I saw the first W7 capture I thought it was ADSL 384 up and 5 down.
But the server shows same up and down,so something is misconfigured.
> but my problem is strictly on the LAN side.
The W7 capture is showing a duplex issue that affects it's performance on the network in general.
Doesn't matter if it's LAN or WAN ,it's dropping packets.
The W7 capture is showing a duplex issue that affects it's performance on the network in general.
Doesn't matter if it's LAN or WAN ,it's dropping packets.
ASKER
What do you suggest?
Attached are screen shots of the Status screen on the Linksys.
Router-Wireless.GIF
Router-WAN.GIF
Router-Ports.GIF
Router-Lan.GIF
Attached are screen shots of the Status screen on the Linksys.
Router-Wireless.GIF
Router-WAN.GIF
Router-Ports.GIF
Router-Lan.GIF
ASKER
This is from the laptop running Win 7 32bit going thru the same Linksys to the Server 2003.
Does this mean that the problem is with the Win 7 64?
bin/iperf.exe -c 192.168.2.107 -P 1 -i 1 -p 5001 -f k -t 10
-------------------------- ---------- ---------- ---------- ----
Client connecting to 192.168.2.107, TCP port 5001
TCP window size: 8.00 KByte (default)
-------------------------- ---------- ---------- ---------- ----
[128] local 192.168.2.117 port 54269 connected with 192.168.2.107 port 5001
[ ID] Interval Transfer Bandwidth
[128] 0.0- 1.0 sec 10472 KBytes 85787 Kbits/sec
[128] 1.0- 2.0 sec 9872 KBytes 80871 Kbits/sec
[128] 2.0- 3.0 sec 10256 KBytes 84017 Kbits/sec
[128] 3.0- 4.0 sec 10256 KBytes 84017 Kbits/sec
[128] 4.0- 5.0 sec 9912 KBytes 81199 Kbits/sec
[128] 5.0- 6.0 sec 9840 KBytes 80609 Kbits/sec
[128] 6.0- 7.0 sec 9824 KBytes 80478 Kbits/sec
[128] 7.0- 8.0 sec 9824 KBytes 80478 Kbits/sec
[128] 8.0- 9.0 sec 9008 KBytes 73794 Kbits/sec
[128] 9.0-10.0 sec 10080 KBytes 82575 Kbits/sec
[128] 0.0-10.0 sec 99352 KBytes 81376 Kbits/sec
Done.
Does this mean that the problem is with the Win 7 64?
bin/iperf.exe -c 192.168.2.107 -P 1 -i 1 -p 5001 -f k -t 10
--------------------------
Client connecting to 192.168.2.107, TCP port 5001
TCP window size: 8.00 KByte (default)
--------------------------
[128] local 192.168.2.117 port 54269 connected with 192.168.2.107 port 5001
[ ID] Interval Transfer Bandwidth
[128] 0.0- 1.0 sec 10472 KBytes 85787 Kbits/sec
[128] 1.0- 2.0 sec 9872 KBytes 80871 Kbits/sec
[128] 2.0- 3.0 sec 10256 KBytes 84017 Kbits/sec
[128] 3.0- 4.0 sec 10256 KBytes 84017 Kbits/sec
[128] 4.0- 5.0 sec 9912 KBytes 81199 Kbits/sec
[128] 5.0- 6.0 sec 9840 KBytes 80609 Kbits/sec
[128] 6.0- 7.0 sec 9824 KBytes 80478 Kbits/sec
[128] 7.0- 8.0 sec 9824 KBytes 80478 Kbits/sec
[128] 8.0- 9.0 sec 9008 KBytes 73794 Kbits/sec
[128] 9.0-10.0 sec 10080 KBytes 82575 Kbits/sec
[128] 0.0-10.0 sec 99352 KBytes 81376 Kbits/sec
Done.
ASKER
I swapped out the network cable between the Win7 64 and Linksys and now performance is back to normal.
Thanks for all your help.
bin/iperf.exe -c 192.168.2.107 -P 1 -i 1 -p 5001 -f m -t 20
-------------------------- ---------- ---------- ---------- ----
Client connecting to 192.168.2.107, TCP port 5001
TCP window size: 0.01 MByte (default)
-------------------------- ---------- ---------- ---------- ----
[156] local 192.168.2.116 port 6628 connected with 192.168.2.107 port 5001
[ ID] Interval Transfer Bandwidth
[156] 0.0- 1.0 sec 3.88 MBytes 32.5 Mbits/sec
[156] 1.0- 2.0 sec 3.90 MBytes 32.7 Mbits/sec
[156] 2.0- 3.0 sec 3.95 MBytes 33.2 Mbits/sec
[156] 3.0- 4.0 sec 4.19 MBytes 35.1 Mbits/sec
[156] 4.0- 5.0 sec 4.12 MBytes 34.5 Mbits/sec
[156] 5.0- 6.0 sec 4.04 MBytes 33.9 Mbits/sec
[156] 6.0- 7.0 sec 3.99 MBytes 33.5 Mbits/sec
[156] 7.0- 8.0 sec 4.53 MBytes 38.0 Mbits/sec
[156] 8.0- 9.0 sec 4.04 MBytes 33.9 Mbits/sec
[156] 9.0-10.0 sec 4.22 MBytes 35.4 Mbits/sec
[156] 10.0-11.0 sec 4.17 MBytes 35.0 Mbits/sec
[156] 11.0-12.0 sec 4.16 MBytes 34.9 Mbits/sec
[156] 12.0-13.0 sec 3.62 MBytes 30.3 Mbits/sec
[156] 13.0-14.0 sec 4.37 MBytes 36.6 Mbits/sec
[156] 14.0-15.0 sec 4.30 MBytes 36.1 Mbits/sec
[156] 15.0-16.0 sec 4.33 MBytes 36.3 Mbits/sec
[156] 16.0-17.0 sec 4.30 MBytes 36.0 Mbits/sec
[156] 17.0-18.0 sec 4.42 MBytes 37.1 Mbits/sec
[156] 18.0-19.0 sec 4.20 MBytes 35.3 Mbits/sec
[156] 19.0-20.0 sec 4.28 MBytes 35.9 Mbits/sec
[ ID] Interval Transfer Bandwidth
[156] 0.0-20.0 sec 83.0 MBytes 34.8 Mbits/sec
Done.
Thanks for all your help.
bin/iperf.exe -c 192.168.2.107 -P 1 -i 1 -p 5001 -f m -t 20
--------------------------
Client connecting to 192.168.2.107, TCP port 5001
TCP window size: 0.01 MByte (default)
--------------------------
[156] local 192.168.2.116 port 6628 connected with 192.168.2.107 port 5001
[ ID] Interval Transfer Bandwidth
[156] 0.0- 1.0 sec 3.88 MBytes 32.5 Mbits/sec
[156] 1.0- 2.0 sec 3.90 MBytes 32.7 Mbits/sec
[156] 2.0- 3.0 sec 3.95 MBytes 33.2 Mbits/sec
[156] 3.0- 4.0 sec 4.19 MBytes 35.1 Mbits/sec
[156] 4.0- 5.0 sec 4.12 MBytes 34.5 Mbits/sec
[156] 5.0- 6.0 sec 4.04 MBytes 33.9 Mbits/sec
[156] 6.0- 7.0 sec 3.99 MBytes 33.5 Mbits/sec
[156] 7.0- 8.0 sec 4.53 MBytes 38.0 Mbits/sec
[156] 8.0- 9.0 sec 4.04 MBytes 33.9 Mbits/sec
[156] 9.0-10.0 sec 4.22 MBytes 35.4 Mbits/sec
[156] 10.0-11.0 sec 4.17 MBytes 35.0 Mbits/sec
[156] 11.0-12.0 sec 4.16 MBytes 34.9 Mbits/sec
[156] 12.0-13.0 sec 3.62 MBytes 30.3 Mbits/sec
[156] 13.0-14.0 sec 4.37 MBytes 36.6 Mbits/sec
[156] 14.0-15.0 sec 4.30 MBytes 36.1 Mbits/sec
[156] 15.0-16.0 sec 4.33 MBytes 36.3 Mbits/sec
[156] 16.0-17.0 sec 4.30 MBytes 36.0 Mbits/sec
[156] 17.0-18.0 sec 4.42 MBytes 37.1 Mbits/sec
[156] 18.0-19.0 sec 4.20 MBytes 35.3 Mbits/sec
[156] 19.0-20.0 sec 4.28 MBytes 35.9 Mbits/sec
[ ID] Interval Transfer Bandwidth
[156] 0.0-20.0 sec 83.0 MBytes 34.8 Mbits/sec
Done.
That includes the switch if it has manual duplex settings.
Make sure all of the nic drivers are up to date.