Hello all,
I'm hoping you can help me with this problem that has completely stymied me...
A friend of mine has a PC (AMD Athlon 1.86GHz, 512 MB RAM, "modern", WinXP Pro Version 2002 SP 1); for Web browsing, he uses Internet Explorer 6 as well as another Web browser called Avant. He connects to the Internet using wireless DSL, and the connection normally works flawlessly.
The problem is when he tries to access some files on one site - "newsticker.shortnews.de" (which serves news headlines using JavaScript). If he types that address into IE6 or Avant, he gets a "Cannot find server or DNS error" message. Now this is where it gets weird, in my opinion. Running "nslookup" on that host name, from his computer, gives the correct IP address, 195.27.247.202. Pinging the hostname succeeds - but reports the ping is coming from localhost (127.0.0.1). Entering the IP address (i.e., the numbers) into IE6 or Avant accesses the Web site correctly. Running "tracert" using the NAME finds a route to localhost (127.0.0.1). Running "tracert" on the NUMBER finds a route to the Web site.
What could be going on? I've always thought that if you can resolve an IP address from the command prompt, then DNS is working properly and you should be able to resolve an address from a Web browser as well. And I'm used to DNS working either 100% or not at all - but again, he can access every other Web site he's tried without any problems.
Thanks for any help, y'all!
--Michael
I'm hoping you can help me with this problem that has completely stymied me...
A friend of mine has a PC (AMD Athlon 1.86GHz, 512 MB RAM, "modern", WinXP Pro Version 2002 SP 1); for Web browsing, he uses Internet Explorer 6 as well as another Web browser called Avant. He connects to the Internet using wireless DSL, and the connection normally works flawlessly.
The problem is when he tries to access some files on one site - "newsticker.shortnews.de" (which serves news headlines using JavaScript). If he types that address into IE6 or Avant, he gets a "Cannot find server or DNS error" message. Now this is where it gets weird, in my opinion. Running "nslookup" on that host name, from his computer, gives the correct IP address, 195.27.247.202. Pinging the hostname succeeds - but reports the ping is coming from localhost (127.0.0.1). Entering the IP address (i.e., the numbers) into IE6 or Avant accesses the Web site correctly. Running "tracert" using the NAME finds a route to localhost (127.0.0.1). Running "tracert" on the NUMBER finds a route to the Web site.
What could be going on? I've always thought that if you can resolve an IP address from the command prompt, then DNS is working properly and you should be able to resolve an address from a Web browser as well. And I'm used to DNS working either 100% or not at all - but again, he can access every other Web site he's tried without any problems.
Thanks for any help, y'all!
--Michael