connection reset by server

[Jay Daniels]

David Curtis wrote:
> On Tue, 30 Jun 2009 20:39:39 -0400
> Jay Daniels <jaydanie at gmail.com> wrote:
> 
>> Seems to only happen on certain sites repeatedly at times and at
>> random. However, while browsing using hardy and firefox I've been
>> getting a lot of these.
>>
>> Connection reset by server...
>>
>> Shoddy satellite connection; however, I was wondering if there is an
>> MTU or some other setting on the Linksys I could set to get rid of
>> this problem?  I believe it set to standard 1500.
> 
> 1500 is the standard for ethernet. But you haven't stated what type of
> protocol your satellite connection uses for IP encapsulation. If your
> using PPPoE the standard MTU is 1492. This allows 8 bytes of PPP
> overhead. If between you and the ISP, ATM or another type of packet/cell
> based protocol is used the MTU can be set lower to avoid IP
> fragmentation which, yes, can produce the symptoms you are suffering. My
> ISP uses ATM from dsl modem to dslam and negotiates on connection with
> an MTU of 1460. Why 1460? I could not tell you. But I do trust my ISPs
> knowledge.
> 
> If you really think the MTU is the issue, most definitely have a chat
> with a _good_ tech at your ISP.  
> 

I read somewhere you could use ping to test.  With the latency on 
satellite, ping not working so well.

jay at my-t60:~$ nslookup www.ubuntu.com
Server:		75.104.96.61
Address:	75.104.96.61#53

Non-authoritative answer:
Name:	www.ubuntu.com
Address: 91.189.94.9

jay at my-t60:~$ ping www.ubuntu.com
PING www.ubuntu.com (91.189.94.8) 56(84) bytes of data.
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=1 ttl=40 
time=1570 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=2 ttl=40 
time=1733 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=3 ttl=40 
time=1459 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=4 ttl=40 
time=1518 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=5 ttl=40 
time=3047 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=7 ttl=40 
time=1773 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=6 ttl=40 
time=2773 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=8 ttl=40 
time=1536 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=9 ttl=40 
time=1545 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=10 ttl=40 
time=1520 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=11 ttl=40 
time=1606 ms
64 bytes from jujube.canonical.com (91.189.94.8): icmp_seq=12 ttl=40 
time=3365 ms

--- www.ubuntu.com ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 26558ms
rtt min/avg/max/mdev = 1459.036/1954.209/3365.905/656.721 ms, pipe 4
jay at my-t60:~$

No packet loss, but look how long that took and that's when it's working 
good.


jay