HP3000-L Archives

June 1997, Week 5

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:
Tony Knowles <[log in to unmask]>
Reply To:
Tony Knowles <[log in to unmask]>
Date:
Mon, 30 Jun 1997 10:23:16 +1200
Content-Type:
text/plain
Parts/Attachments:
text/plain (66 lines)
I'm no networking expert, but I have managed to get my PC running
reflection for HP with NSVT to the HP3000. It was quite a struggle, I too
referred to Denys' excellent tips which I only found out about near the end
of my struggle!

I have IPX/SPX and TCP/IP configured but not NETBEUI which I read somewhere
that Win95 networking uses. Someone posted a message recently that
suggested that IPX and TCP/IP couldn't co-exist??

I didn't need to make any changes in NMMGR as all the networking stuff was
already setup. Look at NETXPORT.NI.LAN.PROTOCOL.IP and make sure that the
HP3000 has an IP address specified.

The steps I missed early on were having a PATH entry in AUTOEXEC.BAT for
the location of RNNSVT.DLL, after I installed Reflection this file was
named RNNSVTX.DLL, I just nenamed it. I have set up a HOSTS file in
C:\WINDOWS, but I think you can just plug the IP address of the HP3000 into
Reflection.

The only problem I still have is that when I start up a new Reflection
session, I always get prompted for a dial-up connection first, even though
I have set 'don't prompt for dial-up' in the dial-up networking program.

Now my challenge is to connect up the laset printer.

Tony Knowles     [log in to unmask]
                           [log in to unmask]

----------
> From: Jim Phillips <[log in to unmask]>
> To: [log in to unmask]
> Subject: Networking 102
> Date: Saturday, 28 June, 1997 07:30
>
> Thanks to all for the help I've received so far!  This is a great
> list!  I've downloaded the HP3000-L FAQ (and finally learned how to
> pronounce Denys' last name! :-)), got to see Denys' great web page
> and learned how to install TCP/IP for WIN 95 (Thanks, Denys).
>
> Okay, so I've got TCP/IP running on my WIN 95 PC (at least I think so,
> can't connect to the HP3K, so who knows?).  I go into NMMGR to configure
> the network and it wants the "Physical Path of LANIC".  Using SYSINFO,
> in the IOMAP GENERAL HOST MAP, I see under "Channel Adapter 4" a
> "Local Area Network(4.3)", so that must be it, right?  Wrong!  That
> address is in use by the DTC's as shown by this error message when I
> exit NMMGR:
>
> Searching for subsystem validation routine VALIDATEDTS
> ---> Validation of DTS/LINK started. <---
> Path:  LINK.TOL948
>   The same physical path is being used at LINK.DTSLINK.  (DTSERR=4)
> 1 Errors Encountered.
> ---> Validation of DTS/LINK finished. <---
>
> So, how do I determine what the LANIC path is?  How do I know if I
> have a LANIC?
>
> You know, I remember seeing George Stachnik connecting a PC to the
> HP3000 in one of those video teleconferences and he didn't do any
> of this stuff!  It was just plug the PC in and away we go! :-)
>
> Jim Phillips                            Manager of Information Systems
> E-Mail: [log in to unmask]      Therm-O-Link, Inc.
> Phone: (330) 527-2124                   P. O. Box 285
>   Fax: (330) 527-2123                   Garrettsville, Ohio  44231

ATOM RSS1 RSS2