PuTTY "Connection Refused" telneting to z/OS UNIX SYSTEM SERVICES 2

[AndromedaM31]

Hi,

I work on z/OS (IBM) systems. While I am very good at managing the Operating System I know practically nothing about TCP/IP, which brings me to my question.

I am trying to telnet in to z/OS UNIX System Services. I am attempting to do this with PuTTY. When I attempt to connect I get the error, "Connection Refused".

The port we have setup for this is 2023. Here is the definition for PORT 2023:
PORT 2023 TCP OMVS ; TELNET UNIX SERVICES

I am at a loss as to why the connection is being refused. Can anyone help?

 

[burtsbees]

Are you trying to telnet via port 23, like the default, or are you changing it to 2023 in PuTTy?

Burt

 

[AndromedaM31]

I changed PuTTy to use port 2023.

 

[burtsbees]

Can you ping via port 2023? Have you tried other telnet clients, such as Windows command prompt, HyperTerminal, or even Tera Term?
First you must establish that there is connectivity. Please explain all that you have tried, if there's a firewall in the path, etc---you are being very vague.

Burt

 

[AndromedaM31]

Hi Burt,

Sorry for being vague. I should have provided more information.

I can ping the IP address of the machine I want to telnet into. I'm not sure what you mean when you say, "Can you ping via port 2023" as I don't know that I can ping at the port level.

There is no firewall between my workstation and the system I want to access.

When I try to use HyperTerminal I get an error dialog stating:
Unable to connect to ... port 2023
Where "..." is the IP address I entered.

When I open a command prompt (DOS window) and issue telnet ip address:2023 it displays the following message:
Connection To ip address:2023...Could not open connection to the host, on port 23: Connect failed

Interestingly the previous messages displays port 23 rather than port 2023 even though I specified 2023.

Is there anything else I can provide? Please let me know and I will get any information you require.

Thanks for your help.

 

[LawnBoy]

Sounds as though the service is not running on z/OS. If this was a permissions problem you would see "connection refused" rather than "connection failed".

I'd triple-check that the service is actually running on the port specified. Can't help you with z/OS, but you could run a port scanner against that server.


"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 

[burtsbees]

Plus, in the Windows command prompt, there is no colon between the IP address and the port. Also, I did not mean ping via a port---I meant telnet.
C:\>telnet x.x.x.x 2023

Burt