The AS400 command is a little bit different that DOS.
AS400 command:<b> PING RMTSYS(usrias01) </b> if you type PING and press F4 you’ll see additional parameters as well.
If you find you still can’t ping your server try using the trace route command.
That should help you find the failure. Perhaps there’s an issue with your network and you don’t know what hop it’s on. The trace route will help you locate the failure.
<b>If your issue is orginating on a PC.. Then the above commands won’t help you.</b>
Try flushing your DNS cache: CMD:<b> IPCONFIG /FLUSHDNS</b>
Then try to ping the server again by name.
If that fails try to ping the server by IP address.
From a Windows CMD prompt use the command <b>TRACERT usrias01</b>
The output will display the network hops and list the IP addresses and response times.
With the<b> Trace Route results</b> either from PC or AS400… Take those results to your network admin. By knowing the last good hop of the route and the hop that’s failing you should be able to identify what segment of the network is failing. If you make it all the way to the final hop to the switch housing the AS400 then you may have a faulty port, bad cable, or server issue.
Do you know the real IP address of the<b> <i>usrias01</i></b> server?
Please try to ping that server by it’s IP address.
If the result is ok, i.e. you have a real response form the server, the problem might be in DNS. The DNS server can have no host configured with that name, or it might be mispelled. It can also be the machine you’re using to test this is not using the right DNS server…
If you ping that server by it’s IP address and even so you can’t get any reply from it, the problem might be a firewall, router ACL, etc preventing it form receiving ping’s or answering ICMP echo requests (answer the ping command)
Please post back any update.