Patrick Nelson wrote:
1. There should not be any because the GW for the mail server is the
ISP GW of 206.58.200.1
2. Here is the TraceRoutes of the Mail to and GW systems.
This is to the GW system not the ISP gateway. The GW system is
attached to the hub that the Mail system:
[mail ~]$ traceroute -v 206.58.200.33
traceroute to 206.58.200.33 (206.58.200.33), 30 hops max, 38 byte packets
1 206.58.200.33 (206.58.200.33) 46 bytes to 206.58.200.39 7.806 ms
0.459 ms 0.442 ms
This is to the ISPs GW which can be pinged by the GW system but not
the Mail system:
[mail ~]$ traceroute 206.58.200.1
traceroute to 206.58.200.1 (206.58.200.1), 30 hops max, 38 byte packets
1 206.58.200.39 (206.58.200.39) 3000.343 ms !H 3000.381 ms !H
3000.118 ms !H
3. Here is the topology:
ISP GW (206.58.200.1)
|
WIFI Modem (ISP Modem of which there is one Ethernet Connection, have
no access to its config, think it acts as a bridge)
|
My External Hub
| |
GW System Mail System
| |
My Internal Hub
|
Internal Network
I am almost completely convinced that there is a routing problem at
the ISP. What do you thing?
Regards, Patrick
Hello All,
I sat down the the ISP network engineer and had him do a traceroute back
to me and found that one of his switches was sending the return packets
to neverland. He fixed that and now it all up and working. Thanks Bob
for your help.
