Re: Local machine - DNS issues?

From: Corey B. (corey_bunch_at_yahoo.com)
Date: 09/10/04 

Date: 10 Sep 2004 05:46:40 -0700

Thanks for everyone's suggestions, but still no progress. The bad
machine is configured exactly the same as the good machine in TCP/IP
properties - everything except IP Address is identical on both
machines- gateway, primary and secondary nameservers. Also - no
firewall software has been installed on this machine and the default
services are started & running, including DNS Client service.

"Mark Renoden [MSFT]" <markreno@online.microsoft.com> wrote in message news:<esjiC1rlEHA.2588@TK2MSFTNGP12.phx.gbl>...
> Hi Corey
>
> Looking at the network traces you sent me:
>
> Good machine: We see a DNS request and response that resolves the name to
> an IP address:
>
> Request - DNS: 0x2623:Std Qry for www.yahoo.com. of type Host Addr on class
> INET addr.
> Response - DNS: 0x2623:Std Qry Resp. Auth. NS is www.yahoo.com. of type
> Canonical name on class INET addr.
>
> If you expand these in Network Monitor, you can see them in much greater
> detail.
>
> Bad machine:
>
> Request - NBT: NS: Query req. for WWW.YAHOO.COM <00>
>
> There is no response.
>
> The request on the bad machine isn't a DNS request but a NETBIOS request.
> This suggests to me that the bad client isn't correctly configured to use a
> DNS server or possibly the DNS Client service is not started. I can see
> from the good trace that the DNS server being used for successful name
> resolution is 152.1.1.206.
>
> Kind regards
> --
> Mark Renoden [MSFT]
> Windows Platform Support Team
> Email: markreno@online.microsoft.com
>
> Please note you'll need to strip ".online" from my email address to email
> me; I'll post a response back to the group.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Mark Renoden [MSFT]" <markreno@online.microsoft.com> wrote in message
> news:O5jKYQilEHA.1356@TK2MSFTNGP09.phx.gbl...
> > Hi
> >
> > A network trace would be conclusive:
> >
> > 1. Install network monitor on a working and non-working client.
> >
> > 2. At a command prompt, run the following on each:
> >
> > ipconfig /flushdns
> >
> > 3. Start a network trace on each.
> >
> > 4. Attempt to ping an internet name on each and wait for positive or
> > negative results.
> >
> > 5. Stop the network traces and compare the results.
> >
> > If you need a hand, feel free to email me the traces and I'll take a look.
> >
> > Kind regards
> > --
> > Mark Renoden [MSFT]
> > Windows Platform Support Team
> > Email: markreno@online.microsoft.com
> >
> > Please note you'll need to strip ".online" from my email address to email
> > me; I'll post a response back to the group.
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >
> > "Ace Fekay [MVP]"
> > <PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
> > message news:efj0a%23hlEHA.3876@TK2MSFTNGP15.phx.gbl...
> >> In news:OE8LT9blEHA.2020@TK2MSFTNGP09.phx.gbl,
> >> Doug Sherman [MVP] <dsherman@nospam.tampabay.rr.com> made a post then I
> >> commented below
> >>> Try:
> >>>
> >>> 1. Delete the hosts file in C:\WINNT\System32\Drivers\etc
> >>>
> >>> 2. Check Event Viewer for errors
> >>>
> >>> Doug Sherman
> >>> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >>>
> >>
> >> In addition, if that doesn't help, make sure no services are disabled,
> >> such
> >> as the DHCP Client service (its a required service).
> >>
> >> --
> >> Regards,
> >> Ace
> >>
> >> Please direct all replies ONLY to the Microsoft public newsgroups
> >> so all can benefit.
> >>
> >> This posting is provided "AS-IS" with no warranties or guarantees
> >> and confers no rights.
> >>
> >> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> >> Microsoft Windows MVP - Windows Server - Directory Services
> >>
> >> Security Is Like An Onion, It Has Layers
> >> HAM AND EGGS: A day's work for a chicken;
> >> A lifetime commitment for a pig.
> >> --
> >> =================================
> >>
> >>
> >
> >

Relevant Pages

  • Re: Local machine - DNS issues?
    ... Response - DNS: 0x2623:Std Qry Resp. ... The request on the bad machine isn't a DNS request but a NETBIOS request. ... Stop the network traces and compare the results. ...
    (microsoft.public.win2000.dns)
  • Re: Local machine - DNS issues?
    ... Response - DNS: 0x2623:Std Qry Resp. ... The request on the bad machine isn't a DNS request but a NETBIOS request. ... Stop the network traces and compare the results. ...
    (microsoft.public.win2000.networking)
  • Re: Local machine - DNS issues?
    ... including DNS Client service. ... We see a DNS request and response that resolves the name to ... > The request on the bad machine isn't a DNS request but a NETBIOS request. ... >> If you need a hand, feel free to email me the traces and I'll take a look. ...
    (microsoft.public.win2000.networking)
  • Re: W2k DNS limitationload
    ... responsibility of the resolver to determine the kind of response it ... added sometime after W2k release in order to harden the DNS server ... >> William Stacey, MVP ...
    (microsoft.public.windows.server.dns)
  • Re: Secondary (backup) domain controller not working ?
    ... client side, as well as if the previous logon server and record was cached. ... is waiting for a response from the server. ... If the query sent to the first entry in the DNS ... As I mentioned, this is ALL based on the client side resolver, not the DNS ...
    (microsoft.public.windows.server.active_directory)
Loading