Cannot browse website

[SONYFX]

I've got this weired problem:

My Internet connection is on, I can use msn messenger, listen to Internet radio without problem. But I can't browse any website using IE or Firefox, it always timeout, does anyone know why?

 

[Markbnj]

This probably should be in the Networking forum, anyway...

Could be a DNS issue. If you have a DNS problem you can't resolve names, however messenger and the radio streams might be connecting by IP, and so they wouldn't have a problem.

You can test this by opening a command prompt (C:\> prompt).

First, type ipconfig /all

Toward the bottom you'll see "DNS Servers." If you are connected to a router/firewall that will show as the address of the router (something like 192.168.0.1). If you aren't connected to a router it should show an external IP or domain name. If it is blank that's a problem.

Now choose a website, anything, like www.anandtech.com. Type:

nslookup www.anandtech.com

You should see at the bottom:

Non-authoritative answer:
Name: www.anandtech.com
Address: 208.65.201.105

If you see any valid address then DNS isn't the problem. If you get any error such as "non-existent domain" or "can't find server address for dns.myisp.com" then DNS might be the problem.

If you get a DNS error then report back with more about your network, whether you have a router, what ISP, wireless or wired, that kind of thing. Detail is your friend .

 

[SONYFX]

Thanks, I tried ipconfig and it shows my DNS server as "192.168.2.1". When I use nslookup it shows:

=======================
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.2.1: Timed out
*** Default servers are not available
Server: UnKnown
Address: 192.168.2.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
========================

I use DSL line that is wired, the DSL modem is provided by ISP. This only happened two days ago, I tried resetting the modem to factory setting but it doesn't seem to work.

 

[SONYFX]

update: I called my ISP and they ssaid there's nothing wrong connection wise, he tried some command to fix the registry but it still doesn't work, any ideas?

 

[Diz2K2]

Are you using a router?

 

[Markbnj]

Thanks, I tried ipconfig and it shows my DNS server as "192.168.2.1". When I use nslookup it shows:

Ok, so you do have a DNS problem, and I think your results show that you are using a router/firewall. I base that on the 192.168.2.1 address of the DNS server. But I'm guessing, and you really need to post your complete network setup before we'll be able to help definitively.

Here is a basic diagram of the two setups you're likely to have:

wall <-what the cable comes out of
cable/DSL modem <- what the wall cable goes in to
PC <- connected to the modem by ethernet

In this case your PC requests a configuration directly from the ISP, which will tell it what IP address it should use, what name servers it should query, etc. This happens at startup and at various other times.

wall <-what the cable comes out of
cable/DSL modem <- what the wall cable goes in to
router/firewall <- connected to the modem by ethernet
PC <- connected to the router by ethernet or wireless

In this case the router is the client to your ISP. When it starts up it requests the configuration and sets itself up. It then acts a contact point when your PC starts up, and provides the PC with its configuration.

Standard troubleshooting:

- Turn off all devices including computer. Now power up devices from the wall out, and let each do its self-test and settle down before powering up the next.

- Type ipconfig /release on your system, then follow with ipconfig /renew. If the renew fails you have a problem with either your router or ISP failing to provide the configuration parameters on request.

- If you have a router you can do the same thing from the administration pages, i.e. you can force it to release/renew, and you can see what parameters it is currently working with (what IP the ISP has assigned to it, and what name servers it thinks it should talk to).

Post some more info.

 

[nweaver]

change DNS on your connection to a root server (4.2.2.1) and then try it. If it works, log into your router and call up your ISP for updated DNS

 

[Markbnj]

Yeah, but the problem might be in the router, not at the ISP. He still hasn't confirmed whether he has one (I suspect he does). So changing to a root DNS server on his desktop (overriding the DHCP) settings might work, but might not indicate that the ISP is the issue.