Cannot Access certain sites

[lordsmurf]

Uninstall TCP/IP and re-install it.

HUH?....were not using DOS (Trumpet Winsock) anymore

You can just right click on the connection and repair it
you can also:
ipconfig/flushdns
arp -d
tracert to the site (asked this before)
check if it's in IE's restricted sites

I still haven't seen the results to my other questions

You sometimes still have to do this in Windows.

[lordsmurf]

Also, do you have some sort of DNS server specified in Windows or in your router?

[TBoneit]

Try repairing your TCP/IP using WinsockFix by Option^Explicit Software Solutions

It removes the TCP/Ip and reinstalls it. Many times that will fix connection to the internet problems.

OTOH if you can log into the router, many times the router is 192.168.1.1 for example that is our DSL modems built-in 4 port router. Others could be different

[dudesmn]

actually when i do tracert i get my external ip.

my Lan is like this

Main PC is connected to the router.

Everything else is connected wireless with WPA (1 Laptop and 1 PSP)

i see no point in calling the ISP as the other computers on the LAN can access thsoe sites.

[lordsmurf]

Your network card may also be dying.

[dudesmn]

Ive been tried the winsock and just tried it again and no luck

[ybeard]

I don't understand why people suggest calling the ISP. He's said he has other computers on his LAN that are capable of accessing the sites he isn't getting to from this one particular computer. If he shuts off one of the working computers and assigns the IP it has to the one in question, one would think he could eliminate the router as a potential cause.

Despite the fact that you say you've used the host file from another computer, it still sounds like you've got a problem with it. Worse thing you could do is if you have a spare drive laying around, install it as your boot drive, format and reinstall Windows. At a bare minimum, with a clean and fresh Windows install on a virgin drive, you'd eliminate any software problems, ie virus, spyware, firewall, etc.

Just a thought. Are the other computers on your LAN like systems? In other words, if they're all Dell Optiplex GX270's for example, you could just swap the hard drives between the two and accomplish the same thing.

Sounds like the problem is software related inside of your computer.

[jimmalenko]

actually when i do tracert i get my external ip.

That seems weird to me. Do you have an internal IP address range ?

my Lan is like this

Main PC is connected to the router.

Everything else is connected wireless with WPA (1 Laptop and 1 PSP)

So everything connected wirelessly to your router works, yet the one connected by cable doesn't ?

Tried replacing the cable ?

Tried plugging into a different port on your router (I assume it is also a 4 port switch) ?

i see no point in calling the ISP as the other computers on the LAN can access thsoe sites.

The whole point would be to prove undeniably that the problem is at your end (which I believe it is). The quickest way to resolving the issue is narrowing down the cause.

[dudesmn]

Do you have an internal IP address range ?

192.168.0.2 - 192.168.0.255 i believe

[jimmalenko]

Do you have an internal IP address range ?

192.168.0.2 - 192.168.0.255 i believe

OK. So that is to say for example your router is 192.168.0.1, and then the 3 PCs are 192.168.0.xxx (which is the same way I have mine set up FWIW). When I tracert anything I get 192.168.0.1 as the first hop.

[dudesmn]

if i were to tracert in my network i get this.

Tracing route to 192.168.0.4 over a maximum of 30 hops

  1    34 ms     3 ms     5 ms  192.168.0.4

Trace complete.

[stiltman]

what happens if you bypass the home router altogether?
As in you connect striaght to the modem.
Unplug the power to the modem for about 30sec
Reboot you PC
You are DHCP right? do an "ipconfig/all" to make sure you have the new IP
do a "tracert www.google.com"

[jimmalenko]

if i were to tracert in my network i get this.

Tracing route to 192.168.0.4 over a maximum of 30 hops

  1    34 ms     3 ms     5 ms  192.168.0.4

Trace complete.

Hang on a minute ....



Earlier you said this:

actually when i do tracert i get my external ip.

192.168.0.4 is not your external IP address.




Anyhoo, stiltman has a good idea there.

[Dv8ted2]

Just a wild guess, but is the content advisor turned on? If so, disable it and see if you can get to the site. Sometimes, this can happen.

