Infamous Request Timed Out when pinging

terrified · 09-04-2009, 02:09 AM

Okay well obviously, i can't ping any website on the internet for some reason. Everytime I do i get a "Request Timed Out", or "Destination net Unreachable". I use the ZoneAlarm Internet Security Suite 8.0. I have enabled ICMP Echo Requests on the Windows Firewall, and on the ZoneAlarm firewall in the options. I'm still boggled why I can't ping other websites? I've uninstalled the firewall, didn't work. Turned them off and didn't work. I'm through a linksys router, but even plugged into my normal Modem, with firewalls turned off, i still can't ping outside. I've also already reset the tcp/ip sockets and it didn't help either.

Suncoast · 09-04-2009, 10:20 AM

Welcome to TSF. I can't believe you're the first one to think of the name Terrified.

And I hope that's not your current state of mind.

Not all web sites permit pinging. Are web sites coming up OK in your web browser? What happens when you ping google.com? If nothing, do a trace route to google.com the same way you ping.

example: tracert www.google.com

When you get three rows of these
* * *
* * *
* * *

Hit Control-C to stop it, it's done. These often stop close to, but not quite at the destination site.

And... Many routers have a Diagnostic screen you can ping from.

And btw, you should only use one firewall at a time.

terrified · 09-04-2009, 10:32 AM

Lol I was amazed my user wasnt taken either. Guess I'm good like that. I'm only using 1 firewall which is my ZoneAlarm Pro.
Heres my tracert

1 1 ms 1 ms 1 ms 192.168.2.1
2 38 ms 35 ms 35 ms grndchn-jb-adsl-255.camtel.net [209.12.233.1]
3 * * * Request timed out.
4 cs-7206-vxr-core-gw.camtel.net [207.191.12.34] reports: Destination net un
reachable.

and heres my ping...

C:\Users\Tsukasa>ping www.google.com

Pinging www.l.google.com [64.233.169.103] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 207.191.12.34: Destination net unreachable.
Request timed out.

Ping statistics for 64.233.169.103:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

It's quite strange.

terrified · 09-04-2009, 10:33 AM

Oh and i can check websites just fine. But I would like to ping. And I never can =\

terrified · 09-04-2009, 10:43 AM

well i was told the ping was turned off on the network. kinda dumb. I called the company about it. So it's no doubt impossible for me to get it enabled.

Suncoast · 09-04-2009, 10:56 AM

They must have had some issue with it. So you'll either have to live with it or find another company. It's a valuable troubleshooting tool, so it is unfortunate.

Suncoast · 09-04-2009, 11:07 AM

Quote:

Originally Posted by terrified

4 cs-7206-vxr-core-gw.camtel.net [207.191.12.34] reports: Destination net un
reachable.

Reply from 207.191.12.34: Destination net unreachable.

That's a Time Warner network. I'm fairly certain they don't block pings.

terrified · 09-04-2009, 11:18 AM

Time warner i believe gets ips starting at 210.0.0, so its fairly close. I noticed this when pinging from a SHELL account. I might call my company back and say it'd be nice to have for school because i can use it to troubleshoot things. But that depends if they can enable it on certain networks or not. Thanks for the help =]

Suncoast · 09-04-2009, 11:30 AM

Code:

root@Ops7:~# whois 207.191.0.0

OrgName:    Xspedius Communications Co.
OrgID:      XSPED
Address:    5555 Winghaven Blvd
City:       O'Fallon
StateProv:  MO
PostalCode: 63366
Country:    US

NetRange:   207.191.0.0 - 207.191.127.255
CIDR:       207.191.0.0/17
NetName:    XSPEDIUS-BLK-1
NetHandle:  NET-207-191-0-0-1
Parent:     NET-207-0-0-0-0
NetType:    Direct Allocation
NameServer: DNS1.XSPEDIUS.NET
NameServer: DNS2.XSPEDIUS.NET
NameServer: DNS3.XSPEDIUS.NET
NameServer: DNS4.XSPEDIUS.NET
Comment:
RegDate:    1999-02-22
Updated:    2009-07-15

OrgAbuseHandle: TWTAD-ARIN
OrgAbuseName:   tw telecom Abuse Desk
OrgAbusePhone:  +1-800-898-6473
OrgAbuseEmail:  abuse@twtelecom.net

OrgNOCHandle: TDN1-ARIN
OrgNOCName:   TWTC Data NOC
OrgNOCPhone:  +1-800-898-6473
OrgNOCEmail:  support@twtelecom.net

OrgTechHandle: ZI80-ARIN
OrgTechName:   Time Warner IP Administrator
OrgTechPhone:  +1-800-829-0420
OrgTechEmail:  ipadmin@twtelecom.com

# ARIN WHOIS database, last updated 2009-09-03 20:00
# Enter ? for additional hints on searching ARIN's WHOIS database.
root@Ops7:~#

Suncoast · 09-04-2009, 11:50 AM

The device at 207.191.12.34 is the one blocking us. I can ping and trace to that point, as can you. So you can at least test your connection to that point. I would write that IP down somewhere.

terrified · 09-04-2009, 01:08 PM

Well my IP starts at 209.x.x, not 207. which is my IPv4. idk why it shows the 207.x.x. Your helping me out nicely XD

Suncoast · 09-04-2009, 02:58 PM

Look at the trace route you posted. That's the network ID for the device that's blocking ICMP Echo, also called ping. And we can both trace to it. So whomever controls that device controls the blockage. Looking at the network though, you appear to be on the third tier. Looks like Time Warner is supplying the backbone connectivity to Cameron Communications of Sulpher, LA through intermediary Xspedius. I can tell a lot from a trace route.

