Website access only using IP Address

November 8, 2010 at 17:21:08
Specs: Windows XP, 3.199 GHz / 1526 MB
I have been going round and round, but still not able to solve this problem. Have a small workgroup of Windows computers and all have access to the Internet through the broadband modem gateway. Been working fine, but now a single Windows XP computer can no longer access web sites (computing.net, google.com, etc). The only way to access a web page using the PC is via the IP address (eg. http://74.125.45.99/ for google.com). If I try to ping a domain name it responds unable to locate. This PC is also able to access other computers on the Network fine.

Here is a list of some things I have tried, but still not working:
-reboot
-reinstall network card driver and networking components
-reset TCP/IP (netsh int ip reset c:\resetlog.txt)
-ipconfig/flushdns
-changed DNS servers from ISP to Google's and back
-tried multiple browsers
-disabled Windows firewall
-uninstalled antivirus
-lspfix (no problem found)
-nslookup will identify site's IP which can then access via IP

Any idea how to fix?


See More: Website access only using IP Address

Report •


#1
November 8, 2010 at 18:25:25
Control Panel
Internet Options
Connections
Lan Settings

> only Autodetect Settings should be checked....


Report •

#2
November 8, 2010 at 18:39:44
The workstation is pointed at an invalid dns server or can't contact the dns server.

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#3
November 9, 2010 at 03:25:57
X86:
Yes, have tried with nothing checked and only "Automatically detect settings" checked in Local Area Network (LAN) Settings of Internet Options.

wanderer:
As I stated - I changed the DNS servers from my ISP (as on other computers) to Google's DNS, but that did not solve the problem. But, nslookup is able to determine IP when I enter domain name - so DNS seems to be working and correct? I agree the problem seems like something to do with DNS, but DNS seems to be working properly, except for the obvious - can only open via IP and not via domain name.

I have been having this problem for about 1 week. Any other suggestions?


Report •

Related Solutions

#4
November 9, 2010 at 05:49:33
Try to use other web browser (Mozilla firefox, Google Chrome, Opera, etc), see whether the problem persists.

If everything is configured correctly and the DNS is pointing to Google's DNS, you might try to reset Winsock catalog and see how it goes.

Hope this helps.


Report •

#5
November 9, 2010 at 06:31:28
post the results of an ipconfig /all for review

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#6
November 9, 2010 at 08:16:14
picohat:
As indicated in my initial post, I have tried multiple browsers (IE, Firefox, Chrome) - none load page by domain, only by IP.

I tried to reset Winsock catalog using WinSock XP Fix 1.2 and rebooted, but that did not resolve the problem.

wanderer:
Here are the results of "ipconfig /all" (with static IP)
Have the problem with Static or using DHCP.

Windows IP Configuration

        Host Name . . . . . . . . . . . . : BDESK
        Primary Dns Suffix  . . . . . . . : 
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : 
        Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
        Physical Address. . . . . . . . . : 00-13-C4-D3-1C-B2
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.142
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.254
        DNS Servers . . . . . . . . . . . : 205.152.144.23
                                            205.152.132.23

Here are the results of "ping yahoo.com"

Ping request could not find host yahoo.com. Please check the name and try again.

Here are the results of "ping 209.191.122.70" (IP of yahoo.com)

Pinging 209.191.122.70 with 32 bytes of data:

Reply from 209.191.122.70: bytes=32 time=47ms TTL=47
Reply from 209.191.122.70: bytes=32 time=47ms TTL=47
Reply from 209.191.122.70: bytes=32 time=47ms TTL=47
Reply from 209.191.122.70: bytes=32 time=47ms TTL=47

Ping statistics for 209.191.122.70:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 47ms, Average = 47ms

Any other suggestions?


Report •

#7
November 9, 2010 at 09:04:24
those appear to be valid southbell dns servers. Post the results of a tracert to one of them.

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#8
November 9, 2010 at 15:47:06
wanderer:

Yes, 205.152.144.23 is a Bellsouth DNS - here are the results of "tracert 205.152.144.23":

Tracing route to 205.152.144.23 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254 
  2    11 ms     *        7 ms  65.14.252.30 
  3     8 ms     8 ms     8 ms  65.14.254.29 
  4     8 ms     8 ms     7 ms  205.152.145.166 
  5     8 ms    10 ms     8 ms  205.152.144.23 

Trace complete.

And, here are the results of "tracert 69.147.125.65" (Yahoo's IP):

Tracing route to 69.147.125.65 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.254 
  2     7 ms     *        8 ms  65.14.252.30 
  3     8 ms     8 ms     8 ms  65.14.126.49 
  4    11 ms     9 ms     9 ms  12.81.8.22 
  5     9 ms     8 ms     9 ms  12.81.8.11 
  6    10 ms     8 ms     9 ms  74.175.192.166 
  7     9 ms    10 ms     9 ms  12.122.106.94 
  8    13 ms     9 ms     9 ms  12.122.81.25 
  9    16 ms    16 ms    19 ms  192.205.36.254 
 10    30 ms    36 ms    35 ms  4.69.138.126 
 11    32 ms    36 ms    35 ms  4.69.140.142 
 12    30 ms    35 ms    36 ms  4.69.138.20 
 13    47 ms    47 ms    51 ms  4.69.132.86 
 14    56 ms    53 ms    54 ms  4.69.134.134 
 15    98 ms    51 ms    50 ms  4.68.17.67 
 16    49 ms    47 ms    48 ms  4.79.228.2 
 17    52 ms    71 ms    48 ms  216.115.108.57 
 18    48 ms    48 ms    51 ms  66.196.112.203 
 19    49 ms    69 ms    50 ms  69.147.125.65 

Trace complete.

Thanks for your help, any other ideas?


Report •

#9
November 9, 2010 at 15:52:48
looks great but not providing any clues.

How about a nslookup yahoo.com? Post that please.

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#10
November 9, 2010 at 19:52:53
wanderer:
Here are the results of "nslookup yahoo.com":
Server:  dns.mia.bellsouth.net
Address:  205.152.144.23

Non-authoritative answer:
Name:    yahoo.com
Addresses:  69.147.125.65, 72.30.2.43, 98.137.149.56, 209.191.122.70
          67.195.160.76

Next suggestion?


Report •

#11
November 10, 2010 at 06:04:31
In command prompt, try to connect to yahoo web server by using this command, see whether it works. If it works, your will see a blank screen and you can terminate the connection by pressing ctl+C.

telnet yahoo.com 80

Advise you to scan the computer again by using antivirus/anti-malware program with latest signature, need to ensure it's not caused by virus/worm...


Report •

#12
November 10, 2010 at 08:06:13
Go to Shields UP! and do a port scan of udp port 53. Is it open?

Go to windows\system32\drivers\etc and rename your hosts file to hosts.old. Reboot and ping yahoo by name. Lets see if there is a different result

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#13
November 10, 2010 at 13:10:05
picohat:
As expected, here are the results of the command "telnet yahoo.com 80":
Connecting To yahoo.com...Could not open connection to the host, on port 80: Con
nect failed

If I issue the command to the Yahoo IP address instead, it works properly.

C:\>telnet 72.30.2.43 80 flashes connect messge blank Ctrl-C displays following

<HEAD><TITLE>Invalid HTTP Request</TITLE></HEAD>
                                                <BODY BGCOLOR="white" FGCOLOR="b
lack">
      <FONT FACE="Helvetica,Arial"><B>
                                       Bad request syntax</B></FONT>

                                                                    <!-- default
 "Invalid HTTP Request" response (400) -->
                                          </BODY>


Connection to host lost.

C:\>

Also as expected - I ran another malware scan which found nothing.

wanderer:
Not able to run a "Shields UP!" scan because can't get to the grc.com site - site will not load completely using the IP address of grc.com.

Already looked at the hosts file, which was still the Windows original with no modifications.


Report •

#14
November 10, 2010 at 13:11:19
SOLVED THE PROBLEM - "case closed"

Thank you everyone for all your suggestions, but just was not able to locate the problem.

Also tried a Windows "System Restore", but Windows was not able to restore.

So had to re-install Windows from scratch.


Report •

#15
November 10, 2010 at 13:36:26
When all else fails reload :-) Sure was a puzzle. Thanks for posting with your soluiton.

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •


Ask Question