[comp.os.vms] Fact finding mission

COSC1Q0@uhvax1.uh.EDU ("Lee K. Gleason, Control-G Consultants") (04/14/88)

  I am looking for any sites that have used Wollongong
TCP/IP to communicate between VAXen and Bridge Corporation
Terminal Servers. A part of our company is pushing this
as a solution to some terminal server problems, and I
need to gather reports on how it works as a solution.

  I would also be interested in hearing reports from
sites that are using Bridge Communications terminal server
products - especially sites that have DECservers on the
same Ethernet as the Bridge boxes. Let's trade stories...


Lee K. Gleason
Control-G Consultants
2416 Branard #D
Houston TX 77098
Phone 713/528-1859

"Pay no attention to that man behind the curtain..."

COSC1Q0@UHVAX1.UH.EDU ("Lee K. Gleason, Control-G Consultants") (04/19/88)

  I am looking for any sites that have used Wollongong
TCP/IP to communicate between VAXen and Bridge Corporation
Terminal Servers. A part of our company is pushing this
as a solution to some terminal server problems, and I
need to gather reports on how it works as a solution.

  I would also be interested in hearing reports from
sites that are using Bridge Communications terminal server
products - especially sites that have DECservers on the
same Ethernet as the Bridge boxes. Let's trade stories...


Lee K. Gleason
Control-G Consultants
2416 Branard #D
Houston TX 77098
Phone 713/528-1859

COSC1Q0@UHVAX1.UH.EDU

"Pay no attention to that man behind the curtain..."
-------

iglesias@ORION.CF.UCI.EDU (Mike Iglesias) (04/19/88)

We have Bridge terminal servers and are using Wollongong's TCP/IP
on both an 8350 and a 785 with no problems.  We're also running
DECnet on the same ethernet.  No DEC terminal servers, though.

The terminal servers will handle ^S/^Q for you instead of passing
it thru to the system, so if you're using editors like EMACS or
devices like plotters, you'll have to make sure the terminal server
is passing the ^S/^Q thru for EMACS and not passing (but stopping 
output) for plotters.  It's fairly easy to do - you just 'escape'
back to the terminal server, turn flow control off/on, and go back
to your telnet session.


Mike Iglesias
University of California, Irvine
-------