Re: Can't connect via TCP

If this is 2nd time, would look in job logs for TCP startup (several jobs)
and check for errors (dspoutq qezjoblog & F18 to see latest entries).
IBM has documented a recommendation on how to start tcp, see
document Changing the IPL Start-Up Program - V5R1M0 in the
Knowledge Base. Also a doc for V4R4/V4R5 and other docs for earlier
releases. Every new release seems to require something different.
Check that your interface is started (netstat comand). Ping is real basic
and should work even if host servers not working.
If had a power failure, check any router/switch/hub needs to be reset?
code 10060 is Connection Timed Out

----- Original Message -----
From: "Leif Svalgaard" <leif@leif.org>
To: "Midrange List Tech" <MIDRANGE-L@midrange.com>
Sent: Sunday, October 14, 2001 12:15 PM
Subject: Can't connect via TCP


> Folks,
> This is the second this happens to me:
> After IPL,
> TCP and associated servers are started,
> Ethernet card verified ok,
> When trying to connect getting error 10060
> (CA, Mocha, FTP, CWBPING).
> Nothing changed in configuration
> (reason for IPL was power failure).
>
> Everything looks normal (or rather: as it was
> before, as it is not clear was NORMAL when
> it comes to voodoo).
>
> How to proceed?
>
> TIA
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>