Do any other sites work, or are you getting that message for all sites?

[dudesmn]

if i were to tracert in my network i get this.

Tracing route to 192.168.0.4 over a maximum of 30 hops

  1    34 ms     3 ms     5 ms  192.168.0.4

Trace complete.

Hang on a minute ....



Earlier you said this:

actually when i do tracert i get my external ip.

192.168.0.4 is not your external IP address.




Anyhoo, stiltman has a good idea there.

If i ping something within the network i get my internal address.

I ping something out of the network i get external.

I tried removing the router from the equation and i still get nothing, but i do get a new ip.

[vhs?]

I had an intermittent problem like this and the local agents blamed everyone but them.
It turned out to be servers that wouldn't talk to each other sometimes.
Drove me nuts.

[dudesmn]

Did i forget to mention that cannot view the pages through googles cache?

[Nelson37]

Do an IPCONFIG /all and list the results. Report particularly the listed gateway address, and DNS. Do the same on one of the wireless, working machines. Report particularly any listed differences.

Ping yourself, the router, and your DNS server. Report particularly the DNS server results. Also ping 63.75.167.11.

Can you access the Internet on occassion, just certain sites, what?

It is almost certainly NOT your ISP. If you can reliably ping a DNS server, your connection is mechanically correct.

What changes occurred to the PC immediately before the problem began to happen? Upgrade to IE7, by any chance?

You have now made enough changes to possibly mask the original problem. After the ping tests, next step would be to hardwire one of the working PC's to the router and disable it's wireless connection, and test.

Before changing anything, first do non-destructive comparison tests to isolate the problem.

[racingintherain]

This may sound crazy, but I had a similar problem a month ago. Date on my computer was set incorrectly. Once corrected, all the sites that would not load were magically fixed. I assume it was some incompatibility created by data in the cookie for these sites that caused the problem.

Probably not your issue, but thought I'd throw it our there since you are still struggling with this.

Rain Racer

[Nelson37]

People are vastly over-complicating the situation.

Ping tests do not return addresses. Tracert does this. You should NOT be getting Destination Host Unreachable. This indicates a failure of basic connection.

Repeat - Ping yourself, router, DNS servers. Do each several times. If you do not know your DNS server, or it is listed as the same as the router (Gateway), ping 63.75.167.11. If at any time your get Timed Out or Unreachable there is a basic problem to solve.

Posting the results of the IPCONFIG/all command, in addition to the results of the ping tests, will almost certainly determine the problem. Tracert is not really all that useful, once the problem is outside your network it is essentially outside your control.

Ping, ipconfig, and a working unit on the same network is ALL you need to solve this problem.

You have also not answered the essential question determining whether the problem PC is ALWAYS able to access some sites and NEVER able to access particular sites, or whether this PC simply fails intermittently, or all the time, and the sites seemingly in question are simply the ones most commonly accessed on this unit.

Good, valid, no-spyware and rairly down sites to test access are www.google.com, www.nfl.com, and www.videohelp.com.

Something as simple as incorrect gateway or DNS could easily be your problem, and is quite common. Nothing yet posted is useful to eliminate the most common issues with your connection type. This info is listed in the ipconfig results, which someone else as well as I have requested.

This is the starting point. Evaluating this info should have been the very first step.

[stiltman]

People are vastly over-complicating the situation.

Nothing yet posted is useful to eliminate the most common issues with your connection type.

One reason I gave up...you can't troubleshoot a problem without seeing the data

[dudesmn]

Self:

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Router

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time=37ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 37ms, Average = 10ms

63.75.167.11:

Pinging 63.75.167.11 with 32 bytes of data:

Reply from 63.75.167.11: bytes=32 time=78ms TTL=109
Reply from 63.75.167.11: bytes=32 time=56ms TTL=109
Reply from 63.75.167.11: bytes=32 time=56ms TTL=109
Reply from 63.75.167.11: bytes=32 time=56ms TTL=109

