Grep
Senior Member
Hi guys
I am turning here because I have tried everywhere else and no go. I have a client with a dynalias.com alias tied to a netgear DG834 which works 100%. I have portforwarded ports like 80/81/22/3389 etc etc and EVERYTHING works except port 80 which died last week for some reason.
Port 80 is port forwarded to an exchange server and it is definitely listening on 80, I also enabled 81 and the client is able to use http://client.dnsalias.com:81/exchange but just not 80. If I telnet locally on the exchange server to port 80 its fine. I have recreated the firewall rules, I have changed ADSL accounts and even changed ADSL routers and just no go.
I then installed IIS onto another server, pointed 80 to that box and still no go. I have run tcptraceroute and this is what I get:
su-2.05b# tcptraceroute **client**.dnsalias.com 80
Selected device xl0, address 196.25.42.234, port 1839 for outgoing packets
Tracing the path to kanteysvpn.dnsalias.com (165.145.240.249) on TCP port 80, 30 hops max
1 196.25.42.233 (196.25.42.233) 9.280 ms 9.699 ms 9.724 ms
2 196.25.165.53 (196.25.165.53) 9.905 ms 8.549 ms 9.729 ms
3 wfor-ip-esr-2-pos-1-0-0.telkom-ipnet.co.za (196.43.24.214) 9.875 ms 9.573 ms 9.710 ms
4 * wfor-ip-esr-2-pos-1-0-0.telkom-ipnet.co.za (196.43.24.214) 23.467 ms !A *
su-2.05b# tcptraceroute **client**.dnsalias.com 81
Selected device xl0, address 196.25.42.234, port 4206 for outgoing packets
Tracing the path to kanteysvpn.dnsalias.com (165.145.240.249) on TCP port 81, 30 hops max
1 196.25.42.233 (196.25.42.233) 6.900 ms 9.122 ms 9.734 ms
2 196.25.165.53 (196.25.165.53) 9.866 ms 7.827 ms 6.995 ms
3 wfor-ip-esr-2-pos-1-0-0.telkom-ipnet.co.za (196.43.24.214) 8.079 ms 14.157 ms 7.565 ms
4 * * *
5 dsl-145-240-249.telkomadsl.co.za (165.145.240.249) [open] 14.492 ms * 33.484 ms
Is it at all possible that telkom blocks ports? I am just stumped.
I am turning here because I have tried everywhere else and no go. I have a client with a dynalias.com alias tied to a netgear DG834 which works 100%. I have portforwarded ports like 80/81/22/3389 etc etc and EVERYTHING works except port 80 which died last week for some reason.
Port 80 is port forwarded to an exchange server and it is definitely listening on 80, I also enabled 81 and the client is able to use http://client.dnsalias.com:81/exchange but just not 80. If I telnet locally on the exchange server to port 80 its fine. I have recreated the firewall rules, I have changed ADSL accounts and even changed ADSL routers and just no go.
I then installed IIS onto another server, pointed 80 to that box and still no go. I have run tcptraceroute and this is what I get:
su-2.05b# tcptraceroute **client**.dnsalias.com 80
Selected device xl0, address 196.25.42.234, port 1839 for outgoing packets
Tracing the path to kanteysvpn.dnsalias.com (165.145.240.249) on TCP port 80, 30 hops max
1 196.25.42.233 (196.25.42.233) 9.280 ms 9.699 ms 9.724 ms
2 196.25.165.53 (196.25.165.53) 9.905 ms 8.549 ms 9.729 ms
3 wfor-ip-esr-2-pos-1-0-0.telkom-ipnet.co.za (196.43.24.214) 9.875 ms 9.573 ms 9.710 ms
4 * wfor-ip-esr-2-pos-1-0-0.telkom-ipnet.co.za (196.43.24.214) 23.467 ms !A *
su-2.05b# tcptraceroute **client**.dnsalias.com 81
Selected device xl0, address 196.25.42.234, port 4206 for outgoing packets
Tracing the path to kanteysvpn.dnsalias.com (165.145.240.249) on TCP port 81, 30 hops max
1 196.25.42.233 (196.25.42.233) 6.900 ms 9.122 ms 9.734 ms
2 196.25.165.53 (196.25.165.53) 9.866 ms 7.827 ms 6.995 ms
3 wfor-ip-esr-2-pos-1-0-0.telkom-ipnet.co.za (196.43.24.214) 8.079 ms 14.157 ms 7.565 ms
4 * * *
5 dsl-145-240-249.telkomadsl.co.za (165.145.240.249) [open] 14.492 ms * 33.484 ms
Is it at all possible that telkom blocks ports? I am just stumped.