Sheesh! I am glad I've never really had to worry about NT domains. That being said, can you try to force synchronization between the PDC and the BDC? The only time I've seen an error of that phrasing is when we've rebooted one of our Windows 2003 DCs (actually do it several times per week, to prevent problems from memory leaks on one machine) and we'll get a temporary error like that, but then it rights itself.
So, my suggestion boils down to forcing the BDC and the PDC to resync and see if that helps. -----Original Message----- From: Eric Brouwer [mailto:er...@forestpost.com] Sent: Thursday, April 08, 2010 10:30 AM To: NT System Admin Issues Subject: Roaming profiles issue Good morning, I'm having a roaming profile issue this morning on a (don't laugh) Windows NT domain. A few of our legacy PCs login to the old NT domain for their roaming profiles. When users login, they get an error that their profile is not available. There is a PDC and a DBC. Profiles are on the BDC. The PDC and BDC can see each other, and I can browse the shares on both, but when I go into the shares, I get an inaccessible error. From my laptop, which is not part of the domain, I can open files on the PDC, but not on the BDC. In the event viewer of the BDC I'm getting an Event ID:3096. The Windows NT domain controller for this domain could not be located. Any idea what might be wrong? We had a power outage last night, but this is the only issue we're running into. Thanks, Eric Brouwer IT Manager www.forestpost.com er...@forestpost.com 248.855.4333 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
