• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 294
  • Last Modified:

Firefox and IE can't resolve host names

Odd problem this morning.  My Windows XP SP2 computer suddenly can't connect to websites using the url.  If I type in the IP address, it works, so "www.google.com" gives me an error, but "64.233.161.104" works fine.  The error is simply "Firefox can't find the server at www.google.com."

This happens in both IE and Firefox.  Outlook can still connect to my 3 email accounts and get my mail.  FeedDemon RSS reader can still collect all my RSS feeds.  I'm on a local network, and all the other computers are fine (which is where I'm posting this from).

I've "repaired" my network connection, flushed the DNS, and changed the DNS servers to the OpenDNS servers (also tried auto-detect, and my ISP's DNS servers)  I've disabled the Kaspersky firewall.  Nothing seems to work!

Any ideas for something else I can try?

0
cinepro
Asked:
cinepro
1 Solution
 
scottdorseyCommented:
First guess would be spyware/virus. Can you ping a domain name by dns? Check your 'hosts' file, download hijack this and analyze the log file at www.hijackthis.de to see if anything nasty is lurking. I presume you have anti-virus installed? www.free.grisoft.com if not.
0
 
omarfaridCommented:
Hi,

If on those m/cs you run from the command line

nslookup

server dnsipaddress

www.cnn.com (or the domain you have problem with)

Do you get the response back or it just give error message / or just time out

If it resolves then there is no problem with the dns server or the communication to it.

If you see errors / time out then your dns servers for some reason are responding or not reachable
0
 
cineproAuthor Commented:
Here's how it went:

-----------------------------------------------------------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\jburk>nslookup
Default Server:  resolver1.opendns.com
Address:  208.67.222.222

www.google.com
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    google.navigation.opendns.com
Addresses:  208.67.216.230, 208.67.216.231
Aliases:  www.google.com

>
---------------------------------------------------------------------------
0
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

 
cineproAuthor Commented:
Additional Note:

Ran "HiJackThis", didn't find anything unwanted.  Ran "spybot s&d", only found tracking cookies (deleted them).

Still no joy.
0
 
cineproAuthor Commented:
Additional additional note:

Just installed "Opera".  It works fine.  Still no Firefox or IE.
0
 
omarfaridCommented:
So, as you can see there is no problem in resolving domain names and the dns server is ok.

Ok, try

C:\> telnet www.google.com  80
GET http://www.google.com


The command above will connect you to www.google.com on port 80

If you see that the session is trying and then disconnecting, then you could be having problem going out.

If you could manage to type the second line and get some response (the index.html) then you have no problem to connect to the web site.
0
 
cineproAuthor Commented:
Can't telnet to www.google.com.  It just says "connection lost"
0
 
omarfaridCommented:
Did you telnet to port 80?

If yes, then there could be a firewall some where interrupting your connection.

0
 
cineproAuthor Commented:
It looks like I can ping www.google.com.  But it still won't load in IE or Firefox (but Opera is fine)


-------------------------------------------------------------------------------------
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


C:\Documents and Settings\jburk>ping www.google.com:80

Pinging www.google.com:80 [208.67.219.137] with 32 bytes of data:

Reply from 208.67.219.137: bytes=32 time=41ms TTL=241
Reply from 208.67.219.137: bytes=32 time=42ms TTL=241
Reply from 208.67.219.137: bytes=32 time=94ms TTL=241
Reply from 208.67.219.137: bytes=32 time=28ms TTL=241

Ping statistics for 208.67.219.137:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 28ms, Maximum = 94ms, Average = 51ms
-------------------------------------------------------------------------------------
0
 
cineproAuthor Commented:
It turns out the problem was the firewall on my Kaspersky software.  It had been disabled, but was still blocking Firefox after Firefox automatically updated last night.

Followed the directions here:

http://support.mozilla.com/kb/Configuring+Kaspersky+Internet+Security

Now it works. :)
0
 
Computer101Commented:
PAQed with points refunded (125)

Computer101
EE Admin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now