Date: 07 Jul 2003 22:45:49 +0000 From: Stacey Roberts <stacey@vickiandstacey.com> To: Micheal Patterson <micheal@cancercare.net> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Changed ISP now can't get to websites / traceroute Message-ID: <1057617948.349.225.camel@localhost> In-Reply-To: <06a901c344d3$8c0a2850$4df24243@tsgincorporated.com> References: <000101c344be$3c994ae0$ac64033e@m00is.net> <1057608657.349.205.camel@localhost> <86ojgvkiu4lfo7tftccepk9c18d0ju6jej@4ax.com> <1057614312.349.220.camel@localhost> <06a901c344d3$8c0a2850$4df24243@tsgincorporated.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Sorry about the delay.., On Mon, 2003-07-07 at 22:03, Micheal Patterson wrote: > > 14 * border-to-141-netrack.boulder.co.coop.net (207.174.144.178) 139.951 > ms !X * > > > 15 border-to-141-netrack.boulder.co.coop.net (207.174.144.178) 136.281 > ms !X * * > > > 16 border-to-141-netrack.boulder.co.coop.net (207.174.144.178) 159.470 > ms !X * 137.951 ms !X > > > > Note here that you don't appear to actually *get* to freebsdforums' IP: > > That's correct. !X is "Communications Administratively Prohibited" meaing > they've got an ACL in place that explicitly denies access to the next hop in > the trace. I can trace to that point and then my trace dies with simple > timeouts instead of "prohibited". To me, that usually means that a firewall > is active that is denying udp and icmp also. > > > >From nslookup for freebsdforums.org : > > Non-authoritative answer: > > Name: freebsdforums.org > > Address: 207.174.189.161 > > > > I'm trying to force Zen to increase their efforts in doing whatever > > they're able to do for me, but its a nightmare getting through to tech > > support to even begin that process.., > > I'm not sure what Zen will be able to do as long as they're advertising that > they're responsible for the network block that you've been assigned to. > Although, they may be willing to contact the network powers that be for the > networks that you can't traverse through due to lack of action on their > part. Then again, it is the remote networks perogative to allow or disallow > the traffic. > > > For now, I'm trying to google around for what I might need to do in > > order that I can get traceroute to work for my *nix boxes here.., > > Good luck. > Thanks for the encouragement.., I've narrowed this down to the router I purchased from Zen here.., I've basically turned off ipfw and I'm still unable to even traceroute to the router itself.., I've now emailed Zen tech support to see if they're gonna provide that support they insisted they could only provide if I bought the router from them - which I did. Thanks again for taking the time. Regards, Stacey > > Thanks again for that.., > > > > Regards, > > > > Stacey > > > > -- > > Stacey Roberts > > B.Sc (HONS) Computer Science > > -- > > Micheal Patterson > TSG Network Administration > 405-917-0600 > > Confidentiality Notice: This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential > and privileged information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1057617948.349.225.camel>