Re: (PM) routing problem on PM-3
James (James@superbug.demon.co.uk)
Sun, 25 Jan 1998 17:50:37 +0000
Hello Desengr.
This is a very simple problem to fix. From what I understand, you
moved a PM3 from one Subnet to another. So there is now a router between
you and the dns server.
All you have to do is clear out the ARP entries from all routers and
workstations that will contain a bad ARP entry.
The simple solution is reboot all routers and PCs that were on the same
segment that the PM3 used to be. Most PCs should be fine. For example
Windows NT is fine. Some Unix boxes and a know most Cisco routers will
need their arp table cleared. You only have to reboot the machines if
you don't know how to clear their arp tables.
Hope this helps.
Cheers
James
P.S. I found this out from experience with a PM3 swap out and a big
Cisco router. Cisco routers tend to take days to clear out bad arp table
enties. On Cisco IOS, just clear the whole arp table. It will relearn
almost immediatly with no loss of service.
The symptom was. PM3 could ping the Cisco router. But dial in users into
the PM3 could not.
> From: Desengr <desengr@bga.com>
> Date: Sat, 24 Jan 1998 13:09:17 +0000
> Subject: (PM) routing problem on PM-3
>
> I'm having a bit of a routing problem with my PM-3, likely
> 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
> the way here? What routing distinction is there between the
> PM3's own IP, and an IP from the modem pool? Any clues?
>
> Thanks,
> Desengr
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.