Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Nov 2006 09:55:12 +0700 (ICT)
From:      Olivier Nicole <>
Subject:   Re: Totally stumped - very long post
Message-ID:  <>
In-Reply-To: <BFE16982B9EB3D6BADF911A8@paul-schmehls-powerbook59.local> (message from Paul Schmehl on Mon, 20 Nov 2006 20:26:59 -0600)
References:  <BFE16982B9EB3D6BADF911A8@paul-schmehls-powerbook59.local>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> Now here's a traceroute from the server to my Mac at home (actually to the =
> IP of the dsl router:
> traceroute
> traceroute to (, 64 hops max, 40 byte packets
>  1  * * *
> traceroute: sendto: Host is down
>  2 traceroute: wrote 40 chars, ret=3D-1
>  *traceroute: sendto: Host is down
> traceroute: wrote 40 chars, ret=3D-1

Would be usefull to try to traceroute from your mac to your server:
comparing both traceroute helps to see where the route is blocked.

A ping in both direction will help too.

A traceroute to another IP in 66.140.63/24 network may help. To
another IP in 66.140/16. To another IP in 66/8.

Traceroute from and to the webmail machine could help too, find the
difference, understand why there is difference and then you have your
problem located.

Then install wireshark (/usr/ports/net/wireshark-lite/) on the server
from the ports and see what it says when you are trying to browse the
server? Can you see the SYN packet? Does the server send the SYN/ACK

Install wireshark on your Mac client and do the same test, does
yourclient send the SYN packet? Do you see the SYN/ACK sent bythe

Desactivate the firewall on both machines.


Want to link to this message? Use this URL: <>