Re: Windows 2003 domain PDC emulator down and users unable to login

I found that a few of my dc's, although configured in Sites and
Services to be a GC, were not actually GC ready. Connect to your DC's
using the LDP utility. After initilazation of the utility to a DC and
your base DSA information is desplayed, somewhere at the bottom it
shows your GC information, such as:

1> isGlobalCatalogReady: TRUE;

If that reads FALSE, even though your configured correctly in SAS, you
may need to "UNCHECK" the GC option for that server, wait an hour and
recheck it. Then use the LDP utility to look to see that GCReady is
TRUE!

Just a thought, I had this problem too and this fixed it!

Shurley

On 29 Jan 2006 20:44:44 -0800, "Vern" <vernon@xxxxxxxx> wrote:

My environment:
Windows Server 2003 in Native Mode
1st domain controller (DC1): PDC emulator, Global Catalog, DNS, WINS &
DHCP.
2nd domain controller (DC2): Global Catalog, DNS, WINS
Workstations: All Windows XP Pro, most with SP1 & rest with SP2
DNS on both servers contain all the records for both controllers. So
does WINS.
The domain has been up since June 2005 with no major or even minor
problems AD wise.

My problem:
After hours, installed an application on DC1 (PDC emulator) which
required a reboot. During the reboot process, I was unable to login to
the domain from any XP workstation. Repeated login attempts failed.
Only after DC1 came back on-line was I able to login to the domain from
an XP workstaion. I was able to login to the domain on DC2 while DC1
was down though as you would expect.

In our labs, I took 3 PCs and brought up a Windows 2000 domain (native
mode) with the above configuration. 2 PCs for the DC1 & DC2 and 1 PC
for the WinXP Pro. Same login failure when DC1 (PDC emulator) is
powered off. Then duplicated the environment above with a Windows 2003
domain with same failed login result.

Question:
Everyone, who is anyone, claims that if all of your DCs are also Global
Catalogs then when the first installed DC (usually the one that will be
the PDC emulator) is off-line, workstations can still login to the
domain. This is not my experience. Anyone have any clues or suggestons
on why?

Thanks,
Vern
.

Relevant Pages

  • Windows 2003 domain PDC emulator down and users unable to login
    ... 1st domain controller (DC1): PDC emulator, Global Catalog, DNS, WINS & ... Repeated login attempts failed. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain users unable to print to parralel printer
    ... Additionally I have disabled the logon scripts that maps drive automatically upon domain users login but did not help to fix the problem. ... I don't understand why a new created domain account with the same privileges as the existing users can print. ... Did you configure the printer as "Default printer" after installing with the administrator account? ... workstations and we encounter a very strange problem which we can't ...
    (microsoft.public.windows.server.networking)
  • Re: Single Desktop?
    ... you can use roaming profiles & folder redirection (for My ... This requires that your workstations ... without having to go to the particular workstation, and login as ... have to setup email accounts for every different possible login. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Domain users unable to print to parralel printer
    ... workstations and we encounter a very strange problem which we can't ... The printer will only print if we login as the Administrator ... when user uses their domain account to login they are unable ...
    (microsoft.public.windows.server.networking)
  • Re: Linux Domain Logon
    ... > with a Domain login at the samba server) and I am fed up with Updating ... > / antivirussing etc. with the MS operating system. ... > The major software used on the Workstations is also available in the ... Linux apps are ok. ...
    (comp.os.linux.networking)
Loading