HP3000-L Archives

July 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:
Denys Beauchemin <[log in to unmask]>
Reply To:
Date:
Fri, 25 Jul 1997 03:14:55 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (55 lines)
The problem is one of name resolution.  Your Windows 95 is trying to find
your HP 3000 and it is having difficulty.  You should verify that you have
the HP 3000's name in the HOSTS file found in the directory of your TCP/IP
stack on your PC.  Either \windows if you use Win95 TCP/IP or \reflection
(or the appropriate one) if you use WRQ's stack.  The time out value is 255
seconds before a different attempt is made at finding the host, hence the
long delay.  Once the resolution is made, everything will indeed go fine.
 I invite you to visit my web page for more info on connecting Windows 95
to the HP 3000.

Kind regards,

Denys. . .

Denys Beauchemin
Hicomp America, Inc.
[log in to unmask]        www.hicomp.com
(800) 323-8863   (281) 288-7438  fax: (281) 355-6879



-----Original Message-----
From:   Curt Brimacomb [SMTP:[log in to unmask]]
Sent:   Thursday, July 24, 1997 4:40 PM
To:     [log in to unmask]
Subject:        NS config and VT-MGR

I have a question for the net gurus out there:

I have a hp3000 917 running MPE/ix 5.0 with express 3 installed.  This is a
demo machine and we do not have support on it.  It is not connected to our
existing network.

I need to add a hub on it for PC's to connect at our  HPWORLD booth.  I
tried to reconfigure NMMGR and have it start NS (LAN1 AND LOOP).  It did
not work the first time (validate failed), so I renamed nmconfig.pub.sys
and tried again.  Then it configured and validated fine.  The machine
reboots with no errors.  I configured it for a node name of
hp917.idaho.computer and an IP of  C199.104.022 007, subnet mask of
255.255.255.224 using 56 for the dtslink path.

I take my PC (WIN95), which connects to our network fine, and plug it into
this new hub on the 917, get reflections to try to connect to the IP
address, and then wait for up to 5 minutes to get a login prompt.  Once I
get connected it seems fine.

Is there something configured wrong on the PC or the 917?

Curt Brimacomb
System Manager                                          www.magiclink.com
Idaho Computer Services, Inc.                                   Voice:
 1-208-734-2245
Twin Falls, Idaho 83301                                         Fax:
   1-208-733-9663

ATOM RSS1 RSS2