Login error

%3CLINGO-SUB%20id%3D%22lingo-sub-1303822%22%20slang%3D%22en-US%22%3ELogin%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303822%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20new%20HPE%20Server%20with%20Windows%20Server%202019%20that%20I%20am%20setting%20up%20to%20replace%20a%20Windows%20Server%202008%20Server%20and%20have%20a%20log%20in%20problem.%26nbsp%3B%20What%20led%20up%20to%20the%20problem%20is%20that%20I%20decided%20to%20change%20the%20name%20of%20the%20Server%20to%20that%20both%20servers%20don't%20have%20the%20same%20name%20on%20the%20network.%26nbsp%3B%20I%20went%20into%20the%20settings%20and%20changed%20the%20name.%26nbsp%3B%20It%20said%20changes%20will%20be%20made%20after%20a%20restart.%26nbsp%3B%20I%20restarted%20it%20and%20when%20I%20try%20to%20log%20in%20now%20I%20get%20the%20message%3A%20The%20security%20database%20on%20the%20server%20does%20not%20have%20a%20computer%20account%20for%20this%20workstation%20trust%20relationship.%26nbsp%3B%20There%20are%202%20users%20configured%20on%20the%20server%20and%20I%20get%20the%20same%20message%20for%20both.%26nbsp%3B%20It%20gives%20me%202%20other%20options%20to%20sign%20in%20but%20neither%20of%20them%20seem%20to%20work.%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20are%3A%20%22Type%20domain%20name%5Cdomain%20user%20to%20sign%20in%20to%20another%20domain%22%20or%3C%2FP%3E%3CP%3E%22Type%20*******%5Clocal%20user%20name%20to%20sign%20in%20to%20this%20pc%20only(not%20a%20domain).%26nbsp%3B%20Whereas%20*******%20is%20the%20new%20name%20of%20the%20server%20that%20I%20renamed%20it%20to.%26nbsp%3B%20Any%20ideas%20on%20how%20to%20log%20in%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJason%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1303822%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303912%22%20slang%3D%22en-US%22%3ERe%3A%20Login%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303912%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20the%20trust%20is%20now%20broken%20you'll%20need%20to%20logon%20with%20a%20valid%20local%20account%20in%20the%20form%20of%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3Eservername%5Cusername%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3CLI%3E%3CSTRONG%3E.%5Cusername%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303951%22%20slang%3D%22en-US%22%3ERe%3A%20Login%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303951%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%26nbsp%3BThank%20you%20for%20the%20reply.%26nbsp%3B%20When%20I%20try%20to%20log%20on%20with%20the%20original%20name%20of%20the%20server%20Poweredge%5Cadministrator%20and%20the%20administrator%20password%20I%20get%20a%20message%20that%20states%3A%20An%20attempt%20was%20made%20to%20log%20on%2C%20but%20the%20network%20logon%20service%20was%20not%20started.%26nbsp%3B%20The%20problem%20started%20after%20I%20renamed%20it%20to%20Poweredge2.%26nbsp%3B%20Do%20I%20log%20on%20using%20the%20original%20name%2C%20Poweredge%2C%20or%20the%20second%20name%3F%26nbsp%3B%20I've%20tried%20it%20numerous%20ways%20and%20it%20wont%20accept%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303983%22%20slang%3D%22en-US%22%3ERe%3A%20Login%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303983%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20roles%20are%20installed%3F%20I'd%20certainly%20try%20them%20all%2C%20but%20it%20sounds%20like%20the%20server%20may%20now%20be%20somehow%20broken.%20If%20this%20is%20the%20case%20I'd%20suggest%20restoring%20a%20recent%20backup.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1306066%22%20slang%3D%22en-US%22%3ERe%3A%20Login%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1306066%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%26nbsp%3BI'm%20not%20sure.%26nbsp%3B%20This%20is%20a%20brand%20new%20set%20up%20and%20haven't%20set%20up%20back%20up%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1306136%22%20slang%3D%22en-US%22%3ERe%3A%20Login%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1306136%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20a%20new%20setup%2C%20the%20quicker%20solution%20is%20probably%20to%20clean%20install%20it%2C%20patch%20fully%2C%20and%20try%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,

 

I have a new HPE Server with Windows Server 2019 that I am setting up to replace a Windows Server 2008 Server and have a log in problem.  What led up to the problem is that I decided to change the name of the Server to that both servers don't have the same name on the network.  I went into the settings and changed the name.  It said changes will be made after a restart.  I restarted it and when I try to log in now I get the message: The security database on the server does not have a computer account for this workstation trust relationship.  There are 2 users configured on the server and I get the same message for both.  It gives me 2 other options to sign in but neither of them seem to work. 

They are: "Type domain name\domain user to sign in to another domain" or

"Type *******\local user name to sign in to this pc only(not a domain).  Whereas ******* is the new name of the server that I renamed it to.  Any ideas on how to log in?

 

Thanks,

 

Jason 

5 Replies
Highlighted

Since the trust is now broken you'll need to logon with a valid local account in the form of;

  • servername\username
  • .\username

 

 

 

Highlighted

@Dave Patrick Thank you for the reply.  When I try to log on with the original name of the server Poweredge\administrator and the administrator password I get a message that states: An attempt was made to log on, but the network logon service was not started.  The problem started after I renamed it to Poweredge2.  Do I log on using the original name, Poweredge, or the second name?  I've tried it numerous ways and it wont accept it.

Highlighted

What roles are installed? I'd certainly try them all, but it sounds like the server may now be somehow broken. If this is the case I'd suggest restoring a recent backup.

 

 

Highlighted

@Dave Patrick I'm not sure.  This is a brand new set up and haven't set up back up yet.

Highlighted

Since a new setup, the quicker solution is probably to clean install it, patch fully, and try again.