"Brent" <Brent@discussions.microsoft.com> wrote in message news:E2BF36DF-D4BA-4B34-9491-87F485CE72A8@microsoft.com...
>I did both the IPCONFIG and NSLOOKUP and the DNS Server address on both match
> 192.168.0.1. When I did the NSLOOKUP it also showed the Default Server name
> and they are both the same.
So? We know that you have some kind of DNS because you claim
that you can connect to anything except microsoft servers.
Did you do lookups for the server names that you need to have
to connect with WU?
BTW that address is a local address, not an Internet address
so that would be no proof that you are using the same DNS
in each case.
> Any other ideas?
We don't really a clear indication that DNS is your problem.
That's just the first obvious thing to test. ping -n 1 would also
check it but telnet is a better connectivity test since it at least
can involve the same port you need to use to connect with a browser.
Tracing a connection attempt using Fiddler2 would give you more details about your failures.
Also, if you really can't open
http://www.microsoft.com/ you would
get some clues from XP's Diagnose Connection Problems... tool.
E.g. that is one the sites that tool tests, though that's not one of the ones
you need to connect to WU.
You may get better assistance in a more relevant forum or newsgroup
(such as XP networking).
Good luck
Robert
---
>
> "Robert Aldwinckle" wrote:
>
>>
>> "Brent" <Brent@discussions.microsoft.com> wrote in message news:BB2AB6E8-21FA-4D7D-9A43-EA6B1CAE7729@microsoft.com...
>> > When I try to connect to windows update it comes up with a message the page
>> > cannot be displayed.
>>
>> > I am able to access the internet but I can't get to Microsoft.com.
>>
>> > I a running Windows XP Pro. Does anybody have any ideas?
>>
>>
>> That is a symptom of a problem with your DNS.
>>
>> Obviously you can connect to some servers from "microsoft.com"
>> because you are posting using the web interface to newsgroups.
>> Even if this is with a different computer you could use this fact
>> to check its DNS with the problem one. E.g. use ipconfig /all
>> and nslookup in a cmd window on both.
>>
>>
>> Good luck
>>
>> Robert Aldwinckle
>> ---
>>
>>
>>