RE: TELNET trouble shooting

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

If you have a console you can end TCP/IP and restart it. But if you don't
have a console (there are reasons, albeit not good ones), then you have to
IPL and hope that TCP/IP is set up to start automatically.

Testing TCP/IP

First thing - try to ping the address in question.
   - In general, with ping, start with the address on the network that is
closest to you (probably your side of a router), then the other side of the
router. If coming from outside, ping the cable modem (if you know its
address), then the outside of the router, then the inside of the router
(these may not work if pinging the router is suppressed), then some other
known internal network Ip address.

Another tool is tracrert (IIRC) on the PC, which will tell you all the
addresses that were found on the way to the final destination. The 400 has
it now, called traceroute. This is an interesting command - from South St.
Paul, MN, where I live, to get to an IFS in another part of town, it takes
16 hops - and it looks like it goes through Chicago. To get from my home to
my office in Rochester, MN, it seems to go through Omaha and took 20 hops.
This is ATT Broadband - no wonder it seems slow sometimes.

Is this naked telnet or is it PC5250 that does not work? If ping works, try
telnet ip-address from a command prompt in Windows
On the 400 and with Client Access, try cwbping from a PC - this verifies
that host Servers are up

If you have the console, run NETSTAT at a command line, look for telnet in
the list of local ports

Check out the TCP/IP Configuration and Reference manual - there are good
troubleshooting sections in it.

Regards

Vern

At 10:47 PM 11/11/02 -0500, you wrote:

>  Stop IMPLing your AS/400 to fix problems.  It's not a PC damn it!
>
> >
> > I have turned off/on the cable modem as well as the LinkSys router and
> > IPL'd the 400, TCPIP appears to be running fine.
> > I can access the Internet using the LinkSys router and the cable modem
> > and I connect to the 400 with CA
> >
> > We are running V5R1 and Windows XP
> >
> > I don't know what to do to start trouble shooting this, any suggestions
> > would be greatly appreciated
> >
> >