Can't access some websites -- same domain different subdomain

There are some Japanese flash game websites on a domain called web.fc2.com. I can access some but not others, getting a timeout error.

I can't get to ancho.web.fc2.com and detarou.web.fc2.com . I can get to pi3141592c147.web.fc2.com and yoinouchi.web.fc2.com . I've pinged all four and get very similar results - I know 'similar' is not 'exact' but I am not techy enough to read/understand ping results.

A possibly relevant pair of messages I get from pinging via dnsstuff.com are
- The destination appears to block unwanted UDP packets.
- There appears to be a firewall at <ip address> (hop 1) that blocks unwanted TCP packets.

Both my windows xp and my ubuntu box have the same problem, so it's not a hosts file issue or a system based blocking software. Might be my router?

Thank you...

Might I ask what browser you are using? Using my Google Chrome, I can access http://ancho.web.fc2.com/ & http://yoinouchi.web.fc2.com/

Pick your browser. Firefox, Chrome, IE. Doesn't work on any.

Gosh, I don't know. Does time of day matter? Other than that, I have no idea & wish you well.

No, I've never been able to access those as far as I know. Thanks for replying.

You're welcome. Good luck.

I can access this

and this too

so can I

so it is not website dependent, but localized to

a) your systems OR
b) your ISP

Tracert shows

Code:

Tracing route to web.fc2.com [b][208.71.106.36][/b]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  localrouter [192.168.0.1]
  2    24 ms    12 ms    12 ms  xxxxx
  3    12 ms    13 ms    16 ms  76.167.22.189
  4    14 ms    14 ms    14 ms  ae5.vnnyca2-rtr1.socal.rr.com [66.75.147.38]
  5    19 ms    23 ms    23 ms  be13-lsanca4-rtr1.socal.rr.com [66.75.147.3]
  6    16 ms    18 ms    34 ms  ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
  7    17 ms    42 ms    17 ms  ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
  8   221 ms   219 ms   211 ms  66.109.9.206
  9    25 ms    40 ms    26 ms  HIGHWINDS-NETWORK-GROUP.TenGigabitEthernet2-4.sar2.phx1.gblx.net [146.82.33.142]
 10    35 ms    36 ms    26 ms  1-4.r2.ph.hwng.net [69.16.191.74]
 11    32 ms    29 ms    28 ms  2-1.r1.la.hwng.net [69.16.191.37]
 12    29 ms    28 ms    28 ms  209.197.4.110
 13    28 ms    28 ms    28 ms  208.71.106.17
 14    27 ms    32 ms    29 ms  sw1.1732.la3.fc2.com [208.71.104.27]
 15    26 ms    28 ms    28 ms  hps0.fc2.com [b][208.71.106.36][/b]
Trace complete.

C:\Documents and Settings\Jeff>tracert pi3141592c147.web.fc2.com

Tracing route to pi3141592c147.web.fc2.com [b][208.71.106.39][/b]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  localrouter [192.168.0.1]
  2    13 ms    12 ms    12 ms  xxxx
  3    11 ms    14 ms    12 ms  76.167.22.189
  4    14 ms    12 ms    12 ms  ae5.vnnyca2-rtr1.socal.rr.com [66.75.147.38]
  5    21 ms    23 ms    23 ms  be13-lsanca4-rtr1.socal.rr.com [66.75.147.3]
  6    44 ms    17 ms    18 ms  ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
  7    28 ms    18 ms    18 ms  107.14.19.138
  8    18 ms    19 ms    18 ms  TenGigabitEthernet1-2.ar5.LAX1.gblx.net [64.208.
205.153]
  9    32 ms    25 ms    25 ms  64.209.102.174
 10    32 ms    27 ms    28 ms  2-1.r1.la.hwng.net [69.16.191.37]
 11    27 ms    28 ms    25 ms  209.197.4.106
 12    28 ms    28 ms    28 ms  sw1.1732.la3.fc2.com [208.71.104.27]
 13    30 ms    28 ms    28 ms  hps5.fc2.com [b][208.71.106.39][/b]

Trace complete.

both 'problem domains' are at the same location

Code:

C:\Documents and Settings\Jeff>nslookup ancho.web.fc2.com
Server:  dns-cac-lb-01.rr.com
Address:  209.18.47.61

Non-authoritative answer:
Name:    ancho.web.fc2.com
Address:  [b]208.71.106.61[/b]


C:\Documents and Settings\Jeff>nslookup detarou.web.fc2.com
Server:  dns-cac-lb-01.rr.com
Address:  209.18.47.61

Non-authoritative answer:
Name:    detarou.web.fc2.com
Address:  [b]208.71.106.61[/b]

and the tracert SHOULD look like

Code:

C:\Documents and Settings\Jeff>tracert detarou.web.fc2.com

