brianleahy
Colonel Panic
I've got a Mac Mini server providing a web site and VPN via the internet. I've got all the needed ports forwarded on my cable modem and most of the time it all works beautifully.
Then every once in a while nobody can connect, even though the server seems to be running fine - and it (the server) can access the web with ease.
Invariably when this happens, I do a trace route from outside and see something like this:
Note that hop 12 says "Timed out".
I'm assuming this means that some router that is a necessary part of the access path to my server is not doing it's job. Am I right??
Is the problem node the one before the timeout? After? Or is the address of the problem node not shown?
Is there anything I could do differently on my end to prevent this?
Are there any magic words I might use with my ISP (TimeWarner/Roadrunner naturally) that will convince them that power-cycling my blasted cable modem isn't the way to fix this??!?!
Please help.
Then every once in a while nobody can connect, even though the server seems to be running fine - and it (the server) can access the web with ease.
Invariably when this happens, I do a trace route from outside and see something like this:
Code:
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
2 0 0 0 4.69.145.208 ae-4-90.edge9.dallas1.level3.net
3 0 1 0 4.28.152.110 roadrunner.edge9.dallas1.level3.net
4 25 31 31 66.109.6.178 ae-1-0.cr0.dfw10.tbone.rr.com
5 29 31 31 66.109.6.23 ae-2-0.cr0.chi30.tbone.rr.com
6 35 35 36 107.14.19.17 ae14.tr00.clmkohpe.mwrtn.rr.com
7 36 35 42 65.189.140.129 ae1.ar01.clmkohpe.mwrtn.rr.com
8 39 39 39 65.25.137.66 tge3-0-0.ncntoh1-rtr1.neo.rr.com
9 42 104 41 24.164.118.97 tge7-2-0.clevoh1-rtr01.neo.rr.com
10 42 42 42 24.164.113.129 tge9-3.lksdoh1-rtr1.neo.rr.com
11 43 43 43 24.164.111.44 tge1-1.elyroh1-swt402.neo.rr.com
12 Timed out Timed out Timed out -
13 62 52 51 my.home.IP.censored cpe-myIPHere.neo.res.rr.com
Trace Complete
Note that hop 12 says "Timed out".
I'm assuming this means that some router that is a necessary part of the access path to my server is not doing it's job. Am I right??
Is the problem node the one before the timeout? After? Or is the address of the problem node not shown?
Is there anything I could do differently on my end to prevent this?
Are there any magic words I might use with my ISP (TimeWarner/Roadrunner naturally) that will convince them that power-cycling my blasted cable modem isn't the way to fix this??!?!
Please help.
Last edited: