Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Question about ping loss

Original Message
Name: masterpom
Date: May 11, 2008 at 05:48:32 Pacific
Subject: Question about ping loss
OS: RHEL AS release 4
CPU/Ram: 2GB
Comment:
Hello, I have been tackling this mystery for
quite some time, and wonder if anyone can give
me an advise.

I am pinging as shown below.(Intranet Network)

$ ping 10.84.81.81
PING 10.84.81.81 (10.84.81.81) 56(84) bytes of data.
64 bytes from 10.84.81.81: icmp_seq=0 ttl=128 time=1.44 ms

And when I change the packet size to 1459(1487)bytes - 1472(1500)bytes, the packet loss occurs.

ping -s 1459 10.84.81.81
PING 10.84.81.81 (10.84.81.81) 1459(1487) bytes of data.

--- 10.84.81.81 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

Is there any reason for this? I had searched through webs but no luck.


Report Offensive Message For Removal


Response Number 1
Name: guapo
Date: May 11, 2008 at 05:58:10 Pacific
Subject: Question about ping loss
Reply: (edit)
There could be an MTU set on the router or it could be that the NIC can't handle that size packet. MTU is Maximum Transmission Unit.

I just checked mine and I start to lose it at 1473.


Report Offensive Follow Up For Removal

Response Number 2
Name: masterpom
Date: May 11, 2008 at 06:14:06 Pacific
Subject: Question about ping loss
Reply: (edit)
Hello Guapo

Hmm,,, could this be a recieving side NIC which
can not handle that packet size? Or a Sender
side which can not handle it packet size.

This mystery is starting to ick me all day
along. Thanks for your advise!


Report Offensive Follow Up For Removal

Response Number 3
Name: guapo
Date: May 11, 2008 at 13:32:13 Pacific
Subject: Question about ping loss
Reply: (edit)
I just tried to ping a different PC on my network, using 1473 and it responded. In my case it's the receiving side that can't handle the packet size.

Report Offensive Follow Up For Removal

Response Number 4
Name: masterpom
Date: May 11, 2008 at 15:48:47 Pacific
Subject: Question about ping loss
Reply: (edit)
Hello Guapo

Hmm,,, It seem for me that from the LINUX
Machine to Windows Machine, the ping fails
from a 1459(1487)bytes - 1472(1500)bytes.

But from Windows Machine to a LINUX machine,
the above test sizes are okay.

I had again searched through the webs but no
source had provided me the ideas or hint for
this matter. Probably not a big deal but this
mystery is killing me, I tell ya.


Report Offensive Follow Up For Removal

Response Number 5
Name: uselessmitch
Date: May 11, 2008 at 18:28:00 Pacific
Subject: Question about ping loss
Reply: (edit)
I could be wrong ( which I probably am) but I believe that the windows nic doesnt support that kind of payload.

I also believe it has something to do with a icmp echo packet vs a tcp packet.

when data is transfered the mtu breaks up the packet.

I believe a echo packet doesnt support that? But I could be wrong

http://mike.passwall.com/networking...


http://www.networksorcery.com/enp/p...


Report Offensive Follow Up For Removal


Response Number 6
Name: guapo
Date: May 12, 2008 at 05:55:12 Pacific
Subject: Question about ping loss
Reply: (edit)
As I said, my own testing shows that it's the receiving side that determines the success or failure. For me, it was the other way around. The FreeBSD box failed on the receiving side and the Windows box answered the higher ping.

I did all pings from and XP box.
XP to FreeBSD didn't answer a ping with 1473 or higher.

XP to a Windows 2000 box had no problem.

I still think it's the NIC and not the OS that makes or breaks it.


Report Offensive Follow Up For Removal

Response Number 7
Name: masterpom
Date: May 12, 2008 at 07:21:51 Pacific
Subject: Question about ping loss
Reply: (edit)
uselessmitch-san, Guapo-san

Thanks for a wonderful Reply!

I am still trying to figure but the information
presented are great. I am currently checking if
the NIC model might have to with this.

And also studying the ICMP role and such,,,

Hopefully I can clear up this mystery one day.


Report Offensive Follow Up For Removal

Response Number 8
Name: guapo
Date: May 13, 2008 at 06:30:19 Pacific
Subject: Question about ping loss
Reply: (edit)
I wouldn't go too crazy but if you want to know more, search google for network card MTU.

Report Offensive Follow Up For Removal

Response Number 9
Name: OrionCA
Date: May 13, 2008 at 13:19:33 Pacific
Subject: Question about ping loss
Reply: (edit)
The MTU is the maximum packet size the unit can send or receive w/o fragmentation. If the receiver can't accept the packet size it make ignore it (older device) or send a response telling the sender to retransmit the portion of the packet that it couldn't read. As a rule most Internet devices default to an MTU of about 1473 so this is the maximum packet size you should transmit. As I said, modern devices *may* warn the sending device to reduce its MTU dynamically, and most new devices automatically comply. If you start losing packets mysteriously you may have to hunt and peck for an MTU that works.

Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Question about ping loss

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




CPU and Graphics Upgrade Questions

VIRUS ALERT in Taskbar, HELP!

DSHUB24 Connection Problems

need help with dsl and dial up

novel 3.12


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC