Home/Support/Support Forum/reverse telnet "access to this port denied" on Portserver 16
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

reverse telnet "access to this port denied" on Portserver 16

0 votes
I've got a portserver/16 and have it setup as a console server.

I can telnet into the terminal server to get admin access, and I can also

telnet <my-server-name> 2000+port #

to get to a given port.

My issue is when I'm on the admin console via Telnet, and try to do a

Telnet <any ip address> <any port>

All I get is an "access to this port denied" error message.

Can this be worked around? Or is there some other way to connect to a given port from the command line?

Thanks

Robb
asked Aug 31, 2004 in Portserver TS by x1pfister New to the Community (2 points)

Please log in or register to answer this question.

5 Answers

0 votes
To resolve this issue, please make sure that 'dev' is set for 'prn'.
#>set port ra=x-xx dev=prn. If it was set to something other then prn(such as 'term' 'mio' etc), make sure that you reboot the PortServer.
Also, make sure that there is no other process on a port. #>who command will display active porocesses on ports
answered Aug 31, 2004 by shatman Community Contributor (76 points)
0 votes
I've check that the port intended is set to PRN, rebooted, made sure nothing else was on that port, but still the error persists.

Note, I don't have a problem if I connect to the portserver via a serial port and do this, it is only when I telnet into the portserver that I can't seem to telnet out of it to any address.

Thanks

Robb
answered Sep 2, 2004 by x1pfister New to the Community (2 points)
0 votes
What user are you logging into the Portserver 16 as? Does this happen when logged in as "root"? What version of firmware does that Portserver 16 have?
answered Sep 7, 2004 by michaelt Veteran of the Digi Community (758 points)
0 votes
Logged in as root, although I recall this happened with other users as well.

The Version is 3.5.0
answered Dec 10, 2004 by x1pfister New to the Community (2 points)
0 votes
This may be an issue which was fixed with firmware. Try loading the 3.5.5 image on the Portserver 16 from a tftp host and see if that resolves the problem.

One thing though, the Portserver 16 didn't have flash proms, so the firmware will need to be loaded every time the Portserver is rebooted.
answered Dec 10, 2004 by michaelt Veteran of the Digi Community (758 points)
...