One of the first things I do with a possible server issue is issue a DOS
or line command something like this, with ip address and port number:
telnet xxx.xxx.xxx.xxx 21
I believe every TCPIP client, even one doing encrypted sessions, first
calls the "connect()" C routine, and that includes telnet. So if that
ip/port is listening and available via the network, you'll get some kind
of response after the telnet connect() is successful. He probably won't
know what to do with the response and you'll need to click ctrl-] and
then "quit", but at least you know you connected. If there's no
connection possible, you'll typically get a delay then an error message,
and that would have given you a good clue about the bad IP address.
I can't remember but I think you said you're on Windows. In modern
Windows, telnet (stupidly) doesn't come enabled. You may need to enable
it with this command from an admin DOS window:
dism /online /Enable-Feature /FeatureName:TelnetClient
On 7/28/2025 11:39 PM, Support, DUNNIT SYSTEMS LTD. wrote:
I owe the entire list a big apology. This was an IP address error. I
accidentally pasted the wrong IP address over the correct one.
"NEVERMIND!" - Emily Litella
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
