Comments on: SSSLOOOWW network http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/ Mon, 09 Nov 2009 08:28:01 +0000 http://wordpress.org/?v=2.6.2 By: pongapundit http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37365 pongapundit Fri, 08 Apr 2005 07:06:45 +0000 #comment-37365 Since all the hardware seems to be in order, to have your applications running ok, try availaing the service of the vendor who provided the software which is causing problem in the given hardware scenario. Since all the hardware seems to be in order, to have your applications running ok, try availaing the service of the vendor who provided the software which is causing problem in the given hardware scenario.

]]> By: EsterP http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37366 EsterP Fri, 08 Apr 2005 06:31:48 +0000 #comment-37366 I know it's a bit late now but as you have not mentioned anything to do with Novell/IPX in your original query, it never occurred to me that that could be causing it. A few years back we had to uninstall the Novell client and associated ipx/spx services/protocol because it slowed down our network. We have arrived at the conclusion that they are forever polling for connection causing the system to slow down. So now we only have IP especially after we have gotten rid of our Novell servers. I know it’s a bit late now but as you have not mentioned anything to do with Novell/IPX in your original query, it never occurred to me that that could be causing it.

A few years back we had to uninstall the Novell client and associated ipx/spx services/protocol because it slowed down our network. We have arrived at the conclusion that they are forever polling for connection causing the system to slow down. So now we only have IP especially after we have gotten rid of our Novell servers.

]]> By: Howard2nd http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37367 Howard2nd Thu, 07 Apr 2005 14:22:49 +0000 #comment-37367 Followup - I installed an Intel Pro 100 Server card and moved the network connection to that device. 7 hours and counting problem solved. The server only has IP, No Novell, No IPX. the embedded nic was choking on ipx broadcast packets just being discarded. Don't ask me I cannot explain it. Thanks for all your help and suggestions. Followup - I installed an Intel Pro 100 Server card and moved the network connection to that device. 7 hours and counting problem solved.

The server only has IP, No Novell, No IPX. the embedded nic was choking on ipx broadcast packets just being discarded. Don’t ask me I cannot explain it.

Thanks for all your help and suggestions.

]]> By: joelsplace http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37368 joelsplace Thu, 07 Apr 2005 11:31:59 +0000 #comment-37368 I set quite a few computers (XPSP1&2) on a network to 100 full duplex (Dlink Gigabit switches & Dlink Gbit cards in servers)and speed measured from those computers dropped to 1-2Mb. Very slooow. Switched back to auto and it jumped to around 95-97Mb. Weird combo not working you say? I found the same to be the case at another client with all 100Mb cards and Linksys 100Mb switches. I used Qcheck for the speed measurement. I set quite a few computers (XPSP1&2) on a network to 100 full duplex (Dlink Gigabit switches & Dlink Gbit cards in servers)and speed measured from those computers dropped to 1-2Mb. Very slooow. Switched back to auto and it jumped to around 95-97Mb. Weird combo not working you say? I found the same to be the case at another client with all 100Mb cards and Linksys 100Mb switches. I used Qcheck for the speed measurement.

]]> By: NetSteve http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37369 NetSteve Thu, 07 Apr 2005 11:04:34 +0000 #comment-37369 Howard Check the new servers NIC settings, if its on Auto then manually set the NIC to 100 whilst no one is connected to the server. Also check the duplex setting on the old server. A few weeks ago I put in a new cisco 2851 router which can run at gigabit the other router could run at 100. The rule of thumb according to cisco engineers is what ever speed you set on one side to do to the other. Both routers were set to auto and there where connectivity problems but forcing the newer router to 100 solved it. Howard

Check the new servers NIC settings, if its on Auto then manually set the NIC to 100 whilst no one is connected to the server. Also check the duplex setting on the old server.

A few weeks ago I put in a new cisco 2851 router which can run at gigabit the other router could run at 100. The rule of thumb according to cisco engineers is what ever speed you set on one side to do to the other.

