This is a response to the close thread (thread1355-1391062) titled "Unable to browse, but able to PING".
The user appears to be having problems with his DNS server(s). He should have tested if they are working by using the "nslookup" utility at the Command Prompt e.g.
nslookup <some-domain-name> <dns-server>
Of course he could see the DNS servers associated with his network adapter by typing "ipconfig /all" at the Command Prompt.
Assumbly his connection to IM services remains active because his network connection is not disrupted. However any IM service that requires a domain name to be resolved for registration / reconnection purposes would not work after he signed out, unless the domain name exists in his local or malfunction DNS server's cache.
Similarly, for the sites he is pinging there are probably cached records, he should try to ping a site he hasn't visited before. Also he could try visiting a web-site by using the IP address in the URL e.g. instead of try going to
There are two DNS servers with easy to remember IP's 4.2.2.2 and 4.2.2.1 which the nslookup can be performed against in order to verify if his network adapter DNS servers are problematic while others DNS servers are fine. E.g.
C:\>nslookup internetworking.engineering.dal.ca 4.2.2.1
Server: vnsc-pri.sys.gtei.net
Address: 4.2.2.1
Non-authoritative answer:
Name: kil-ws-2.UCIS.dal.ca
Address: 129.173.1.241
Aliases: internetworking.engineering.dal.ca
C:\>nslookup internetworking.engineering.dal.ca 4.2.2.2
Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
Non-authoritative answer:
Name: kil-ws-2.UCIS.dal.ca
Address: 129.173.1.241
Aliases: internetworking.engineering.dal.ca
If the problem was indeed as outlined, then the DNS servers on the network adapter need to be changed to some that work better. Also he should have a primary and a secondary DNS server at least (that are different machines).
The user appears to be having problems with his DNS server(s). He should have tested if they are working by using the "nslookup" utility at the Command Prompt e.g.
nslookup <some-domain-name> <dns-server>
Of course he could see the DNS servers associated with his network adapter by typing "ipconfig /all" at the Command Prompt.
Assumbly his connection to IM services remains active because his network connection is not disrupted. However any IM service that requires a domain name to be resolved for registration / reconnection purposes would not work after he signed out, unless the domain name exists in his local or malfunction DNS server's cache.
Similarly, for the sites he is pinging there are probably cached records, he should try to ping a site he hasn't visited before. Also he could try visiting a web-site by using the IP address in the URL e.g. instead of try going to
There are two DNS servers with easy to remember IP's 4.2.2.2 and 4.2.2.1 which the nslookup can be performed against in order to verify if his network adapter DNS servers are problematic while others DNS servers are fine. E.g.
C:\>nslookup internetworking.engineering.dal.ca 4.2.2.1
Server: vnsc-pri.sys.gtei.net
Address: 4.2.2.1
Non-authoritative answer:
Name: kil-ws-2.UCIS.dal.ca
Address: 129.173.1.241
Aliases: internetworking.engineering.dal.ca
C:\>nslookup internetworking.engineering.dal.ca 4.2.2.2
Server: vnsc-bak.sys.gtei.net
Address: 4.2.2.2
Non-authoritative answer:
Name: kil-ws-2.UCIS.dal.ca
Address: 129.173.1.241
Aliases: internetworking.engineering.dal.ca
If the problem was indeed as outlined, then the DNS servers on the network adapter need to be changed to some that work better. Also he should have a primary and a secondary DNS server at least (that are different machines).