TCP/IP V5.1 ECO 5 blocks all incoming telnet connections by default?

[Adrian Graham_1]

Hi Folks,

Got an AS4100 here running VMS 7.2-2 (I know...) and TCP/IP V5.1. Sometimes Telnet gets upset and all new incoming sessions just receive a screen full of umlaut-y characters. The only cure is to reboot the box as tcpip$shutdown doesn't close telnet down properly.

I read somewhere (possibly here) that this problem was fixed in ECO 5 (155) which is the last patch available for V5.1 so we download, backup the system disk, apply the patch and reboot. However, when back up any incoming telnet connections are rejected with a message like 'INTERnet connect request rejected - IP address access list, IP address 10.x.x.x'

In the abstract for the previous patch (154) there's an entry for 'default access lists becomes IPv6 only, everything else is rejected' which would explain the problem, but that should've been fixed in patch 154. According to $tcpip sho serv telnet/full there aren't any access lists set.

"Accept netw: 0.0.0.0:255.0.0.0, 192.168.90.0:255.255.255.0"

(this is the setting from unpatched V5.1 which works)

Anyone come across this before? Failing that does anyone have ECO 4 (154) as a PCSI saveset?

Cheers

Adrian

[labadie_1]

On the "old" australian ftp site, it seems you will find the Eco 4

http://ftp.support.compaq.com.au/pub/patches/vms/axp/v7.2-2/tcpip/5.1/

I see, among others
http://ftp.support.compaq.com.au/pub/patches/vms/axp/v7.2-2/tcpip/5.1/dec-axpvms-tcpip_eco-v0501-154-4.pcsi-dcx_axpexe

[Adrian Graham_1]

Excellent, thanks! I keep forgetting about the 'old' Australian site.

*bookmarks*

I'll give that a go and report back.

Cheers

A

[Adrian Graham_1]

Well, ECO 4 does the same thing. I'm now officially puzzled! Anyone else seen this behaviour before?

[labadie_1]

Dumb question, but have you rebooted, as it is necessary ?

[Adrian Graham_1]

I have, yes :) I did the patch with the system in 'minimum' mode so had to reboot to full multiuser.

[Wim Van den Wyngaert]

Which is the telnet client ? Tried it with other clients (e.g. vms-to-vms) ?

Wim

[Adrian Graham_1]

Hi Wim,

Both telnet from windows and a local $telnet localhost get blocked despite the access list being defaulted. I'm just about to change the IP address of the machine to see if that makes a difference.

[Wim Van den Wyngaert]

Always with tunish on the screen ? Nover a message ?

ucx sho servi telnet/fu doesn't show "peak" as high as "limit" ?

Did you try disable servi telnet , wait a few seconds, ucx enable servi telnet ? That should normally help (but kill all users).

Did you check quotas tcpip$inetacp ? Opcom messages ? Accouting of the process (may be it aborted the telnet after leaving the screen blocked/client unabortable) ?

Wim

[Wim Van den Wyngaert]

I meant of course rubbish on the screen, not tunish or so.

[Adrian Graham_1]

This is from a freshly booted box with otherwise nothing running, It's acting like I've created an access list on WE0. I checked output from a $tcpip sho serv telnet/full both before and after patching and it's the same - limit 250, current 0, peak 0.

OPCOM always shows the same error - "INTERnet ACP Telnet reject request - IP Address access list"

[Wim Van den Wyngaert]

Do you mean you have the problem starting from the first telnet or that there are no users present now ?

I'm on 5.3 eco 2 and I'm unable to get anything in the "accept netw". It just doesn't react to my commands. As 1 allow for 0.0.0.0 is enough, I wpould trry to remove the 182. ucx set servi /accept=nonetw=192...

Wim

[Wim Van den Wyngaert]

You can remove the service and configure it again. That should get rid of the access list.

[Adrian Graham_1]

Funnily enough that's what I've just done and it's now running happily so I'll patch up to ECO 5 again and see what happens!