NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/os/vms/19682

Internet Message Format | 1992-12-22 | 1.6 KB

Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsc!cbfsb!att-out!rutgers!spcvxb!terry
From: [e-mail] (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.os.vms
Subject: Re: UCX TELNET name.name.name portnumber -- How?
Message-ID: <[e-mail]>
Date: 22 Dec 92 00:27:15 GMT
References: <1992Dec21.092203.1@gallua>
Organization: St. Peter's College, US
Lines: 21

In article <1992Dec21.092203.1@gallua>, [e-mail] (Kevin Cole; Washington DC) writes:
> [Since vmsnet.networks.tcp-ip.ucx appears dead, I thought I'd try here...]

  It's not dead. You could post there and folks would see it and answer it.
But we're not picky, we'll answer here too 8-)

> Why does it understand one and not the other?  And is there anything *as a user
> not a systems manager* I can do about it?  Is there a way to feed it the
> parameters in a way that it will understand that it should translate the host
> name to the numeric address and then apply the port number?  Or am I misdiag-
> nosing the symptoms?

  You're running 1.3 without CSCPAT #903, I see. You could either upgrade to
2.0 or install the patch. Installing the patch would be a good idea anyway,
as there is a _giant_ security hole in base 1.3, and there are a number of
other problems where non-priv'd users can crash the VAX. Exploiting either of
those would likely convince your system manager to upgrade 8-)

    Terry Kennedy        Operations Manager, Academic Computing
    [e-mail]    St. Peter's College, Jersey City, NJ USA
    [e-mail]    [phone]