On Thu, 2007-04-26 at 10:01 -0700, James D. Parra wrote: > Thanks for the info. I pinged the server from two different test boxes on > the same subnet, which did not get any response, however arp on the test > boxes did return a response showing the IP address and the mac address of > the server having problems. I might add that no other service, ssh, telnet, > traceroute, etc, can get to the server either. > /sbin/arp or arp -a on Windows shows just contents of cache table on the machine you operated the command. It doesn't send any packets at the time. When you ping the server first time by its IP address the machine broadcasts ARP request to LAN to get the MAC address of the destination. It caches on the memory for a limited duration of time to avoid another broadcast when it needs to send another packet to the same destination.
Anyhow, you proved all the hardware NIC, Eth Switch, cables, or whatever inbetween are good. Because the server responded its MAC address to the device you pinged from. So, something on the server is preventing from accepting ping packets from outside, or just ignoring. 90% of the times it's caused by firewall setting at the server. Something must have gotten changed recently. Whatever the trigger was, like online updates. I'm actually not a specialist for firewall setting or that kind of stuff. Please get help from somebody else from here. Toshi -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
