(PM) routing problem on PM-3 (fwd)

MegaZone (megazone@livingston.com)
Sun, 25 Jan 1998 17:27:03 -0800 (PST)

Once upon a time Desengr shaped the electrons to say...
>due to ignorance on my part. I moved the portmaster to a
>different IP block, but left my dns server at it's old IP
>address, still on the same ehternet segment though. I've set
>up static routes so that everybody sees
>everybody else now, with one acception. Even though I can
>ping my dns server from the command line on the portmaster,
>a dialup user can't ping that same IP. What could be in

Sounds like a routing issue then. Ping isn't very useful, use traceroute.
Try to trace from the user's machine to the host, and from the host to
the users machine. Somewhere along the line the route is probably being
lost. It is most likely at the gateway router between the PM-3's segment
and the host segment.

>the way here? What routing distinction is there between the
>PM3's own IP, and an IP from the modem pool? Any clues?

The only distiction are those inherent in IP routing.

-MZ

--
Lucent Remote Access Division - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.