Re: Lost NT 4.0 Domain access on all win2k machines
From: Rob Elder, MVP (relder_at_thisisnotcorrect.com)
Date: 02/07/04
- Next message: Rob Elder, MVP: "Re: Copying User Profile Issues"
- Previous message: Arild Bakken: "Re: Problems with WMI on cluster"
- In reply to: Joe Smith: "Lost NT 4.0 Domain access on all win2k machines"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 7 Feb 2004 07:15:44 -0500
Try removing the DNS configuration on one of the clients. Then see if it
will authenicate to the NT PDC.
"Joe Smith" <anonymous@mybox.com> wrote in message
news:esweU1V7DHA.3024@tk2msftngp13.phx.gbl...
> situation: nt server 4.0 w/several win2K workstations ... everything
worked
> fine ...
>
> ran trial version of 2003 server 2 see if it would forfill some
requirements
> for a small office ... did the research and 2003 seemed to be a viable
> answer to several concerns. AFter many experiences in the past with
> microsoft products, risk managment was assessed and a plan for recovery
was
> implimented.
>
> if there was ANY warning that win2k machines would not be able to turn
back
> to their original NT server 4.0 domain controller, this DANGEROUS
trialware
> would have been scrapped the moment it was burnt onto a CD. There is NO
> documentation on how to revert back to the original domain controller or
how
> to remap files again. the answer after trying 2 reautenticate with the
> orginal domain controller is: no logon servers are availble to service
the
> request.
>
> test was done w/a test machine. the original was simply disconnected from
> the net. TEST MACHINE was established and tested ok - identical to the
> original NT server 4.0 - upgraded the TEST system and the TRIALWARE
upgrade
> bombed big time - forced a re-format of system disk. After several trial
> runs to configure this nasty dangerous-ware, it is NO EASY task to GO BACK
> to NT server 4.0 - as I've experienced. The only OS that would listen and
> was NOT affected were windows 3.11, 95, 98, ME, and NT wkst.
>
> I've established a web page with more details - along w/a few other
> NASTY-WARE experiences of which FIXES have been established to restore
> bungled installations.
>
> after looking around at microsoft web sites to see what has to be done to
> FIX win2K workstations to authenticate and map the original NT 4.0
> directories and such (sharing, etc) it has come down to one possible
> answer - reinstall all the win2k systems again - NOT ACCEPTABLE.
>
> There is a ACTIVE DIRECTORY icon in the networks that cannot be removed,
> along with other security issues, including not being able to update the
> local security profile using local admin privilidges.
>
> is there something I've missed here? or are all the win2K installations
> basically SCREWED UP permanantly of which requires re-installation to
regain
> NT server connectivity again?
>
> I have not had much time to read every article - hope no one else has had
> this problem yet - or maybe you have and can offer the solution Microsoft
> does not seem to provide for such a situation.
>
> Thanks for your help
>
>
>
>
- Next message: Rob Elder, MVP: "Re: Copying User Profile Issues"
- Previous message: Arild Bakken: "Re: Problems with WMI on cluster"
- In reply to: Joe Smith: "Lost NT 4.0 Domain access on all win2k machines"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
