- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Depending on where I am, I am having difficulty getting to my sites locating on server1.wirenine.com. From my home computer (FIOS), my traceroute looks like this:
C:Documents and SettingsMaulik>tracert www.outprove.com
Tracing route to outprove.com [208.43.212.208]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms fios_router.home [192.168.1.1]
2 52 ms 7 ms 7 ms L100.WASHDC-VFTTP-125.verizon-gni.net [173.66.17
0.1]
3 9 ms 10 ms 9 ms G5-0-5-1725.WASHDC-LCR-07.verizon-gni.net [130.8
1.140.110]
4 8 ms 10 ms 9 ms so-3-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net
[130.81.29.0]
5 8 ms 12 ms 12 ms 0.so-4-1-0.XL3.IAD8.ALTER.NET [152.63.30.2]
6 51 ms 52 ms 52 ms 0.so-1-2-0.XL3.DFW7.ALTER.NET [152.63.98.77]
7 51 ms 52 ms 52 ms TenGigE0-4-1-0.GW4.DFW13.ALTER.NET [152.63.101.5
4]
8 51 ms 54 ms 52 ms internapGIGE1-gw.customer.alter.net [65.208.15.2
30]
9 51 ms 54 ms 52 ms border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
191.83]
10 51 ms 52 ms 54 ms te1-2.cer01.sr01.dal01.networklayer.com [216.52.
189.30]
11 53 ms 59 ms 57 ms po1.fcr04.sr05.dal01.networklayer.com [66.228.11
8.214]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * ^C
You see it times out right @ po1.fcr04.sr05.dal01.networklayer.com.
But if I go to other servers that I have access to in other parts of the country, I can get to it:
C:Usersmshah>tracert www.outprove.com
Tracing route to outprove.com [208.43.212.208]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 64.34.171.2
2 1 ms 1 ms 1 ms 1ge-gi2-22.wdc-sp2-cor-1.peer1.net [216.187.120.
229]
3 <1 ms 1 ms 1 ms 10ge.xe-0-0-0.wdc-eqx-dis-1.peer1.net [216.187.1
15.233]
4 2 ms 2 ms 2 ms te3-5.bbr01.eq01.wdc01.networklayer.com [206.223
.115.185]
5 27 ms 27 ms 27 ms po3.bbr02.tl01.atl01.networklayer.com [173.192.1
8.153]
6 34 ms 34 ms 34 ms po7.bbr02.eq01.dal01.networklayer.com [173.192.1
8.134]
7 34 ms 34 ms 34 ms po5.dar02.sr01.dal01.networklayer.com [173.192.1
8.203]
8 69 ms 34 ms 34 ms po2.fcr04.sr05.dal01.networklayer.com [66.228.11
8.218]
9 35 ms 34 ms 41 ms server1.wirenine.com [208.43.212.208]
As you can see, that route takes it to po2.fcr04.sr05.dal01.networklayer.com, which seems to route correctly.
I don't know what to do here! It works from every other place I've tried *except* from my home computer (FIOS). Anything I can do to affect the routing from where I am?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, it doesnt look like it is a problem on your end. The problem is with networklayer.com. More specifically with the router at ...
11 53 ms 59 ms 57 ms po1.fcr04.sr05.dal01.networklayer.com [66.228.118.214]
This hop then routes you to a router that is not responding either because it is not supposed to respond or is otherwise disabled.
The only thing you can do is contact networklayer.com and report the problem. Provide them with the tracert so they can look at the network.
But you are navigating your network, and Verizon's network just fine and making it all the way to networklayer, so the problem is on networklayers's side.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the response and attention, spacedebris.
Just to update for the record, it looks like the issue was with Wirenine, and their firewall. They must have done something to their firewall that prevented some traffic but let other traffic in. After contacting them, they flushed their firewall settings and now all is right.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok, that is great to hear/read.
Please mark as solved.