Cannot get Windows 11 PC to connect to MSE 2016

Anonymous
2023-11-11T23:17:59+00:00

I had a user account on the server become corrupted after an unplanned power interruption while the generator was being repaired. After banging my head against that wall for a while I decided to create a new user account and move her files into that account.

I suspended the offending account and added the new account on the server. When I first setup the new PC, however, I tried to use the Connector app for MSE but it wouldn't see the server. I also cannot change from Workgroup to Domain. Error "Server does not exist"; "Domain does not exist". I tried that with both static IPs and DHCP. Neither will it recognize the DNS name.

I can map drives to the server all day long and work on the internet but that's about all I can do. I'm really stumped here. I have been unable to find anything that directly addresses this issue. Am I doing something wrong or forgetting to do something?

Definitely will appreciate any suggestions! Thanks

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Anonymous
    2023-11-13T01:37:59+00:00

    Hello JGold7236,

    Thank you for posting in Microsoft Community forum.

    1.What do you mean about "MSE 2016"?Is it a Windows sever?

    2.What is "the Connector app for MSE"?

    Is "MSE 2016" also an DNS server? If so, you can set the Preferred DNS server on Windows 11 using the IP address of "MSE 2016".

    Check if you can ping the domain name or the IP of the domain or the FQDN of the Domain Controller.

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,
    Daisy Zhou

    0 comments No comments
  2. Anonymous
    2023-11-14T20:18:42+00:00

    Hi Daisy and Thanks!

    MSE is an abbreviation for Microsoft Server 2012 or 2016 Essentials. It's a less robust than the full server OS. It's for small businesses that don't have a full time IT person.

    MSE, rather than having to configure permissions for client PCs, uses a little "Connector" app to do all the heavy lifting of that task. It's how I set up this system in 2016 and in 2020.

    Essentials is also a DNS which is where I'm getting lost. I'm fairly certain that all these problems are related to permissions.

    Ping is another bone of contention. I can ping from the Win11 client to the server and from the server to the client. Which again to me sounds like permissions.

    Thanks again for the help! Have a great rest of your week!

    0 comments No comments
  3. Anonymous
    2023-11-15T08:03:23+00:00

    Hello JGold7236,

    Thank you for your reply.

    Please check if the machine you want to joined domain is in Active Directory Users and Computers? If so, you can try to remove/delete it and rejoin this machine to domain, then check if the same error?

    Please run nslookup on the client machine and check the result.

    Best Regards,
    Daisy Zhou

    0 comments No comments
  4. Anonymous
    2023-11-15T20:43:46+00:00

    Hi Daisy, thanks! I'll double check that. It's been a couple of days since I was in there but I'm fairly sure both computer name and the username are both showing up.

    I'm very grateful for the command. I'm slowly starting to get familiar with the inner workings of Active Directory. LOL

    Thanks again!

    0 comments No comments
  5. Anonymous
    2023-11-16T01:26:59+00:00

    Hello JGold7236,

    Thank you for your reply.

    You can try to remove/delete the computer name in ADUC (Active Directory Users and Computers) and rejoin this machine via the Connector app on client to domain, then check if you can join the client to domain successfully.

    Best Regards,
    Daisy Zhou

    0 comments No comments