09-04-2009, 02:09 AM	#1 (permalink)
terrified Registered User Join Date: Sep 2009 Posts: 6 OS: Windows Vista Home Premium	Infamous Request Timed Out when pinging Okay well obviously, i can't ping any website on the internet for some reason. Everytime I do i get a "Request Timed Out", or "Destination net Unreachable". I use the ZoneAlarm Internet Security Suite 8.0. I have enabled ICMP Echo Requests on the Windows Firewall, and on the ZoneAlarm firewall in the options. I'm still boggled why I can't ping other websites? I've uninstalled the firewall, didn't work. Turned them off and didn't work. I'm through a linksys router, but even plugged into my normal Modem, with firewalls turned off, i still can't ping outside. I've also already reset the tcp/ip sockets and it didn't help either. Last edited by terrified; 09-04-2009 at 02:11 AM.

09-04-2009, 10:20 AM	#2 (permalink)
Suncoast Registered User Join Date: Jul 2009 Location: Largo, FL, USA Posts: 389 OS: XPP, Linux, 2003, Cisco	Re: Infamous Request Timed Out when pinging Welcome to TSF. I can't believe you're the first one to think of the name Terrified. And I hope that's not your current state of mind. Not all web sites permit pinging. Are web sites coming up OK in your web browser? What happens when you ping google.com? If nothing, do a trace route to google.com the same way you ping. example: tracert www.google.com When you get three rows of these * * * * * * * * * Hit Control-C to stop it, it's done. These often stop close to, but not quite at the destination site. And... Many routers have a Diagnostic screen you can ping from. And btw, you should only use one firewall at a time.

09-04-2009, 10:32 AM	#3 (permalink)
terrified Registered User Join Date: Sep 2009 Posts: 6 OS: Windows Vista Home Premium	Re: Infamous Request Timed Out when pinging Lol I was amazed my user wasnt taken either. Guess I'm good like that. I'm only using 1 firewall which is my ZoneAlarm Pro. Heres my tracert 1 1 ms 1 ms 1 ms 192.168.2.1 2 38 ms 35 ms 35 ms grndchn-jb-adsl-255.camtel.net [209.12.233.1] 3 * * * Request timed out. 4 cs-7206-vxr-core-gw.camtel.net [207.191.12.34] reports: Destination net un reachable. and heres my ping... C:\Users\Tsukasa>ping www.google.com Pinging www.l.google.com [64.233.169.103] with 32 bytes of data: Request timed out. Request timed out. Reply from 207.191.12.34: Destination net unreachable. Request timed out. Ping statistics for 64.233.169.103: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), It's quite strange.

09-04-2009, 10:33 AM	#4 (permalink)
terrified Registered User Join Date: Sep 2009 Posts: 6 OS: Windows Vista Home Premium	Re: Infamous Request Timed Out when pinging Oh and i can check websites just fine. But I would like to ping. And I never can =\

09-04-2009, 10:43 AM	#5 (permalink)
terrified Registered User Join Date: Sep 2009 Posts: 6 OS: Windows Vista Home Premium	Re: Infamous Request Timed Out when pinging well i was told the ping was turned off on the network. kinda dumb. I called the company about it. So it's no doubt impossible for me to get it enabled.

09-04-2009, 10:56 AM	#6 (permalink)
Suncoast Registered User Join Date: Jul 2009 Location: Largo, FL, USA Posts: 389 OS: XPP, Linux, 2003, Cisco	Re: Infamous Request Timed Out when pinging They must have had some issue with it. So you'll either have to live with it or find another company. It's a valuable troubleshooting tool, so it is unfortunate.

09-04-2009, 11:18 AM	#8 (permalink)
terrified Registered User Join Date: Sep 2009 Posts: 6 OS: Windows Vista Home Premium	Re: Infamous Request Timed Out when pinging Time warner i believe gets ips starting at 210.0.0, so its fairly close. I noticed this when pinging from a SHELL account. I might call my company back and say it'd be nice to have for school because i can use it to troubleshoot things. But that depends if they can enable it on certain networks or not. Thanks for the help =]

09-04-2009, 11:50 AM	#10 (permalink)
Suncoast Registered User Join Date: Jul 2009 Location: Largo, FL, USA Posts: 389 OS: XPP, Linux, 2003, Cisco	Re: Infamous Request Timed Out when pinging The device at 207.191.12.34 is the one blocking us. I can ping and trace to that point, as can you. So you can at least test your connection to that point. I would write that IP down somewhere.

09-04-2009, 01:08 PM	#11 (permalink)
terrified Registered User Join Date: Sep 2009 Posts: 6 OS: Windows Vista Home Premium	Re: Infamous Request Timed Out when pinging Well my IP starts at 209.x.x, not 207. which is my IPv4. idk why it shows the 207.x.x. Your helping me out nicely XD

09-04-2009, 02:58 PM	#12 (permalink)
Suncoast Registered User Join Date: Jul 2009 Location: Largo, FL, USA Posts: 389 OS: XPP, Linux, 2003, Cisco	Re: Infamous Request Timed Out when pinging Look at the trace route you posted. That's the network ID for the device that's blocking ICMP Echo, also called ping. And we can both trace to it. So whomever controls that device controls the blockage. Looking at the network though, you appear to be on the third tier. Looks like Time Warner is supplying the backbone connectivity to Cameron Communications of Sulpher, LA through intermediary Xspedius. I can tell a lot from a trace route.