Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We're running a SharePoint 2007 intranet hosted internally.

Whilst sitting at the desk hardwired in the office, browsing/file copying/downloading from the site is acceptable but slow. Pings and Trace routes come back with no extra hops, all under 1ms response times.

If I connect to the standard VPN whilst still in the office and force all traffic over the VPN gateway, speeds of copying files between the Intranet and local machines can almost double.

I'm at a loss as to why this is happening to be honest. Any ideas?

share|improve this question
2  
Use winmtr and look for packet loss to those internal destinations while in the office. –  Mike Pennington Oct 16 '12 at 9:43
    
Both internally and externally produce at most 3% traffic loss so no real difference there unfortunately. –  Mikeysoft Oct 16 '12 at 13:22
    
If you try and download a big file from SharePoint internally, does it download quickly? –  longneck Oct 16 '12 at 16:17
    
Apologies, it was meant to be 0.3% whilst I was testing on a wireless connection. Wired is 0.0% –  Mikeysoft Oct 18 '12 at 11:40

1 Answer 1

Both internally and externally produce at most 3% traffic loss so no real difference there unfortunately

Sustained 3% traffic loss will decimate TCP throughput. You need to fix that, regardless of whether it's on your internet side or corporate network side.

Speaking as a guy who has built networks for the last 20 years, you should never accept significant ongoing packet loss on a wired network, and do not let any equipment vendor or ISP tell you otherwise.

The most I will tolerate for a public internet service on a cable modem (where you expect some loss from occasional oversubscription) is 0.1% over a 24 hour period, and no more than 0.5% over any 5 minute period.

I tolerate 0.0% packet loss on a wired corporate network.

Wifi is a different game; depending on local conditions, you might not be able to demand good performance from it all the time. If your corporate wifi is bad enough to complain on serverfault, reengineer that wireless solution to improve performance or get real a wire.

share|improve this answer
1  
Well said Mike... there should be ZERO packetloss internally. –  SpacemanSpiff Oct 17 '12 at 15:04
    
Apologies, it was meant to be 0.3% whilst I was testing on a wireless connection. Wired is 0.0% –  Mikeysoft Oct 18 '12 at 11:38

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.