What makes you think this is an issue on IBM i? Since this is a network issue, there are a lot of 'pieces' involved, network cards, cables, switches, routers, firewalls and possibly other things, depending on your network.

My approach to troubleshooting something like this is to try to isolate where it's failing by systematically testing each 'piece' that are in the equation.

Also, a lot of shops use firewalls that block PING (aka ICMP echo requests) because it can be used for a denial-of-service attack. Or, at least, this was commonplace years back. You should not rely on PING as your only way of testing connectivity.


On 11/18/2015 1:08 PM, Rob Dixon wrote:
I have a V5R1 system and a V5R3 system on the same network and they have
worked fine for several years. I have been able to access them both from
several PCs using client access. I have been able map network drives to
them both.I have been able to ping them both from PCs. Now I can access
only the V5R1 system from a PC. The V5R3 system looks fine through a
terminal yet I cannot ping the it from a PC yet I can ping it within client
access running on the same PC. I am not sure what I have done but probably
something stupid. Netstat on the V5R3 system shows the Interface as active.
I have tried enough times to be fairly sure that it isn't a simple typing
error.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].