HP3000-L Archives

July 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Rick Clark <[log in to unmask]>
Reply To:
Rick Clark <[log in to unmask]>
Date:
Thu, 8 Jul 1999 14:46:32 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (82 lines)
Boy, is my face red!!! You are correct Kevin. IPX, IP, are protocols.
10baseT would be considered an IEEE standard, or a wiring scheme.

Rick Clark
WW&R


"Newman, Kevin:" wrote:
>
> So, if 10baseT is a protocol, where are the specs for it?
>
> I thought that it stood for 10Mbps capable wire, connector, or NIC.  My
> 10baseT NIC is not tied to a specific protocol.  I can run IPX, IP, or
> anything else that I can program to run on it.  The NIC is about as low
> level as you can get - hardware, yet it is a 10baseT card.
>
> So where is the line drawn between protocol and hardware?
>
> Kevin
>
> > -----Original Message-----
> > From: Rick Clark [SMTP:[log in to unmask]]
> > Sent: Thursday, July 08, 1999 10:54 AM
> > To:   [log in to unmask]
> > Subject:      Re: can you make terminals work on a network?
> >
> > 10baseT is a protocol. What we should have been saying is, as someone
> > pointed out earlier, that the cable infrastructure is CAT5 (or CAT3
> > depending on your requirements).
> >
> > Rick Clark
> > WW&R
> >
> >
> > "Johnson, Tracy" wrote:
> > >
> > > 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

ATOM RSS1 RSS2