Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Scott Burg

Cannot connect Windows 10 PC to Server Essentials 2012

We inherited a Server Essentials 2012 server/domain. We were previously able to run the connector to join Windows 10 PCs to the domain (unless they were in-place upgrades from Windows 7). We now have 3 PCs running Windows 10 Pro for Workstations 21H2 that produce the error message stating "Cannot connect this computer to the network" and "The server is not available. Try connecting this computer again, or for more information see Troubleshoot connecting computer to the server." We are in a single-DC environment, so moving forward I will refer to the Server Essentials 2012 server as "server." When referring to the PC we have tried this on all three machines with the same result.

Here are the troubleshooting factors:

  • The server is fully updated according to Windows Update.
  • The PC is pointed to the server for DNS and is on the same subnet.
  • The PC resolves the server name on ping and can ping the server.
  • The error occurs after putting in credentials to join the PC. The connector is doing a credential check, putting in the wrong credentials throws a different error.
  • The time and date settings on the PC match the server.
  • The PC has not been joined to the domain.
  • There are no event logs on the PC or server that I could find that are triggered during the attempt to run the connector.
  • The connector is the 2012 version, it appears to find the server on its own prior to requesting credentials, although it is a very brief flash on the app.
  • The https://(server)/connect page is showing as not secure, so I know it doesn't have a valid certificate. It also only shows the download for Windows 7 and Windows 8 or for Mac.
  • The firewall is off on the PC and the server.
  • The server is running System Center 2012 Endpoint Protection, but I did test with Real Time Protection disabled.

I have done what feels like fairly exhaustive searches on Google and this site to troubleshoot the cause of this issue, and checked into more things that I am remembering to put above, but I feel like those are the salient details. I am open to any suggestions at this point.

Thank you in advance for any help that I can get on this issue.

Scott

asked02/25/2022 18:11
121 views
Add Comment
Scott Burg

Does the connector automatically install a WAN Miniport (SSTP)? I noticed that the process of trying to use the connector was installing it and I'm wondering if that is an indication that the installer thinks that this PC is not on the same subnet as the server.

Mariette Knap

No, the connector creates a VPN connector. Nothing special

replied 03/01/2022 05:07
Reply
David Moore
  • The PC has not been joined to the domain.
I could be wrong but fairly sure PC needs to be joined to the domain.
Mariette Knap

Using the Connector in this situation should join the workstation to the domain also but you can also first join the workstation manually to the domain and then run http://server/connect to install the connector software.

replied 02/27/2022 14:20
Scott Burg

Thank you both for your comments. I just tried to run the connector after joining the PC to the domain and it is giving the same error.

replied 02/28/2022 16:05
Mariette Knap

Can you check the client for the exact error message? The event log might show that for you.

replied 02/28/2022 16:10
Scott Burg

I didn't see anything in the logs that was relevant to the time(s) that I ran the connector.

replied 02/28/2022 21:24
Reply
Last Activity 03/01/2022 05:07

No answers found

Add an Answer