- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Slow network performance with W2K and NOT XP
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2006 08:04 AM
тАО06-19-2006 08:04 AM
I am starting to do a parallel migration from our legacy network to our new HP network consisting of 2 5406's and 1 3500.
I know this sounds weird, but I am having performance issues with only Windows 2000 SP4 pc's and servers and NOT with Windows XP or Windows Server 2003. When I say performance issues I mean latency. On a 2000 workstation I can ping its local gateway and get <10ms response time. If I do the same thing on WinXp I get <1ms which is what I expect. I've proven this by taking a WinXP machine and plugged it into the same network connection that the W2K pc was using and don't have latency. I even rebuilt the W2K pc with XP and am now getting <1ms response time. On the W2K pc I made sure that the nic drivers were up to date and also tried hard coding the speed/duplex settings on the pc and switch with no luck.
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2006 12:47 PM
тАО06-19-2006 12:47 PM
Re: Slow network performance with W2K and NOT XP
This is just a wild guess, but any chance
the time resolution on the older OS's are
10msec, while the new OS is 1msec ?
Do you see actual performance problems
copying data ? Like if you have a
genuine 10 millisecond per packet delay,
your throughput will be pretty awful,
max 150kilobytes/sec or so.
Director, Network Services
Information Systems and Technology
MC 1018
(519)888-4567 x38323
University of Waterloo, Waterloo, ON
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2006 01:30 PM
тАО06-19-2006 01:30 PM
Re: Slow network performance with W2K and NOT XP
If you run a packet capture you will see the actual response is much quicker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 12:17 AM
тАО06-20-2006 12:17 AM
Re: Slow network performance with W2K and NOT XP
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 01:35 AM
тАО06-20-2006 01:35 AM
Solutionhttp://rdweb.cns.vt.edu/public/notes/win2k-tcpip.htm
The fact that it was running fine on the old network is hard to explain, but I think you should focus on the OS rather than the new network infrastructure.
This application that is suffering, can you share more detail about it?
What about basic file copy tests?
Windows 2000 Server > 2000 client = ?
Windows 2000 Server > XP client = ?
And the same tests for 2003 Server.
For much better throughput testing I would recommend using iperf: http://dast.nlanr.net/Projects/Iperf/
With Windows 2000 you will never see it display less than <10ms, to truly see the ping response you will need to use a packet capture application like Ethereal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2006 03:33 AM
тАО06-20-2006 03:33 AM
Re: Slow network performance with W2K and NOT XP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 07:35 AM
тАО06-21-2006 07:35 AM
Re: Slow network performance with W2K and NOT XP
There are also some XP pc's that again seem pokey when I used their 1000T nic compared to when they were on the 100FX network.
I looked at iperf, but couldn't figure out how to run under windows. Can anyone recommend a windows based tool that will tell me what is going on the new network?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 07:47 AM
тАО06-21-2006 07:47 AM
Re: Slow network performance with W2K and NOT XP
Try to connect all gig NICs to one switch, and all the 100mbps NICs to another (if there is a possibility.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 07:56 AM
тАО06-21-2006 07:56 AM
Re: Slow network performance with W2K and NOT XP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-21-2006 10:47 AM
тАО06-21-2006 10:47 AM
Re: Slow network performance with W2K and NOT XP
server: iperf -s
client: iperf -c
You can set a lot more options if required, the default test is 10 seconds so I increase that to 60 seconds with this:
iperf -c
Looking back at your network, if you do a 'show span', how long ago was your last topology change? If it is in the seconds or even the minutes that is probably going to be your problem. Otherwise look through the port counters to try and see anything unusual there.
Otherwise if you can post a copy of the show tech from the ProCurve switches, it may help (remove any sensitive info, public IP's or SNMP community names).
Make sure you're running K.11.33 on these switches too.