Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Internet Explorer / General Topics / June 2007

Tip: Looking for answers? Try searching our database.

Dns problems with vista

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dns problems with Vista - 26 Jun 2007 20:06 GMT
have a cisco 2800 router with 7 linksys accesspoints. As client i have
xp,vista and apple.

All xp clients works well they can surf in internet without any problems.
But vista and apple clients doesn't.

i check everything but have till now not any solution. For exempla Vista pc
got all information from the router. i checked ip adress and dns adresses
well. if i ping to the dns adresses no problem but if i ping to
www.google.com i did'nt get any answer. And if i ping direct ip adress from
google like ping 209.85.135.104 i got answer.

Same in the browser if put www.google.com no answer and if i put the
ipadress i can surf.

i put ipadress and dns manualy but does'nt help.

And with nslookup i can't see the dnsservername i can see only ip adress.
Robert Aldwinckle - 27 Jun 2007 16:23 GMT
(cross-post added to Vista Networking)
> have a cisco 2800 router with 7 linksys accesspoints. As client i have
> xp,vista and apple.
[quoted text clipped - 6 lines]
> well. if i ping to the dns adresses no problem but if i ping to
> www.google.com i did'nt get any answer.

More significantly than getting a response to a ping is what address
the lookup for the ping resolved to--also whether in order to resolve
that name to an IP address it also had to discover the canonical name
for an alias, which  www.google.com  usually is.   Notice that  ping -n 1
can show you both, even if the ping itself fails:

<cmd_output>
Non-authoritative answer:
Name:    www.l.google.com
Addresses:  64.233.167.104, 64.233.167.99, 64.233.167.147
Aliases:  www.google.com

F:\>ping -n 1 www.google.com

Pinging www.l.google.com [64.233.167.147] with 32 bytes of data:
</cmd_output>

> And if i ping direct ip adress from
> google like ping 209.85.135.104 i got answer.

Where did you get that address?   FWIW  reverse lookup here shows:

<nslookup>
Name:    mu-in-f104.google.com
Address:  209.85.135.104
</nslookup>

> Same in the browser if put www.google.com no answer and if i put the
> ipadress i can surf.
>
> i put ipadress and dns manualy but does'nt help.

It may help if you explained exactly what you did in case
there are errors in your procedure.

> And with nslookup i can't see the dnsservername i can see only ip adress.

Guessing that you're seeing a local address for that?
E.g.  via  ipconfig  /all

What happens if you log on to your router and find the real  DNS  addresses
being used?   Then use either one of them as second operands for  nslookup?
In fact, I think that getting those real addresses is what you would have had
to do anyway to "put ipadress and dns manualy".   So then if you had done
that correctly  ipconfig /all  would have been showing them there too.
Otherwise I don't think that there is a requirement to have a reverse lookup
for dns server names.

If you're having trouble with your real  DNS  addresses it may help
to use  nslookup  in its interactive mode with  set debug  as the first
command.

BTW This is slightly off-topic for the IE NG and I don't use Vista.
You may get more knowledgeable assistance from Vista Networking.
E.g. another possible unique factor with it will be whether  IPv6  is involved.
Cross-posting for convenience.

Good luck

Robert Aldwinckle
---
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.