ICQ/Email but not Browsing?

[Rhombuss]

I'm currently on Rogers Cable Internet in Toronto. It's a really inconsistent service, but the weird thing is that sometimes when I cannot browse (ie. view websites), my ICQ/MSN/email programs always work still. I'm using a router, but I don't see how that could case this problem.

Are there any known general problems that could cause this?

 

[fs5]

possible DNS server resolution problem. make sure your have working DNS servers.

When you experience this problem again in the command prompt type "ipconfig /all"
there should be a primary and secondar DNS server ip. then type "ping xxx.xxx.xxx.xxx" where xxx is the primary / secondary dns servers. If there is a response then it's something else.

 

[Rhombuss]

Hmm...it seems to have gotten worse the past few hours. The DNS listed for this computer is 192.168.0.1, because the router is set at that address. Of course, the WAN actually has the DNS assigned by my ISP. And it pings fine to 192.168.0.1.

Any other ideas?

 

[Fuzznuts]

Originally posted by: fivespeed5
possible DNS server resolution problem. make sure your have working DNS servers.

When you experience this problem again in the command prompt type "ipconfig /all"
there should be a primary and secondar DNS server ip. then type "ping xxx.xxx.xxx.xxx" where xxx is the primary / secondary dns servers. If there is a response then it's something else.

ping the server is by no means a test to see if dns on that ip is working. a better test would to to perform an nslookup or a dig useig the dns servers ip. it may respond to ping even though the dns daemon is dead.

 

[Rhombuss]

Hmm...it's still on and off, but sometimes I can access some sites but not others. Fuzznuts, could you go into more detail about checking the DNS addresses?

 

[fs5]

Originally posted by: Fuzznuts

Originally posted by: fivespeed5
possible DNS server resolution problem. make sure your have working DNS servers.

When you experience this problem again in the command prompt type "ipconfig /all"
there should be a primary and secondar DNS server ip. then type "ping xxx.xxx.xxx.xxx" where xxx is the primary / secondary dns servers. If there is a response then it's something else.

ping the server is by no means a test to see if dns on that ip is working. a better test would to to perform an nslookup or a dig useig the dns servers ip. it may respond to ping even though the dns daemon is dead.

it's a first step into seeing if your DNS are configured properly. Rhombuss, look in your router settings for the DNSes. 192.168.0.1 is your router and it is relaying dns requests to the ones in the router.

 

[Fuzznuts]

Originally posted by: fivespeed5

Originally posted by: Fuzznuts

Originally posted by: fivespeed5
possible DNS server resolution problem. make sure your have working DNS servers.

When you experience this problem again in the command prompt type "ipconfig /all"
there should be a primary and secondar DNS server ip. then type "ping xxx.xxx.xxx.xxx" where xxx is the primary / secondary dns servers. If there is a response then it's something else.

ping the server is by no means a test to see if dns on that ip is working. a better test would to to perform an nslookup or a dig useig the dns servers ip. it may respond to ping even though the dns daemon is dead.

it's a first step into seeing if your DNS are configured properly. Rhombuss, look in your router settings for the DNSes. 192.168.0.1 is your router and it is relaying dns requests to the ones in the router.

its a wrong step. a failed lookup against the servers will give you both answers in one go. what if his server responded to pings you woul dhave said well aint the dns server cos its up.

 

[fs5]

Originally posted by: Fuzznuts

Originally posted by: fivespeed5

Originally posted by: Fuzznuts

Originally posted by: fivespeed5
possible DNS server resolution problem. make sure your have working DNS servers.

When you experience this problem again in the command prompt type "ipconfig /all"
there should be a primary and secondar DNS server ip. then type "ping xxx.xxx.xxx.xxx" where xxx is the primary / secondary dns servers. If there is a response then it's something else.

ping the server is by no means a test to see if dns on that ip is working. a better test would to to perform an nslookup or a dig useig the dns servers ip. it may respond to ping even though the dns daemon is dead.

it's a first step into seeing if your DNS are configured properly. Rhombuss, look in your router settings for the DNSes. 192.168.0.1 is your router and it is relaying dns requests to the ones in the router.

its a wrong step. a failed lookup against the servers will give you both answers in one go. what if his server responded to pings you woul dhave said well aint the dns server cos its up.

alright lets skip the ping step then and explain to him how to do an nslookup. He did ask you didn't he? Oh wait you were too busy trying to prove me wrong so here Rhombuss:

http://www.kloth.net/services/nslookup.php
go there and enter a domain name like yahoo.com and change the "server" to the IPs of your DNSes.

 

[Fuzznuts]

Originally posted by: fivespeed5

Originally posted by: Fuzznuts

Originally posted by: fivespeed5

Originally posted by: Fuzznuts

Originally posted by: fivespeed5
possible DNS server resolution problem. make sure your have working DNS servers.

When you experience this problem again in the command prompt type "ipconfig /all"
there should be a primary and secondar DNS server ip. then type "ping xxx.xxx.xxx.xxx" where xxx is the primary / secondary dns servers. If there is a response then it's something else.

ping the server is by no means a test to see if dns on that ip is working. a better test would to to perform an nslookup or a dig useig the dns servers ip. it may respond to ping even though the dns daemon is dead.

it's a first step into seeing if your DNS are configured properly. Rhombuss, look in your router settings for the DNSes. 192.168.0.1 is your router and it is relaying dns requests to the ones in the router.

its a wrong step. a failed lookup against the servers will give you both answers in one go. what if his server responded to pings you woul dhave said well aint the dns server cos its up.

alright lets skip the ping step then and explain to him how to do an nslookup. He did ask you didn't he? Oh wait you were too busy trying to prove me wrong so here Rhombuss:

http://www.kloth.net/services/nslookup.php
go there and enter a domain name like yahoo.com and change the "server" to the IPs of your DNSes.

sorry but christmas aint been good commericalised stress loaded time of hell. DFS on Boxing looking at couches I ask what the hell is the world coming too.

The savior of mankind was born and we celebrate by trying to find the cheapest leather couches that match our new laminate floor, and it has to be today " cos its in sale and its a bargain"

/rant mode off