HP3000-L Archives

January 2006, Week 3

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:
Timothy Atwood <[log in to unmask]>
Reply To:
Timothy Atwood <[log in to unmask]>
Date:
Wed, 18 Jan 2006 19:41:24 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
OK, I switched around the hop counts as per a couple people. The old TR card
has neighbour gateways at hop count 20. The new Ethernet hop count 1.

Print to network printer still connects through old TR card, not new
Ethernet.

Any other ideas?

----- Original Message ----- 
From: "Timothy Atwood" <[log in to unmask]>
To: "HP3000-L" <[log in to unmask]>
Sent: Wednesday, January 18, 2006 3:17 PM
Subject: New NIC: Why Printers Connecting Under Old NIC?


> We are in the process of replacing old obsolete Token Ring network with
> Ethernet on HP3000 928 (MEP/iX 6.0 PP2). Right now we have both cards
> running. DNS servers, host tables, etc. are being converted to address of
> new Ethernet NIC.
>
> Looking at things still connected through old TR network to see what we
> missed, I find our network printers keep showing as connected through old
TR
> network.
> Why? Any idea how to get them to route through new Ethernet NIC card?
>
> I thought that setting up new network (NMMGR) with a higher hop count on
the
> neighbour gateway would give new network priority for network printers.
> Apparently not so.
>
> Thanks to all who answered my question on how to find what was connected
> through old network. Final answer was from David Knispel - Thanks David:
>
> Run NETTOOL.NET
> status
> tcpstat
> conntable
> IP address of old TR card on HP3000
>
> This gives me a list of all IP's connected through the old TR card. Using
> our IP documentation I then identify what each was (PC or peripheral such
as
> network printer, etc.). If there was any question who was using a
particular
> PC, I then list the logon session ID for each IP with LISTF CI.PUB.SYS,8.
I
> then match the IP's between the two listings to find the session name
> connected through the TR card.
>
> Thank you,
>
> Timothy Atwood
> Holtenwood Computing
> for Domtar Vancouver Mill
> http://www.holtenwood.bc.ca/computing/
>
>
>
>

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

ATOM RSS1 RSS2