"Outbound" telnet sessions quit working

[Stephen Daddona]

I have a couple of ports on a DECserver 700 set up to use Outbound (I think that's what it's called) Telnet sessions. They've been working for over a year, but just recently they've quit working, and I can't figure out why. I create the Telnet session thusly:

$ telnet cmprm5 /create_session /permanent 2016 8007

The Telnet listener port on the terminal server is defined thusly:

Listener TCP-port: 2016
Identification:
Ports: 16
Connections: Enabled

And the terminal server port looks like this:

Port 16: Server: CMPRM5

Character Size: 8 Input Speed: 9600
Flow Control: XON Output Speed: 9600
Parity: None Signal Control:Disabled
Stop Bits: 1 Signal Select:CTS-DSR-RTS-DTR

Access: Remote Local Switch: None
Backwards Switch: None Name: TNA8007
Break: Local Session Limit: 2
Forwards Switch: None Type: Hard
Default Protocol: ANY

Preferred Service: None

Authorized Groups: 0
(Current) Groups: 0

Enabled Characteristics: (none)

I have a Breakout Box (BOB) between the port connection and the terminal device. I can see data coming down the line when I do a TEST PORT on the terminal server, but don't see anything when I try copying something to TNA8007: from VMS.

As far as I can tell, nothing has changed from when it was working.


Any thoughts?

Thanks in advance!

[Volker Halle]

Craig,

did you get any error message when creating the outbound TELNET device ?

Can you UCX PING the DECserver ?

Is there a BG device pointing to the DECserver and port ($ UCX SHOW DEV) ?

If the TNA8007 device spooled (SHOW DEV TNA8007) ?

Do you get an error message when you COPY file TNA8007: ?

Volker.

[Wim Van den Wyngaert]

Did you try a reset of the port on the decserver with logout ?

Wim

[Stephen Daddona]

Volcker,

1) Not when I create the telnet device, but I get a %SET-W-NOTSET error when I do a SET TERM command on the terminal. But the stuff that I'm setting gets set anyway.
2) Yes
3) No
4) No
5) No. Initially the COPY finished and returned to the system prompt, lately it's been "hanging", and I've had to do a ctl-Y to get back to the prompt.

Wim,

No, but I did reboot the terminal server twice. When I saw your response I did a logout on the port with no change.

[Volker Halle]

Craig,

what happens, if you manually create an interactive TELNET session to that port on the DECserver ?

$ TELNET CMPRM5 2016

If the session gets established, everything you type should show up on the device connected to the DECserver port. To disconnect the session, type CTRL-] or CTRL-5

You could trace the IP messages with:

$ TCPTRACE cmprm5

from another terminal.

Volker.

[Volker Halle]

... and what does SHOW PORT 16 STATUS say ?

Volker.

[Stephen Daddona]

I'm 99% sure that a couple of power outages did "something" to the terminal server. I installed another one and it worked ok.