Re: Connecting but no internet!

Inline:

John Navas wrote:

In <1143226534.898181.139880@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> on 24 Mar 2006
10:55:34 -0800, danr_18@xxxxxxxxx wrote:

Yep, nslookup works, but ping or tracert say that it can't find the
server if I use the machine/domain names. If I put in the IP address
which I looked up in nslookup, it works fine.

That doesn't make sense -- they all use the same resolver. Please cut and
paste here the exact output of each.

It's someone elses computer. If I do nslookup, it resolves the name. If
I do a ping or tracert it gives me an error (I don't remember the exact
text). If I ping, tracert or use IE with an IP address, they all work
fine.

ipconfig /all show the DNS of the ISP (I've tried using the router or
one of the 'global' DNS servers - with the same results).

What happens when you configure DNS manually in your TCP/IP settings?

Same exact thing.

.

Relevant Pages

  • Re: Some DNS server names will not resolve using internal servers
    ... command above and now www.microsoft.com resolves as it should. ... I get ":Server Failed". ... and the MMC Properties page on both DNS servers and I still get:Server ... I have done all the nslookup commands. ...
    (microsoft.public.windows.server.dns)
  • Re: Resolution fails, running nslookup causes it to succeed
    ... and the server has eventually received the answer and is ... Resolution still failed after clearing the client cache and hitting retry. ... Browsing to download.nai.com fails due to our internal DNS servers not ... Then if we run nslookup against our DNS ...
    (microsoft.public.win2000.dns)
  • Re: nslookup question?
    ... > If nslookup is unsuccesful, FOR EXAMPLE, showing the ... > how can I force a client to see the Primary DNS as ... > Give me constant errors that RPC server is unavailable. ... for service locations on domain controllers, not for DNS servers. ...
    (microsoft.public.windows.server.dns)
  • Re: Resolution fails, running nslookup causes it to succeed
    ... and the server has eventually received the answer and is ... Resolution still failed after clearing the client cache and hitting retry. ... Then if we run nslookup against our DNS ... Likely irrelevant except that it may reflect flaky DNS servers on there ...
    (microsoft.public.win2000.dns)
  • Re: Machines never look to secondary DNS
    ... Default Server: UnKnown ... After you get these messages from nslookup, will the DNS servers ... These messages from nslookup are not indicative that DNS is not resolving. ...
    (microsoft.public.win2000.dns)