Ping statistics for 63.75.167.11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 78ms, Average = 61ms

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Control
ler
        Physical Address. . . . . . . . . : *edited out*
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.2
        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, April 21, 2007 3:04:13 PM
        Lease Expires . . . . . . . . . . : Sunday, April 22, 2007 3:04:13 PM

Also when i ping my external IP i get timed out.

I used to be able to access those sites, but cant anymore. I just tried NFL.com and its not accessable.

[stiltman]

So show the same stuff with the router removed.

Also tracert results will help

[Nelson37]

Where did you get the 127.0.0.1 address from??? Was this indicated somewhere, if so by what and how? That number should NOT be coming up.

It WOULD come up with certain types of security software, or an edited HOSTS file, or probably a couple other oddball possibilities. That is a null address for the local PC. When I want to block a site, I redirect it to that address. Pinging this checks TCP/IP but not the hardware.

Where and how this number was indicated could be the key to the problem.

You should be pinging the 192.168.0.2. That is YOUR PC address, internal to the net. Since the other pings worked, this should be ok but test it and report.

Your PC's DNS is directed to the router. Enter in DNS addresses directly to the PC, so as not to depend on the router for this info. Same with DHCP. Static the addresses. Just one more failure possibility that can be easily eliminated. I thought this was mentioned earlier as having already been done.

DHCP and DNS are worse than useless on a small network, you are depending on simple electronics to supply four different essential numbers that never change. The number of times the router will screw this up is orders of magnitude higher than the possibility of the numbers disappearing from your PC.

For instance, if the DNS is static on the wireless machines, and the router has lost that information, that would result in the symptoms you are seeing. Check the wireless PC's Network Connections for DNS settings. This change may be all you need.

Do a "ping www.nfl.com". If you get numbers for the address, then DNS is OK. If not, there is the problem.

Next step is to turn off all PC's. Take a wireless PC, disable the WiFi, connect it to the router with the SAME CABLE as the existing PC. Test. If the PC does NOT work, the problem is Isolated to the Wired connection, including the cable, on the Router. If the PC does work, the problem is isolated to the original PC.

You are physically connected to the Internet and are able to access it. Problem is narrowing down to either DNS or some problem with the Hosts file, or some firewall or security software.

[stiltman]

Where did you get the 127.0.0.1 address from??? Was this indicated somewhere, if so by what and how? That number should NOT be coming up.

127.0.0.1 is called loopback

You use it to test your TCP/IP stack.
If you can't ping it, you got worse problems

[dudesmn]

i pinged 127.0.0.1 myself because you did say to ping myself.

Pinging www.nfl.com [64.30.236.35] with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 64.30.236.35:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Ill try pinging without the router later on when its not in use.

Pinging 192.168.0.2 with 32 bytes of data:

Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128
Reply from 192.168.0.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

[jimmalenko]

Do you think it might be time to just reinstall windows and be done with it ?

[dudesmn]

true.

I need to back a few things up.

Do you guys reccomend an internal Hard drive or external?

[stiltman]

WTF????

I think you're F***ing with us.

Last post is pinging yourself 192.168.0.2 (the gateway is .1)
and to www.nfl.com

Do you want help?

you need to re-read my posts

In any event, I'm staying out of this thread

[Nelson37]

For crying out loud, I know damn well what loopback is. Completely worthless, once a ping has been returned from anywhere. That number should not come up anywhere. My question is where did the OP get that number? Most folks do not know it, and it should not show up anywhere.

To the OP, pinging this is not the same as pinging yourself. The loopback tests TCP/IP only, using your IP address also tests the card and drivers for functionality.

The ping to NFL resolved the address, indicating functioning DNS, yet gives Destination Host Unreachable, which near as I can tell he gets on anything outside his own net, on this one machine.

I have been starting to wonder if this guy lives under a bridge.

With the way info is dribbling out, this just seems rather odd.

Compare the working PC's settings with the one that does NOT work. Test a working PC on the same connection as the one that does NOT work. This is quite simple. This will completely eliminate all hardware, software, and equipment OUTSIDE the suspect PC.

If you want to follow proper diagnostic procedure, I will help you. If you wish to continue to stumble around in the dark, I got better things to do.