Both routers were set to auto and there where connectivity problems but forcing the newer router to 100 solved it.

]]> By: elangeland http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37370 elangeland Thu, 07 Apr 2005 10:22:57 +0000 #comment-37370 PaulieEddie, I have heard the exact opposite. I was told that autonegotiate required both ends to be set to autonegotiate, and that if one device had speed or duplexing set manually, the other end may get the wrong setting during autonegotiation. PaulieEddie, I have heard the exact opposite. I was told that autonegotiate required both ends to be set to autonegotiate, and that if one device had speed or duplexing set manually, the other end may get the wrong setting during autonegotiation.

]]> By: poppaman http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37371 poppaman Thu, 07 Apr 2005 10:08:41 +0000 #comment-37371 Don't know how much help this will be - I have experienced a similar issue, but on a Win2K server/Mac OS network. While checking/setting the speed of the switch port (I'm assuming you are in a switched environment, as the building is six months old....) could be the cause if the issue, I found that a version mismatch between the version of Excel which created the problem file and the version accessing the file caused the opening process to slow or fail. Check the creation type to see if this might be the case... Don’t know how much help this will be - I have experienced a similar issue, but on a Win2K server/Mac OS network. While checking/setting the speed of the switch port (I’m assuming you are in a switched environment, as the building is six months old….) could be the cause if the issue, I found that a version mismatch between the version of Excel which created the problem file and the version accessing the file caused the opening process to slow or fail. Check the creation type to see if this might be the case…

]]> By: bigshybear http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37372 bigshybear Wed, 06 Apr 2005 23:43:10 +0000 #comment-37372 Also check if you have a hub or a switch. I've run into problems where shifting to a faster server slowed the network throughput down because the hub couldn't keep up. Also check if you have a hub or a switch. I’ve run into problems where shifting to a faster server slowed the network throughput down because the hub couldn’t keep up.

]]> By: PaulieEddie http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37373 PaulieEddie Wed, 06 Apr 2005 18:42:37 +0000 #comment-37373 Do you have a switched network? If the switch ports are set to auto-negotiate the speed/duplex, you may need to set the NIC on the server to force it to 100Mb/Full Duplex - expecting that your switch is capable of this. NICs and Switches can't always negotiate well if one or the other isn't set specifically to be a particular speed and duplex. The result is a radical reduction in network performance that manifests itself most notably when large file copies are done. Usually I notice this when we are trying to perform backups over the network and it takes an exceptionally long time. Switching the NIC (or the switch port) fixes the problem. Do you have a switched network? If the switch ports are set to auto-negotiate the speed/duplex, you may need to set the NIC on the server to force it to 100Mb/Full Duplex - expecting that your switch is capable of this. NICs and Switches can’t always negotiate well if one or the other isn’t set specifically to be a particular speed and duplex. The result is a radical reduction in network performance that manifests itself most notably when large file copies are done. Usually I notice this when we are trying to perform backups over the network and it takes an exceptionally long time. Switching the NIC (or the switch port) fixes the problem.

]]> By: bobkberg http://itknowledgeexchange.techtarget.com/itanswers/sssloooww-network/#comment-37374 bobkberg Wed, 06 Apr 2005 17:45:43 +0000 #comment-37374 Have you taken a sniffer trace with a problem child system to see if anything is obvious? Another possible check is to dump the arp cache (arp -a at the command prompt) and look for "Incomplete" arp entries - which indicate that the system is looking for things that don't answer (as a previous poster mentioned with the missing mapped drives). Bob Have you taken a sniffer trace with a problem child system to see if anything is obvious?

Another possible check is to dump the arp cache (arp -a at the command prompt) and look for “Incomplete” arp entries - which indicate that the system is looking for things that don’t answer (as a previous poster mentioned with the missing mapped drives).

Bob

]]>