Tracing route to detarou.web.fc2.com [208.71.106.61]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  localrouter [192.168.0.1]
  2    12 ms    25 ms    12 ms  xxx
  3    12 ms    13 ms    12 ms  76.167.22.189
  4    44 ms    14 ms    12 ms  ae5.vnnyca2-rtr1.socal.rr.com [66.75.147.38]
  5    21 ms    23 ms    23 ms  be13-lsanca4-rtr1.socal.rr.com [66.75.147.3]
  6    19 ms    18 ms    18 ms  ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
  7    17 ms    28 ms    20 ms  107.14.19.138
  8    16 ms    19 ms    19 ms  TenGigabitEthernet4-1.ar4.LAX1.gblx.net [64.209.93.65]
  9    34 ms    28 ms    28 ms  HIGHWINDS-NETWORK-GROUP.TenGigabitEthernet2-4.sar2.phx1.gblx.net [146.82.33.142]
 10    28 ms    36 ms    26 ms  1-4.r2.ph.hwng.net [69.16.191.74]
 11    28 ms    28 ms    28 ms  2-1.r1.la.hwng.net [69.16.191.37]
 12    33 ms    29 ms    31 ms  209.197.4.110
 13    30 ms    27 ms    28 ms  208.71.106.17
 14    28 ms    28 ms    28 ms  sw1.1732.la3.fc2.com [208.71.104.27]
 15    30 ms    28 ms    28 ms  hps13.fc2.com [208.71.106.61]

Trace complete.

Hi Jobeard, here is what I get on the nslookup and the traceroute. Since it happens on both computers it must be the router or as you suggest my ISP. What must I do to fix?

the RED stuff says your router(modem) is not correct
OR your TCP stack is a mess,
but how it found the Address: 208.71.106.61 is amazing.
We'll need to work on that.

Code:

1 2 ms <1 ms <1 ms 192.168.0.1   <<YOUR ROUTER ADDRESS
2 14 ms 14 ms 14 ms adsl-99-58-75-254.dsl.pltn13.sbcglobal.net [99.5 8.75.254]  << YOUR ISP GATEWAY ADDRESS
3 15 ms 14 ms 13 ms dist2-vlan62.pltnca.sbcglobal.net [99.36.71.2]  <<STILL inside your ISP
4 * * * [COLOR="Red"]Request timed out.   << first node outside your ISP[/COLOR]
5 * * * Request timed out.

the network beyond your ISP is questionable, but let's fix the router/modem and do this again.

Using an Admin login, get a command prompt and enter

Code:

netsh winsock reset catalog
netsh int ip reset c:\resetlog.txt

1. Disconnect the system from the router
2. Power off the router
3. reboot the system and while waiting for it, power on the router
4. login again and then connect the system to the router

Now get a command prompt again and run IPCONFIG /ALL >MYTCP.txt
follow-up with a copy/paste of mytcp.txt contents . . .

Good morning
Everything went without a hitch and here are the ipconfig results

Code:

Windows IP Configuration
        Host Name . . . . . . . . . . . . : noneother
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
        Physical Address. . . . . . . . . : 00-A0-D1-49-0A-59

Ethernet adapter Wireless Network Connection:
        Connection-specific DNS Suffix  . : 
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
        Physical Address. . . . . . . . . : 00-13-02-B2-85-1D
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.3
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 192.168.0.1
        Lease Obtained. . . . . . . . . . : Saturday, May 28, 2011 7:09:07 AM
        Lease Expires . . . . . . . . . . : Sunday, May 29, 2011 7:09:07 AM

that's perfect; try these - - your results should look like the BLUE data

Code:

[B]nslookup google.com.[/B]   <<note trailing PERIOD
Server:  dns-cac-lb-01.rr.com
Address:  209.18.47.61

[COLOR="Blue"]Name:    google.com
Addresses:  74.125.224.146, 74.125.224.147, 74.125.224.148, 74.125.224.144
	  74.125.224.145[/COLOR]

[B]nslookup yahoo.com.[/B]    <<note trailing PERIOD
Server:  dns-cac-lb-01.rr.com
Address:  209.18.47.61

[COLOR="Blue"]Name:    yahoo.com
Addresses:  69.147.125.65, 72.30.2.43, 98.137.149.56, 209.191.122.70
	  67.195.160.76[/COLOR]

[/COLOR]

then try this to each one:

Code:

[B]tracert google.com[/B]  << MISSING THE TRAILING PERIOD[B]
[B]tracert yahoo.com[/B]

AND FINALLY, try

Code:

[B]tracert ancho.web.fc2.com[/B]

again
We are looking for the * * * Timeouts and if you see any in the path, COPY/PASE the whole tracert data . . .

My nslookups are different ... :/
Is it looking to 192.168.0.1 as a dns server? Because I don't think that's right...

Code:

