We have our 3000 on 192.168.2 subnet. We have an ISDN link to another site
with a router at 192.168.2.198 (actually an NT box doing something useful),
which feeds a 192.168.58 subnet
So we added this gateway spec on 3000:

  Neighbor Gateway Name: GATEWAY3    Gateway IP Address: C 192.168.002 198
    Reachable Networks:
      IP Network Number    IP Subnet Mask     Hops
      -----------------    --------------     ----
      C 192.168.058 000    255.255.255.000     3

And the .58 subnet can talk to the 3000 on .2 and 3000 can talk to all
devices on .58 subnet.
To be able to reach the .58 subnet (or any other  foreign subnet) from my PC
(on .2 subnet), I need to run a batch file containing - (best done by
Startup)
 
Route add 192.168.58.0 mask 255.255.255.0 192.168.2.198


We also ran out of addresses in .2 when we went all TCP/IP from serial
connections. Now each site has its own subnet (50,51,52,etc), and a gateway
entry in the 3000 telling it what the gateway is for each of them (all the
same address)

HTH
jp

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Bob Comeau
Sent: Tuesday, 31 May 2005 1:20 AM
To: [log in to unmask]
Subject: [HP3000-L] Network subset change

I didn't see anything in the archives that addressed my specific problem so
I thought I'd throw out the question and see what happens.

Ever since our 3000 was set up it has existed nicely as part of our
192.168.0 subnet.

We have run out of ip addresses in that range and are going set up the dhcp
server to start handing out 192.168.2.xxx addresses, while the static ip
addresses are going to stay in the original 192.168.0.xxx range.

The only static addresses the HP will care about are a few printers.

Initial testing while my pc is in the new subnet gets a failure to connect
using Reflection and VTMGR.

There must be a change I can make to the HP's network set up to make it
responsive to both subnets, but my network configuration skills are somewhat
lacking.

Only a handful of users are still actually connecting to the HP.  If
necessary we can keep those as static addresses in the old range, but this
strikes me as a bandaid.

Does any one have an easy fix for this?

Thanks.

Bob Comeau
Sr. Systems Programmer Analyst
Crossley Carpet Mills Ltd.
(902)895-5491 ex 139

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *