Re: Unable to login locally to workstation via domain or locally - reposted

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

At this stage workstation doesn't belong to domain because you re-created
computer account on DC. This is why I suggested to try logon to workstation
(with domain credentials) when there is no connectivity to DC. If that
doesn't work, try local administrator credentials. If you don't remember
local admin credentials you might need to look for some tools to reset
password. Only than you can take workstation out of domain and try to rejoin
after reboot.

--
Jan Wakulicz
www.micropol.com.au


"Simon" <simon@xxxxxxxxxxxx> wrote in message
news:FlySf.155$Ph2.116@xxxxxxxxxxxxxxxxxxxxxxx
Hi Jan, thanks for the reply.
After not being able to login locally or via the domain, and also looking
at the issues regarding the original problem we had where I could not view
the event logs on the PC from the server console (some sort of break in
the secure channel from the PC to server from the info I got) I deleted
the computer from the server, re-added it, then deleted the current IP
address lease in the dhcp server, got the client to the reboot. One thing
I noticed in the computer properties for this one is that the dns name
when you double click on the computers from the server management screen
is the name is just the computer, not computer.domain.local as all the
others are. We still couldn't login locally, or to the domain or even no
network and even tried safe mode..
To complete the story, the computers I setup for them are fine, this one
is a new PC from HP they have put on the network, run a transfer files and
settings wizard from the old win2k machine, then added to the domain using
the normal /connectcomputer method. It worked fine for about 2 weeks
before these issues (I suspect the access log error was there all along
though) I haven't done anything without using wizards apart from setting
up WSUS for them.
I think I may need to look into just gaining access to this PC using 3rd
party tools, what concerns me is why it happened in the first place, and
could it happen again.
Thanks Simon.
Jan wrote:
If you cannot login at all, HOW did you add PC back to the domain after
recreating computer account?
You are not telling the whole story.
Unplug network cable from PC and see if you can login using cached
credentials.



.

Relevant Pages

  • RE: Unable to connect to anonymous network share
    ... installed on a network ... I am setting up an anonymous share on the server. ... If I use credentials, I have no problem connecting to ... if I use any other Windows XP workstation ...
    (microsoft.public.windowsxp.security_admin)
  • Re: user migration
    ... I don't think the problem is with the server. ... The problem should be on the workstation and it's very difficult to tell without having access to it. ... If I had to guess I would say that some security settings might be preventing the wizard from running. ... >>> means that the computer account has not yet been used ...
    (microsoft.public.windows.server.sbs)
  • Re: Computer Connect Wizard
    ... Logon to the server and open the Management console ... Check if the name of the workstation is already there. ... Locate the computer account there, ... Logon to the workstation. ...
    (microsoft.public.windows.server.sbs)
  • SBS 2003 Premium, user changes password and loses network share access
    ... Basically the policy on the server requires a new password every x days. ... The same user could login on other PC's with no issue. ... help and even using other credentials resulted in a error (Multiple ... This is the second time the problem has occurred on this workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW and "Connect to my computer at work" link
    ... 2003 and for it not to work on an in place upgarde of Win 2k server ... you could move one XP workstation to the SBSComputers ... >b) delete the workstation computer account at the server ... >What are the differences between these two computer accounts, ...
    (microsoft.public.windows.server.sbs)