C:\Documents and Settings\fallinghawks>nslookup google.com.
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.0.1

Non-authoritative answer:
Name:    google.com
Addresses:  74.125.224.115, 74.125.224.112, 74.125.224.113, 74.125.224.116
          74.125.224.114

C:\Documents and Settings\fallinghawks>nslookup yahoo.com.
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.0.1

Non-authoritative answer:
Name:    yahoo.com
Addresses:  69.147.125.65, 72.30.2.43, 98.137.149.56, 209.191.122.70
          67.195.160.76

Traceroutes are slow since I had a bunch of other stuff running at the time. It found google and yahoo, but crapped out on ancho.

Code:

C:\Documents and Settings\fallinghawks>tracert google.com

Tracing route to google.com [74.125.224.144]
over a maximum of 30 hops:

  1     3 ms    <1 ms    <1 ms  192.168.0.1
  2    13 ms    14 ms    14 ms  adsl-99-35-223-254.dsl.pltn13.sbcglobal.net [99.
35.223.254]
  3    14 ms    15 ms    14 ms  dist2-vlan60.pltnca.sbcglobal.net [76.197.23.194
]
  4    14 ms    14 ms    14 ms  ag2-10g0-12-3-0.pltnca.sbcglobal.net [151.164.10
3.2]
  5    15 ms    16 ms    15 ms  ppp-151-164-52-213.rcsntx.swbell.net [151.164.52
.213]
  6    15 ms    17 ms    15 ms  gar7.sffca.ip.att.net [12.122.79.97]
  7    20 ms    19 ms    19 ms  cr1.sffca.ip.att.net [12.122.110.118]
  8    18 ms    18 ms    18 ms  cr1.sffca.ip.att.net [12.123.15.109]
  9    20 ms    19 ms    20 ms  cr81.sj2ca.ip.att.net [12.122.1.118]
 10    19 ms    21 ms    17 ms  gar4.sn1ca.ip.att.net [12.122.110.61]
 11    17 ms    17 ms    17 ms  12.248.108.10
 12    23 ms    17 ms    19 ms  216.239.49.168
 13    19 ms    18 ms    18 ms  64.233.174.119
 14    19 ms    18 ms    99 ms  74.125.224.144

Trace complete.

C:\Documents and Settings\fallinghawks>tracert yahoo.com

Tracing route to yahoo.com [98.137.149.56]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    14 ms    15 ms    15 ms  adsl-99-35-223-254.dsl.pltn13.sbcglobal.net [99.
35.223.254]
  3    13 ms    14 ms    13 ms  dist1-vlan60.pltnca.sbcglobal.net [76.197.23.193
]
  4    14 ms    15 ms    13 ms  ag1-10g0-12-2-0.pltnca.sbcglobal.net [151.164.10
2.222]
  5    18 ms    16 ms    16 ms  ppp-151-164-52-163.rcsntx.swbell.net [151.164.52
.163]
  6    16 ms    16 ms    17 ms  asn10310-yahoo-10g.eqsjca.sbcglobal.net [151.164
.248.58]
  7    17 ms    17 ms    17 ms  ae-0-d161.msr1.sp1.yahoo.com [216.115.107.59]
  8    17 ms    18 ms    16 ms  et-18-1.fab4-1-gdc.sp2.yahoo.com [98.136.16.29]

  9    17 ms    17 ms    16 ms  te-9-3.bas1-1-prd.sp2.yahoo.com [67.195.130.102]

 10    17 ms    18 ms    17 ms  ir1.fp.vip.sp2.yahoo.com [98.137.149.56]

Trace complete.

C:\Documents and Settings\fallinghawks>tracert ancho.web.fc2.com

Tracing route to ancho.web.fc2.com [208.71.106.61]
over a maximum of 30 hops:

  1     1 ms     2 ms    <1 ms  192.168.0.1
  2    14 ms    14 ms    13 ms  adsl-99-35-223-254.dsl.pltn13.sbcglobal.net [99.
35.223.254]
  3    13 ms    14 ms    13 ms  dist1-vlan62.pltnca.sbcglobal.net [99.36.71.1]
  4     *        *        *     Request timed out.
  5

Yes that IS right, but it's indirect. NOTICE the ipconfig data shows

Code:

        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        [B]DNS Servers . . . . . . . . . . . : 192.168.0.1[/B]

that is very common.
The action for a DNS request on port 53 received by the router is to just forward it to the WAN port connected to your modem and then to your ISP where it gets resolved.
This can be corrected, but would not appear to be YOUR issue.

did not effect the results; your times on line 5

Code:

5    15 ms    16 ms    15 ms ...

are very typical

my nslookup google.com.

Code:

Addresses:  74.125.224.[B]146[/B], 74.125.224.[B]147[/B], 74.125.224.[B]148[/B], 74.125.224.[B]144[/B]
          74.125.224.145

