HP3000-L Archives

June 1998, 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:
Chester Copeland <[log in to unmask]>
Reply To:
Chester Copeland <[log in to unmask]>
Date:
Tue, 9 Jun 1998 09:44:15 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (61 lines)
Yes you can bridge your DTC LAN with your PC LAN but;
-The PCs in Bldg A will have to connect to the LAN via a Network Interface
Card and be running a TCP/IP stack (best bet is to upgrade them to Windows
NT) as well as the appropriate Reflections for the stack (ie. Reflections
for HP with NSVT).
-You will require NS3000 on your HP3000 in order to get NSVT.
-These PCs will no longer require their async (serial) connection to the DTC
and if all users in Building A are PCs connecting in this manner, you will
no longer require the DTC there. In fact, if all users have PCs equipped in
this manner, you would not require any DTCs.

The HP3000 NS protocol can coexist on a LAN with a protocol such as
Microsoft Networking (which your NT servers are probably running) or Novel
Networking. I doubt there is any good reason for isolating DTC traffic from
your PC LAN but if you want, you could use an intellegent bridge between
your (new) DTC LAN with its added PCs and your existing PC LAN. This would
isolate HP3000 traffic to your segment of the LAN and it would not be passed
through the bridge to the PC LAN. Traffic that is destined for another
segment (such as Internet traffic) would pass through. I believe most
bridges will do this.

Regards
Chester Copeland

Tim Herrin wrote in message <[log in to unmask]>...
>About a year ago, Jim Phillips wrote "Okay, so we're the last company
>with an HP 3000 to be doing this! <g>".  Well... not quite.
>
>We need to connect our HP 3000 to our PC network and I'm hoping someone
>could give me some advice.
>
>In the computer room (where the HP 3000 is) are a couple of 10base-T
>hubs that connect to our NT server and the PC's in our building.  The
>AUI port on one hub has a transceiver that connects to the fiber optic
>cable going to our library and the internet.
>
>We have three DTC's connected to the HP 3000.  Two are DTC 48's in the
>computer room.  The other is a DTC16 in another building (building A)
>connected over fiber transceivers.  The PC's in building A are not
>connected to the PC network (we're using our only fiber optic cable to
>that building for the DTC).  We would like to have the PC's in this
>building connect to the network so they could have e-mail and internet
>access.
>
>Could I daisy chain the thinLAN cable from my DTC 48 to one of the hubs
>on the PC network and then to the transceiver going to building A?  I
>guess I'd need another hub in building A to hook the PC's to, then those
>users  with PC's could access the HP 3000 with NS/VT.  Could I daisy
>chain from this hub to the DTC16 to keep access for terminal users and
>printers?
>
>We have an extra LAN adapter on our 3000.  We had wanted to keep the DTC
>traffic off the PC network, but if we do that, the folks in building C
>still will not be on the PC network.  Is there any real security or
>performance benefit to having the DTC's on a seperate LAN that would
>warrant installing another line to building A?   TIA for any advice.
>--
>Tim Herrin
>Wingate University
>(704) 233-8150

ATOM RSS1 RSS2