Re: terminal server for vax?

Richard wrote:

Actually I was referring to what DEC named things. I know better than
to trust ebay listings to be wholly accurate :).

Every "DECserver" I've seen is a terminal server, but there are a number of "DECgizmo" devices around, and some of these can have very similar names. And obviously what can get posted on eBay (or reported here, for that matter) can be incorrect or ambiguous. Unfortunately.

Now that I've browsed more items on ebay, I see that there are three
port types: DB25, RJ45 and MMJ.

I've seen very little DIGITAL iron with a RJ45 for asynchronous serial communications -- there were probably a few, but I don't recall any off-hand. The classic DECconnect parts were the DB9 (beware: two different pinouts; see the OpenVMS FAQ), the classic DB25 (for serial on older systems, and modem control can be particularly entertaining), and the MMJ. The RJ45 was mostly used with and for NICs, as is obviously still the case -- not usually for asynchronous serial comms.

As mentioned, the MMJ doesn't have the modem control signals in its classic wiring and pinout.

Pinouts and diagrams and such for many of these widgets are, as was mentioned, in the OpenVMS FAQ.

I also see that there are standalone
boxes and 8 port units that plug into a backplane (DECserver 90 Hub, I
think its called). Is the only difference between these the capacity,
with the hub providing a range of capacity (and options since you can
put more than terminal server boxes in the backplane)?

The DEChub series provided power, mounting and other such. You'd need the backplane and the particular device(s) to be installed into it.

You mean that I would connect the console port to the terminal server
and then by initiating something on the shell of a host connect
through the terminal server to the console port of the 11/03 like it
was a "host" on the network? That would be handy! is this simply a
matter of configurin the port on the terminal server?

Yes. Configure the port speeds and feeds appropriate for the host, and set it up as a service within the terminal server.

Any guide for which models support IP connectivity?

Boxes that post-date the DECserver 300 series, IIRC, which would be the DECserver 90 and the DECserver 700, among others. (The further back you go into the series, the tougher it can get to maintain them, and, relatively speaking, the less capable the devices are.)
.

Relevant Pages

  • Re: REMOTE DESKTOP NOT WORKING ANY LONGER PLEASE HELP!
    ... I understand that you have checked in the registry *which* port is ... Is the host located at your work? ... be a centrally managed GPO which disables Remote Desktop ... Noest MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: REMOTE DESKTOP NOT WORKING ANY LONGER PLEASE HELP!
    ... OK, and it's the host that is running Vista, is that correct? ... Have you checked if it is listening on port 3389, ... centrally managed GPO which disables Remote Desktop connections. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: External drives not installing or working properly on USB
    ... with the USB system before but these disappearred when I disabled the ... Only one of the five host controllers is connected to the 6 ... work on any port on the PC? ... operating system to recognise the four additional 'drives'. ...
    (microsoft.public.windowsxp.general)
  • Re: A firewall wont stop this one
    ... On top of that I implement IPF on each host ... >> for further access control to limit NFS, ... By restricting access to the NFS server. ... >> via port filtering that only allowed specific hosts rather than all. ...
    (alt.computer.security)
  • Re: /etc/hosts.equiv & .rhosts
    ... want to login at another host, that host needs the first host's name ... best to allow key-only login so hackers can't ... on the port 22 as it WILL be messed with all day long. ... # Protocol 2 only ...
    (comp.os.linux.security)