THAT I can understand, copper is copper and crimping it down to whatever contact on an RJ-45 is not a problem, I've been doing that for years.  I think of 10BaseT as a protocol, not a cable type.

So back to my original thought, how does he get serial RS-232 to talk 10BaseT protocol?  Or is this not the question?  The only valid recipient for RS-232 protocol at one end is RS-232 at the other.

If the reference is only to cable, no problem, a no-brainer, I've used bent paper clips on some interfaces.

So, is 10BaseT a protocol or a cable?

-----Original Message-----
From:   Bryan Greenberg [SMTP:[log in to unmask]]
Sent:   Thursday, July 08, 1999 10:10 AM
To:     [log in to unmask]
Subject:        Re: can you make terminals work on a network?

Tracy Johnson poses the question:
I'm at a loss to understand how Bryan does it.  Especially a terminal
model that has only a serial port connected directly to a 10baseT port
in the second sentence.

I may have munged up my thoughts on this one.  Basically you leverage
the existing (or in this case newly installed) network wiring by
running your serial terminals over the 10baseT cable.  Most
installations of network wiring will have RJ-45 jacks on the node end
that are connected by individual runs of cat5 cable to some sort of
punch down panel.  Normally you would then run a patch cable from the
punch down panel to a hub, completing the connection.  If you run that
patch cable to a dtc instead you get a serial connection (if you've
plugged a terminal in on the other end).  If your network is more
exotic (ie switched or not on the same side of a router as the dtc)
then this configuration will not work.

I hope this clears the fog from my writing.

Bryan