Re: Diagnose co-location networking problem
- From: Gary Palmer <gpalmer@xxxxxxxxxxx>
- Date: Thu, 28 Dec 2006 12:31:42 -0500
On Wed, Dec 27, 2006 at 10:08:25PM -0800, Stephan Wehner wrote:
Ok, this is a little unfortunate: I can't run traceroute from the client PC
(the service provider doesn't seem to like it). (Nor can I use ping)
/usr/ports/net/tcptraceroute
You should normally be able to use tcptraceroute to get path information
to systems that are listening on a TCP port (e.g. a web or mail server).
You can try ports that aren't open on the other end, but that may be
less useful.
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- References:
- Diagnose co-location networking problem
- From: Stephan Wehner
- Re: Diagnose co-location networking problem
- From: Matthew Hudson
- Re: Diagnose co-location networking problem
- From: Stephan Wehner
- Diagnose co-location networking problem
- Prev by Date: ipsec-tools 0.6.6 problem
- Next by Date: Re: Diagnose co-location networking problem
- Previous by thread: Re: Diagnose co-location networking problem
- Next by thread: Re: Diagnose co-location networking problem
- Index(es):
Relevant Pages
|
|