Irene Xie wrote:
>Hi, Ticker,
>
>Thank you for your email and attention. I did take a look at the MTU stuff,
>since it is a new stuff for me, and it requires to change the register file,
>I hesitate to change it now and I will need more time to read the material
>before I do the changes. I was too busy to do that part. Seems that is the
>only part that I didn't get a chance to try yet. I will do that maybe late
>today or tomorrow since the machine is at my home.
>
>Since you did that before, I would like to ask you some special questions
>about the MTU. What is the range of the XXXX number that you use to ping,
>1464 and lower? Does that mean 1464 to 1? Should I try 1464 then 1463 and
>....to 1 or there is some trick that I can follow?
>
>Thank you again and have a nice day!
>
>
>Irene
>
>
>
>-----Original Message-----
>From: ticker [mailto:[EMAIL PROTECTED]]
>Sent: Monday, September 16, 2002 9:12 AM
>To: Irene; [EMAIL PROTECTED]
>Subject: Re: help with network problem
>
>
>Hi Irene...
>Someone mentioned earlier that your MTU might be too big, did you
>try to change it ? I had same kind of problems earlier and by changing
>the MTU to a smaller value, I was able to fix this problem.
>
>You can determine the MTU by doing:
>
>ping -f -l xxxx IP/name of the webserver that you are trying to access.
>For xxxx, start with 1464 and lower the number until you get a reply.
>Then add 28 to the highest number at which you get a reply.
>The result is the MTU that you should change to.
>
>/Jani
>
>
>
>
>
>
>
Just found this post and actually sounds quite weird. A connection lost
should seem that the first handshake passes and then for one reason it
times out or whatever (as Mr Burton implies). Is it possible to tell me
what site we r talking about ??? What connection type do you have ( for
example a adsl using pppoe will use such mtu's in 1400 range due to
overhead and depending on the connection software)? MTU might be a
problem but shouldnt give such error due to fragmenting and TCP should
resend. ( If it is TCP we are talking about off course). Other things
that might give such error are for example a connection killer. Someone
just wants to fool around and kills the connection to a given port on a
given server. Arp spoofing or double ip addresses on a LAN etc.
As i said i just got these so i dont really know every detail of the
problem so if someone could resend i can do a quick check :) .
Cya
