Re: Strange AD and DNS Error



"Chris-n-Jordan" <chrismcbr@xxxxxxxxx> wrote in message
news:1141337229.906848.260110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the reply....

First, the DHCP has the DNS listed which should give the PDC IP address
in response to the request for Default Domain- AMP

Huh? Ok, but in neither this explanation or you original is it
giving the "DC" but rather it appears the default DOMAIN.

That should NOT be an IP but rather the machines domain name.

Every machine should ALSO have the correct name set in the SYSTEM
control panel.

As to the IP, the DHCP should provide the IP of the DNS server
which may also be the DC but that portion is irrelevant to making
it work -- just an accident of the way we run our systems with
multiple service roles.

As for DHCP- I don't really suspect DHCP...I was just noting that it
was one player in the game... It really passes off the issue to DNS
immediately. The problem is that when the login goes through so
quickly, the DNS resolution is not happening and the DC is not
contacted and the GP is not applied.

Well we know that DHCP completes BEFORE the computer
logs (itself) on, before it obtains its GPOs (if any), before it
logs on any user (even autologon).

All of these must happen after DHCP and DNS are working
since they are required for any network IP access.

This is a regulary user profile on the domain, but I have put it in its
own OU and set up a special set of policies that apply to it.

Profiles are not assigned through or by OUs unless you have
figured out something that I don't know....

Do you mean GPO or do you mean Profile? Group Policies
are something entirely different from profiles....

Not only
is it heavily locked down in terms of NTFS permissions, it can't do
much of anything...see my computer, execute an exe, no command
prompt...etc.

I will run the NetDiag and DCDiag tests tomorrow. I will also
experiment with some kind of script to increase the logon timout time.

If that works, then the answer is a (semi)bug and this solution (of
mine) is pretty cheesy. But hey, it if works it works.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


.



Relevant Pages

  • Re: Taking over Operations Master / DC roles
    ... I suggested you replicate the DNS service and zones ... Neither DHCP or User Profiles are a "DC" function ... Profile storage is a File Server function, ...
    (microsoft.public.win2000.active_directory)
  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: dhcp not matching DNS
    ... What we are finding is the client will get a lease and you check dns ... and it does not match what was given by dhcp. ... To elaborate on scavenging and DnsUpdateProxy group that Meinolf mentioned, please read the following to gain a better understanding of how the whole thing works. ... Force DHCP to register all records, Forward and PTR, (whether a client ...
    (microsoft.public.windows.server.dns)
  • Re: Duplicate HOST A record entries on the reverse lookup Zone
    ... then 24 and did the manual/ start scavenging of the stale resource records ... Used the DHCP server to update DNS records: ... "Set Aging/Scavenging for All Zones. ...
    (microsoft.public.windows.server.dns)
  • RE: Remote Access Issue
    ... the DHCP server do not update the A record for the ... Click DNS ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)

Quantcast