HP3000-L Archives

April 1997, Week 4

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:
Steve Forrette <[log in to unmask]>
Reply To:
Steve Forrette <[log in to unmask]>
Date:
Wed, 23 Apr 1997 13:20:41 GMT
Content-Type:
Text/Plain
Parts/Attachments:
Text/Plain (21 lines)
In article <[log in to unmask]>, [log in to unmask] says...
>After being in the relatively sane world of the HP3000 for the last 14
>years, I am now faced with the challenge of adding a Windows NT box to
>the equation.
>I could use some direction on the "how to" side of connecting these two
>systems.  My users are running Reflection 1 with NS/VT on Win 95 Vectras
>and the NT server (another HP box) is connected to the thinlan cable
>going to the Open View PC.  What do I need to setup on the 3k to allow
>users to connect to the 3k via the NT box rather than their current
>serial connection?

The NT server does not get involved in making the connections between the
users' desktop and the HP 3000 - the NS/VT protocol connects directly between
the desktop clients and the HP 3000.  The only involvement that the NT server
would possibly have is if you had Reflection loaded on the server instead of
each client for ease of administration.  In that case, Reflection would load
from the server using Microsoft drive-sharing, but the connection to the 3000
would still be directly from the client, bypassing the NT server.

Steve Forrette, [log in to unmask]

ATOM RSS1 RSS2