Strange problem...cant open any site!

Hi all!

I have a very strange problem....
I have to computers connected on internet via router. First computer works fine , but on the other computer i cant open any site...

Everything works well, i can ping (example www.google.com), i can tracert google.com, but i cant open it neither with FF or IE.


I dont have any firewall installed (except XP firewall), it is a fresh installed system so there is no spyware.
When i connect adsl modem directly to my computer then everything works.

Any one knows were is the problem?

Speedy

 

I just gotta try.

I write this from the 2nd machine while the other is still on

BB

 

I had the same problem at times when I first started out with the Router. After a bit( lot ) of frustration I decided to have a go at shutting down all but the machine I was trying to connect and connected them one at a time. I wound up with 3 machine 100% independent of the others.

Is it possible that SHARING got mixed into things ? With the Router there is no need for sharing anything other than the Modem which is after the Router


BillyBob

 

Hi BillyBob

The first machine is shut down, but no change

 

If this was one PC, I'd be tempted to look at local settings - but as this is affecting more than one PC, I think it must be something on the network. The most obvious culprit would be the router.

OK, if you can tracert to a named internet site, DNS and IP routing are working. This must be something specific to http transfer. I think the most likely issue is that port 80 is being blocked. Try the following at the command prompt:

telnet www.google.com 80

This will open a telnet session on port 80. If it works you will get a blank screen and hitting keys will just result in the cursor moving. I know this sounds strange, but if that is what you get then the test has worked. If on the other hand you get a message along the lines of "Could not open connection to the host, on port 80: Connection failed" we have narrowed down the problem to a block on port 80.

While we are testing ports, can you access this site:

https://www.dellbatteryprogram.com/Default.aspx

As it is https, it should be accessed through port 443. If you can then we know the problem is restricted to port 80.

If this is a port 80 problem, I think you have to be looking at a router issue. I'd check through your NAT settings and make sure you haven't misconfigured a port forwarding set up for port 80 (http). Also have a look for any firewall settings and double check those.

 

Hi ReggieB.

It is one PC, like i said in the first post the first PC can access to every site, and everything works fine.

Ok, this is working.

I cant access neither on that site.

 

The obvious thing to suggest is a virus or spyware, but then why aren't you getting the problem when you connect directly to the modem

Try installing Opera and see if that works? It's a long shot but got to be worth a try.

Otherwise lets look at where we are. If it was a firewall, routing or DNS issue, telnet to port 80 using the site name wouldn't work. So what is different between the telnet session and a browser connection? It can't be the browser itself as the problem effect both IE and Firefox.

OK - How about packet size. Down loading a web site involves downloading images. Even small images are going to be larger than ping packets and telnet communication. If you have a problem downloading larger files, that would account for the symptoms you describe. That indicates a problem with the network card.

Now there are two aspects to packet size. It could just be a problem with the size of individual packet size. You can test that with:

ping www.google.com -l 1000

-l is minus L and sets the length of the ping packet (in this case 1000 bytes). The maximum is 65500 bytes, but my system was failing to get responses to packets larger than 1000 bytes. However, I could get up to 30000 bytes pinging www.bbc.co.uk so it might be worth trying a few sites (I'm UK based so probably get a better response from a BBC site than people in other parts of the world).

It might be worth trying these tests on your two PCs and seeing if there is much difference between the maximum ping packet size you get.

The other problem with larger files is that they have to be broken down into a number of smaller packets and then reassembled at the receiving PC. It could be this reassembly that is failing.

If it looks like packet size is the problem, you could try updating you network card drivers. However, it could be a hardware fault - in which case you'll have to get a new network card.

 

Generally it is something very simple.....have you checked your logon id and password are set correctly on the non connecting machine?

 

Hi ReggieB

I try all of this, and it really was a network card probrem (i even try in linux, and there works fine ).
I bought a new network card and now everything works well.

Thanks for help.

Speedy