- Posts: 521
- Thank you received: 0
504 Gateway Unreachable server ...PLEASE HELP
21 years 1 week ago #1734
by tfs
Thanks,
Tom
Replied by tfs on topic Re: 504 Gateway Unreachable server ...PLEASE HELP
That's why I have been gone.
OBVIOUSLY, I am not needed. Oh the pain, the pain.
OBVIOUSLY, I am not needed. Oh the pain, the pain.
Thanks,
Tom
21 years 1 week ago #1735
by tfs
Thanks,
Tom
Replied by tfs on topic Re: 504 Gateway Unreachable server ...PLEASE HELP
If you get the "Destination unreachable", a router along the way had no where to go (as Sahirh said, a problem with the default gateway). It apparently got to 195.226.227.105 and that device sent back a message to you saying there is no way to get to that address from that device and there is no default gateway to go out.
If the router can get to the network that that address is on, but there is no response (if the machine were turned of, for example), you would get "Request timed out".
If the router can get to the network that that address is on, but there is no response (if the machine were turned of, for example), you would get "Request timed out".
Thanks,
Tom
21 years 1 week ago #1743
by sahirh
Sahir Hidayatullah.
Firewall.cx Staff - Associate Editor & Security Advisor
tftfotw.blogspot.com
Replied by sahirh on topic Re: 504 Gateway Unreachable server ...PLEASE HELP
Sahir said:
*slaps head in disgust* what was I thinking there.. it was supposed to read as "your packets can't find their way out of the 195.226.227.105 router"
Tom's post above this explains the 'Destination net unreachable' message correctly.
Hope its sorted
your packets cant find your way to the 195.226.227.105 net
*slaps head in disgust* what was I thinking there.. it was supposed to read as "your packets can't find their way out of the 195.226.227.105 router"
Tom's post above this explains the 'Destination net unreachable' message correctly.
Hope its sorted
Sahir Hidayatullah.
Firewall.cx Staff - Associate Editor & Security Advisor
tftfotw.blogspot.com
21 years 1 week ago #1753
by tfs
Thanks,
Tom
Replied by tfs on topic Re: 504 Gateway Unreachable server ...PLEASE HELP
Did anything leak out??????? :lol:
Thanks,
Tom
20 years 7 months ago #3425
by ice
Replied by ice on topic 'Destination net unreachable ' but reachable !
Hi all.
I just bumped into your site on a google search & think it's nice.
Afterall , it has nice fundamentall tutorials.
I have a problem with ping/tracerout'ing sites.I type www.microsoft.com in the IE & the microsoft site appears.ok ,
i go to command prompt and enter : ping www.microsoft.com
& I get :
Pinging www2.microsoft.akadns.net [207.46.156.252] with 32 bytes of data:
Reply from 217.218.80.5: Destination net unreachable.
Reply from 217.218.80.5: Destination net unreachable.
Reply from 217.218.80.5: Destination net unreachable.
Reply from 217.218.80.5: Destination net unreachable.
Ping statistics for 207.46.156.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
& also from traceroute :
Tracing route to www2.microsoft.akadns.net [207.46.156.252]
over a maximum of 30 hops:
1 185 ms 171 ms 171 ms 217.218.80.5
2 217.218.80.5 reports: Destination net unreachable.
Trace complete.
What's wrong?
I use a dialup connection & I have Sygate Personal Firewall Installed.
Thanks in advance
I just bumped into your site on a google search & think it's nice.
Afterall , it has nice fundamentall tutorials.
I have a problem with ping/tracerout'ing sites.I type www.microsoft.com in the IE & the microsoft site appears.ok ,
i go to command prompt and enter : ping www.microsoft.com
& I get :
Pinging www2.microsoft.akadns.net [207.46.156.252] with 32 bytes of data:
Reply from 217.218.80.5: Destination net unreachable.
Reply from 217.218.80.5: Destination net unreachable.
Reply from 217.218.80.5: Destination net unreachable.
Reply from 217.218.80.5: Destination net unreachable.
Ping statistics for 207.46.156.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
& also from traceroute :
Tracing route to www2.microsoft.akadns.net [207.46.156.252]
over a maximum of 30 hops:
1 185 ms 171 ms 171 ms 217.218.80.5
2 217.218.80.5 reports: Destination net unreachable.
Trace complete.
What's wrong?
I use a dialup connection & I have Sygate Personal Firewall Installed.
Thanks in advance
20 years 7 months ago #3426
by Chris
Chris Partsenidis.
Founder & Editor-in-Chief
www.Firewall.cx
Replied by Chris on topic Re: 504 Gateway Unreachable server ...PLEASE HELP
I wouldn't say that your personal Firewall is the problem here, however it would most likely block the incoming replies from your traceroute/ping.
One reason you won't get any ping replies from microsoft is because they do block ICMP Echo's (which is what your sending) and receiving (or expecting to receive) ICMP Echo replies.
It's really not all that of a catastophy not being able to receive any ping replies from microsoft's site and I wouldn't loose any sleep over it! You can try pinging www.google.com and you will see that you are receiving ping replies. If not - you need to modify your personal firewall to allow them through!
Hope this helps!
One reason you won't get any ping replies from microsoft is because they do block ICMP Echo's (which is what your sending) and receiving (or expecting to receive) ICMP Echo replies.
It's really not all that of a catastophy not being able to receive any ping replies from microsoft's site and I wouldn't loose any sleep over it! You can try pinging www.google.com and you will see that you are receiving ping replies. If not - you need to modify your personal firewall to allow them through!
Hope this helps!
Chris Partsenidis.
Founder & Editor-in-Chief
www.Firewall.cx
Time to create page: 0.146 seconds