> On Fri, 24 Nov 1995, Rodney Lorimor wrote:
>
> > > still does not work.... maybe I should do the rain dance on this one.
> > I don't think that that is required yet. :)
>
> damn, just got the hat out...
> >
> > I just looked at one of our remote PM's. The only other thing I might
> > think to ask at this time would be, what IP does your default route
> > (0.0.0.0) point to? Does it point to the IP of W1?
>
> 0.0.0.0 206.29.218.17 NS 1 frmW1
>
> but when I look at it
>
> bc-01> sho w1
> Local Address: slc-t1.fr.bc-01.vii.net slc-t1.fr.bc-01.vii.net
> which is 206.29.218.18
> which is not the ip of W1
>
> > Can you ping or traceroute to your default host from the PM?
>
> yes
>
> bc-01> ping vii.com
> vii.com (206.29.221.2) is alive
>
> bc-01> trace vii.com
> traceroute to vii.com (206.29.221.2), 30 hops max
> 1 206.29.218.17
> 2 206.29.221.2
> bc-01>
>
> I also have routing off
> Default Route: Quiet (Off)
This is what we use.
> Routing: Quiet (Off)
> could that be it?
If this is from W1, this could very well be your problem. Our W1
interface has routing turned on.
Interface: frmW1 (FRM,Routing)
--- Rodney J. Lorimor LAN/WAN consultant Spokane, Washington rodl@iea.com (509) 624-6798 "Just Another Day in Paradise"