HP3000-L Archives

January 2005, Week 2

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:
Matthew Perdue <[log in to unmask]>
Reply To:
Matthew Perdue <[log in to unmask]>
Date:
Tue, 11 Jan 2005 23:25:25 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (72 lines)
Quoting john pitman <[log in to unmask]>:

>Terry,
>BTDT - seen similar symptoms. For a while our only work around was to
>change IP address of printers. Somebody suggested use of netcontrol command,
>as in Netcontrol update;lan=lanx
>
>To get network back to std parameters I think.
>
>Also do some poking around in nettool.net.sys - check gateways, nameaddr
>and routings for incorrect stuff. We seemed to have picked up a wrong
>gateway somehow, and the netcontrol update fixed it somehow.
>
>Do a search of the list site for things like this. Something to do with
>Cisco routers and strange requests they send out.
>
>HTH
>jp

The Cisco routers can sometimes send out redirect requests, and the HP3000
dutifully complies... setting up gateway redirects that go nowhere. The problem
isn't with the HP, it behaves according to protocol; the problem is with the
Cisco routers and/or switches - they need to be configured to not send the
redirect requests in the first place. I've had this same problem at a clients
site a couple of times.

RUN NETTOOL.NET;INFO="NAMEADDR;ROUTING;GATELIST" and see if you have more than
one gateway listed. If you have only one LAN and more than one gateway, that's
more than likely your problem.

Then do a NETCONTROL NET=<netname>;UPDATE=INTERNET
and it should clear the problem.

> -----Original Message-----
>From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
>Behalf
>Of Simpkins, Terry
>Sent: Wednesday, 12 January 2005 12:21 PM
>To: [log in to unmask]
>Subject: [HP3000-L] "blocked" IP traffic
>
>We have a site in California that is suddenly having problems
>communicating with our site in VA.=20
>The symptoms make no sense to us, but maybe someone on the list will
>have seen something like this before.
>
>From the site in VA, we can ping some IP addresses, but not all.
>The HP3000 can establish communications (NS/VT) with PCs, but can't see
>some of the printers.
>
>In some instances you can ping the printer(in CA) from a PC in VA, but
>not from the HP3000.
>In other instances you can't ping the printer(in CA) from either the PC
>or the 3K (both in VA).
>In both cases, PC users in CA can ping the printer in question.
>
>The people who manager the routers, say there are no active access
>lists, or anything blocking=20
>traffic.  But something is stopping traffic.
>
>Any ideas?   My users are really anxious to be printing again.
>
>*****************************
>Terry W. Simpkins
>Director ISIT
>Measurement Specialties
>757-766-4278
>[log in to unmask]

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

ATOM RSS1 RSS2