|
tech
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Throughput problems to W2K3 Servernetwork analysis program called QCheck to measure the throughput and get good results. By this, I mean they are operating at about 100 Mbps. They are GB NICs but not a GB switch and the workstations are not GB either. But from any workstation, they will get good 100 Mbps results. BUT one of the servers will always reply with about 500 kpbs - most of the times it's even about 300 kbps. I switched the NIC to another one, I switched the cables, I ran it through a different switch and different ports on the same switch. I tried putting it into a port another server was using. I keep getting the same results. The server is running a client/server application that is running ridiculously slow over the network - but runs fine ON the server (locally). This is because of the throughput TCP error. UDP throughput will give me about 60 Mbps on this server - which is about the same as the other servers get. What could be causing this speed problem? The Server is also running Pervasive SQL Server, but that doesn't appear to be the problem (turned it off and tested and no difference). The only other "ROLE" the server has is File Sharing - to map a drive to each workstation for the application to run from. These results are from throughput tests from QCheck - not just the application, so I don't think it is that application that's causing problems (ie. copying a file to the server over the network also takes a loooong time). Are there settings I can check for this? Any help is greatly appreciated as I am perplexed. bflounders-it AT @ AT mainlineoncology DOTCOM. I have disabled the Master Broswer service (another server will pick up that
load). And took off the Intelligent Backgorund Updater files from my Backup Exec jobs (they kept giving errors). With some other tweaking of small magnitude, the network check (QCheck) gives me roughlr 40 Mbps. But this number fluctuates. If I run it 10 times in a row, 7 will be 35-40 Mbps. 2 will be ~18 and one will be ~3 Mbps. So its better than 500k, but it's still lagging a lot. What could be the cause of the fluctuations? Thanks. Show quote "Brian Flounders" wrote: > We have several Windows 2003 Servers. Every machine but one, I can run a > network analysis program called QCheck to measure the throughput and get good > results. By this, I mean they are operating at about 100 Mbps. They are GB > NICs but not a GB switch and the workstations are not GB either. But from > any workstation, they will get good 100 Mbps results. BUT one of the servers > will always reply with about 500 kpbs - most of the times it's even about 300 > kbps. I switched the NIC to another one, I switched the cables, I ran it > through a different switch and different ports on the same switch. I tried > putting it into a port another server was using. I keep getting the same > results. The server is running a client/server application that is running > ridiculously slow over the network - but runs fine ON the server (locally). > This is because of the throughput TCP error. UDP throughput will give me > about 60 Mbps on this server - which is about the same as the other servers > get. What could be causing this speed problem? The Server is also running > Pervasive SQL Server, but that doesn't appear to be the problem (turned it > off and tested and no difference). The only other "ROLE" the server has is > File Sharing - to map a drive to each workstation for the application to run > from. These results are from throughput tests from QCheck - not just the > application, so I don't think it is that application that's causing problems > (ie. copying a file to the server over the network also takes a loooong > time). Are there settings I can check for this? Any help is greatly > appreciated as I am perplexed. bflounders-it AT @ AT mainlineoncology DOTCOM. I've seen these kind of speed issues when the duplex is incorrect on
the adapter. If its a stable server and the network switch is full duplex, its worth it to take the adapter off "auto" and put it on 100M duplex. Sounds silly. Usually the last thing you try! Thanks for the answer, JoeV. I did do that already, in attempts to work
around the issue. Both the server and the workststaions have been set to 100 Mbps Full Duplex. This did not improve anything. Any other suggestions? Thanks a lot for replying! Show quote "JoeVolcano" wrote: > I've seen these kind of speed issues when the duplex is incorrect on > the adapter. If its a stable server and the network switch is full > duplex, its worth it to take the adapter off "auto" and put it on 100M > duplex. > > Sounds silly. Usually the last thing you try! > >  |
|||||||||||||||||||||||
Other interesting topics