Archived from groups: microsoft.public.win2000.dns (
More info?)
"serge calderara" <sergecalderara@discussions.microsoft.com> wrote in
message news:4F1EE410-61E3-4F0B-A91E-C8FF04503908@microsoft.com...
> Even if the ping the full server name is working, the nslookup stiil
fails...
Be more specific please:
The nslookup of the FULL name fails when
the PING of the FULL name fails?
If that is the case, then the DNS server is not resolving the name
for the client, but rather the client is using one of the alternate
methods (or a different DNS server if the first one is not answering
at all):
(client DNS cache)
hosts file
NetBIOS methods
(NetBIOS cache/memory)
Broadcast (same subnet only)
WINS server
LMHosts file
The caches above are largely irrelevant since if that
were the source of the resolution it would need to come
originally from one of the other methods -- but do note that
NSLookup does bypass the DNS resolver client side cache.
--
Herb Martin
"serge calderara" <sergecalderara@discussions.microsoft.com> wrote in
message news:4F1EE410-61E3-4F0B-A91E-C8FF04503908@microsoft.com...
> Even if the ping the full server name is working, the nslookup stiil
fails...
>
>
> "Herb Martin" wrote:
>
> > > What could I check more from server side ?
> > > What do you mean by
> >
> > Read my other (first) post this thread.
> >
> > "serge calderara" <sergecalderara@discussions.microsoft.com> wrote in
> > message news:8B72BE73-696B-4763-8CDF-290344B9B69A@microsoft.com...
> > > Some more information..
> > >
> > > When I ping my dns server with its full name instead of IP, ping is
> > succesfull
> > > From client side my Primary DNS server IP is automatically given my
DHCP
> > service unning on my server.
> > >
> > > My server adress settings are:
> > > IP: 192.168.1.20
> > > Mask: 255.255.255.0
> > > gateway: 198.168.1.1
> > > DNS ip: itself (127.0.0.1)
> > >
> > > On my client Xp machine DHCP gives to my adapter card folowing
parameters:
> > >
> > > IP : 192.168.1.2
> > > Mask: 255.255.255.0
> > > Gateway:192.168.1.1
> > > DNS: 192.168.1.20
> >
> > Looks good.
> >
> > > ON both side Gateway adress is an ADSL modem router but I do not car
about
> > i for now.
> >
> > Right, that is irrelevant.
> >
> > > SO based on that I geus that the client is configure properly as there
is
> > nothing mucg I can set here except thos IP settings given by DHCP
> >
> > See my other post.
> >
> > You don't seem to have a problem now though.
> >
> > Ping by name works now, right?
> >
> > NSlookup probably works also....
> >
> > It might require the "full name" (as I said before) if you
> > don't have the workstation's full domain name in the System
> > control panel set correctly.
> >
> > > From DNS server side, the reverse zone is the default one that you can
see
> > when you select from View - Advanced
> > >
> >
> >
> > --
> > Herb Martin
> >
> >
> > "serge calderara" <sergecalderara@discussions.microsoft.com> wrote in
> > message news:8B72BE73-696B-4763-8CDF-290344B9B69A@microsoft.com...
> > > Some more information..
> > >
> > > When I ping my dns server with its full name instead of IP, ping is
> > succesfull
> > > From client side my Primary DNS server IP is automatically given my
DHCP
> > service unning on my server.
> > >
> > > My server adress settings are:
> > > IP: 192.168.1.20
> > > Mask: 255.255.255.0
> > > gateway: 198.168.1.1
> > > DNS ip: itself (127.0.0.1)
> > >
> > > On my client Xp machine DHCP gives to my adapter card folowing
parameters:
> > >
> > > IP : 192.168.1.2
> > > Mask: 255.255.255.0
> > > Gateway:192.168.1.1
> > > DNS: 192.168.1.20
> > >
> > > ON both side Gateway adress is an ADSL modem router but I do not car
about
> > i for now.
> > >
> > > SO based on that I geus that the client is configure properly as there
is
> > nothing mucg I can set here except thos IP settings given by DHCP
> > >
> > > From DNS server side, the reverse zone is the default one that you can
see
> > when you select from View - Advanced
> > >
> > > What could I check more from server side ?
> > > What do you mean by
> > >
> > > regards
> > > serge
> > >
> > > "Herb Martin" wrote:
> > >
> > > > "serge calderara" <sergecalderara@discussions.microsoft.com> wrote
in
> > > > message news:141BD03F-D4C5-4859-BDC8-7491DE8DB6AF@microsoft.com...
> > > > > Dear all,
> > > > >
> > > > > I have setup a test environement at home which is based on a W2000
> > server
> > > > PC setup as a domain controler. On that server DHCP and DNS is
> > confugure.
> > > > > Domain name is home.net.
> > > > >
> > > > > Then I have a client PC running XP that I would like it to join
that
> > > > domain.
> > > > > From the client I can ping succesfully the DNS server IP, and DHCP
is
> > > > running fine.
> > > >
> > > > That might be due to broadcasts unless you are pinging
> > > > the full name server.yourdomain.com. or whatever.
> > > >
> > > > > Problem I get is that when trying to join the domain is raise an
error
> > > > that it can nor found the domain.
> > > >
> > > > This gives further evdicence that you have a DNS problem.
> > > > ....likely the CLIENT is misconfigured.
> > > >
> > > > > Then I run from the client command nslookup <my Server IP>
127.0.0.1
> > and
> > > > at that time DNS server fail to respond.
> > > >
> > > > And more evidence PERHAPS, but that nslookup command is a
> > > > REVERSE request and I bet you don't have the revere zone set
> > > > up -- and if you are running it from the CLIENT then this is
> > > > more evidence that you don't have DNS CLIENT side configured.
> > > >
> > > > Try this: nslookup ServerName.yourdomain.com server.IP.addr.ess
> > > >
> > > > (Put in the DNS server address as the last parameter.)
> > > >
> > > > If that works you server is fine.
> > > >
> > > > > DNS configuration is set with all default entries, and if I run
the
> > TEST
> > > > querry inside DNS it PASS all of them
> > > > > ON my client PC I am Administrator
> > > > >
> > > > > Do I have to add my XP machine inside my Domain Controler ?
> > > >
> > > > Not for DNS to work.
> > > >
> > > > But I bet you forgot to change the CLIENT NIC IP DNS server
> > > > properties to SOLELY the INTERNAL DNS server.
> > > >
> > > > You really need to do this on that DNS server too - servers are
> > > > DNS clients also.
> > > >
> > > > If you wish to resolve Internet names also, then use the the
> > > > Forwarding tab of the DNS server to put in the ISPs DNS
> > > > server address.
> > > >
> > > > > Do I have to set a particular account to be able to joind the
domain?
> > > >
> > > > Admins always can do it, but normally so can users. This is
> > > > NOT your problem though (at least so far).
> > > >
> > > > > What did I miss here ?
> > > >
> > > > DNS client NIC settings.
> > > >
> > > > --
> > > > Herb Martin
> > > >
> > > >
> > > >
> > > > > Thnaks for your reply
> > > > > regards
> > > > > serge
> > > >
> > > >
> > > >
> >
> >
> >
Facebook
Twitter
Instagram