differs only in the last octet (ie three digits) from yours

Code:

Name:    google.com
Addresses:  74.125.224.[B]115[/B], 74.125.224.[B]112[/B], 74.125.224.[B]113[/B], 74.125.224.[B]116[/B]
          74.125.224.[B]114[/B]

Using another network tool, I find the Google owns

Code:

NetRange:       74.125.0.0 - 74.125.255.255
CIDR:           74.125.0.0/16

which means it has everything in 74.125.*.*
so your nslookup is returning good results.

I can perform tracert ancho.web.fc2.com all the way and get the final Trace Complete without any timeouts.

Got to go for now - - - if you have the time google for Black Hole Routers and Setting MTU. Will discuss with you asap . . ..

Good to know about the 192.168.0.1 and DNS - I am learning a ton here thanks to you. I also will be away for the day but will google for those this evening. BTW, had to reboot the router this morning to connect wireless, not sure why.

3/31/11
I took a look at the routing table. Does that entry for 192.168.0.0 mean anything?

Code:

Destination 	Mask 	Gateway 	Metric 	Active
76.254.15.254 	255.255.255.255 	0.0.0.0 	0 	Yes
192.168.0.0 	255.255.255.0 	0.0.0.0 	0 	Yes
0.0.0.0 	0.0.0.0 	76.254.15.254 	0 	Yes

Hate to do this, but -- bump.

Code:

Destination 	Mask 	           Gateway 	     Metric 	Active
76.254.15.254      255.255.255.255  [COLOR="Red"]0.0.0.0[/COLOR] 	     0 	Yes[B][1][/B]
192.168.0.0        255.255.255.0     [COLOR="Red"]0.0.0.0 [/COLOR]	     0 	Yes[B][2][/B]
0.0.0.0             0.0.0.0         76.254.15.254    0 	Yes[B][3][/B]

[3] is the default route; notice ip/mask is as broad as it gets
[1] is an example of the most specific route; one address and the mask says that's all yoiu get
[2]is routing for anything on your LAN

the output you show is different than mine and the 0.0.0.0 entries for gateway are puzzling

here's mine

Code:

C:\Documents and Settings\Jeff>route print
================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f b0 3d bc 1d ...... Realtek RTL8139 Family PCI Fast Ethernet NIC -
acket Scheduler Miniport
================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     192.168.0.4       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0      192.168.0.4     192.168.0.4       20
      192.168.0.4  255.255.255.255        127.0.0.1       127.0.0.1       20
    192.168.0.255  255.255.255.255      192.168.0.4     192.168.0.4       20
        224.0.0.0        240.0.0.0      192.168.0.4     192.168.0.4       20
  255.255.255.255  255.255.255.255      192.168.0.4     192.168.0.4       1
Default Gateway:       192.168.0.1
================================================================
Persistent Routes:
  None

I got a new computer with Win7. Still am unable to get to the sites listed.

This is my route print - somewhat lengthier than yours. There are entries for IPv6 but I edited those out.

Should I attempt to edit my router's table?

Code:

===========================================================================
Interface List
 17...d0 df 9a 1e 3d ca ......Microsoft Virtual WiFi Miniport Adapter
 13...d0 df 9a 1e 3d ca ......Realtek RTL8188CE Wireless LAN 802.11n PCI-E NIC
 11...e8 9a 8f 4a 8a 39 ......Atheros AR8152 PCI-E Fast Ethernet Controller
  1...........................Software Loopback Interface 1
 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 12...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
 14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1      192.168.0.4     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link       192.168.0.4     26
  169.254.255.255  255.255.255.255         On-link       192.168.0.4    281
      192.168.0.0    255.255.255.0         On-link       192.168.0.4    281
      192.168.0.4  255.255.255.255         On-link       192.168.0.4    281
    192.168.0.255  255.255.255.255         On-link       192.168.0.4    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link       192.168.0.4    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link       192.168.0.4    281
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      169.254.0.0      255.255.0.0      192.168.0.4       1
===========================================================================

leave the routing table alone

use google to find disable ipv6 and apply the win/7 fix

I don't mean to question your expertise, but is that really necessary? The problem still exists on the Ubuntu box and of course the WinXP laptop. IMHO IPv6 is or should be irrelevant to the problem.

question all you like - - that's how we all learn.

Our routers just don't handle IPv6 yet. Linksys is just terriible and few really work.

We can't shutdown IPv6 in the router per se, so we make sure our systems only
make IPv4 requests.

Then too, all the reasons for using IPv6 are targeted for the Internet Backbone or
hugh companies like GM, IBM, Verizon where there's far more system internally to the domain.

Think about it; our person home system NEVER have 253 devices attached
(the limit for one subnet), so why do we need to coerse IPv6 into a subnet with only 5-6 devices?