RE: (PM) Destination host unreachable
Josh Richards (josh@lucent.com)
Mon, 11 May 1998 14:02:10 -0700 (PDT)
On 11 May 1998, Terje Sten Bjerkseth wrote:
[..]
> It is connected on-demand via another PM2, 193.71.150.20. BTW, I can
> ping/traceroute to 172.29.220.0 from 193.71.148.10 itself:
>
> trf-pm2[193.71.148.10]> traceroute 172.29.220.11
> traceroute to (172.29.220.11), 30 hops max
> 1 193.71.148.12
> 2 193.71.150.15
> 3 193.71.150.20
>
> Still, 193.71.148.10 says "unreachable" when I try to ping it from *my*
> PC (which is dialled up via 193.71.148.10):
>
> Tracing route to 172.29.220.11 over a maximum of 30 hops
>
> 1 30 ms 30 ms 30 ms 193.71.148.10
> 2 193.71.148.10 reports: Destination host unreachable.
>
> Trace complete.
Yep, see my previous e-mail. It is your filters. Remember that when you
ping/traceroute from the PM itself from an administrative session, it
bypasses locally defined filters.
-jr
----
Josh Richards - <jrichard@livingston.com> - <josh@lucent.com>
[Beta Engineer] - LUCENT Technologies - Remote Access Business Unit
<URL:http://www.livingston.com/> * <URL:http://www.lucent.com/dns/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>