Not able to connect computers to network via connector

Answered

I’m trying to add a computer using the Windows Server Essentials Client Connector, but I encounter the error: “The Server is not available. Try connecting the computer again.” I’ve attempted standard troubleshooting steps on the client, including manually setting the DNS to the server (192.168.1.5), disabling IPv6, and enabling network discovery, but the issue persists.

This server previously had an SSL issue after GoDaddy stopped renewing certificates for remotewebaccess.com. I resolved this by purchasing a new domain and SSL certificate from NameCheap, which restored remote access for existing machines. However, I’m now trying to connect six new Windows 11 machines, and this error appears. I initially encountered this problem after the SSL expiration but before getting the new domain. At the time, I attributed the issue to the SSL problem and didn’t prioritize fixing it since those machines didn’t need remote access. Now, I need this functionality to work for the new machines.

On the Windows 11 machines, I performed the usual preparations: I disabled IPv6, enabled SMB through Features, and turned on Function Discovery in Services. DHCP is functioning correctly, handled by the router, which is configured to point DNS to the server (192.168.1.5). On the server, DNS is set to only point to itself (192.168.1.5). I’ve also uninstalled and reinstalled the Windows Server Essentials role on the server and added WINS as an additional measure.

A notable issue is that the server’s NetBIOS name (server) does not resolve when running nslookup server, even though the A record for server exists in the DNS Forward Lookup Zone. Additionally, there’s a persistent secondary DNS entry pointing to the router (192.168.1.1) on the client, which I can’t eliminate despite the router’s DHCP settings specifying only 192.168.1.5. In the past, manually setting the DNS on the client resolved this, but it’s not working now.

I also tried adding the IDENTITY key in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Identity) on the client, as the connector deployment hangs at the ValidateUser task. This did not resolve the issue.

Both I and Grok are stumped by this problem. What can I do to resolve this and successfully connect the new Windows 11 machines?

WSEE Installer / WSEE Updater

AskAmyS asked 3 weeks ago

You must log in to post comments.

Answers (1)

Best Answer

The Windows Server Essentials Connector software works just fine at connecting Windows 11 (24H2, etc.) client computers to the server. We have dozens of them successfully connected up to various versions of Windows Server Essentials (2016, 2019, 2022, and 2025) over here without issue.

That being said… Are you attempting to remote domain join your client computers to the server (i.e. are you connecting them to the server via https://YourRWADomainName.com/connect rather than using http://YourServerName/connect)? If not, then the SSL certificate that you’re using in Anywhere Access/Remote Web Access (RWA) doesn’t matter in the least (seeing as Anywhere Access/Remote Web Access doesn’t even need to be configured on the server in order to locally join client computers to the server).

I cannot speak directly to why your specific client computers are having trouble locating the server (with all of the steps that you took/mentioned), but in order to successfully connect client computers to the Essentials server all that is required is for you to:

1. Ensure that the “SchUseStrongCrypto” and “SystemDefaultTlsVersions” .NET Framework security settings have been added to ALL of your client computers as well as to the server (and that they have been restarted afterwards).

2. Ensure that the server has been configured with a static IP address.

3. Ensure that the preferred IPv4 DNS server address of your server is set to the default 127.0.0.1 localhost/loopback address, and that the alternate IPv4 DNS server address is set to the IP address of your network router (e.g. 192.168.1.1) or other “known” DNS server (e.g. 8.8.8.8, etc.).

NOTE: IPv6 should also be enabled on the server, and its preferred IPv6 DNS server address should be set to the default ::1 (loopback) value.

4. Ensure that the preferred IPv4 DNS server address on ALL of your client computers has been set to the static IP address of the server, and that the alternate IPv4 DNS server address is set to the IP address of your network router (e.g. 192.168.1.1) or other “known” DNS server (e.g. 8.8.8.8, etc.).

After performing all of the steps above, the connector software should then be able to successfully locate (and communicate with) the server (assuming that you don’t have any other firewall, anti-virus, proxy, DNS, etc. settings that are interfering with the connection that is).

Also, if you don’t want to join your client computers to the domain, then be sure to use Microsoft’s SkipDomainJoin connection method BEFORE running the connector software on the client computers.

Mike answered 3 weeks ago
last edited 3 weeks ago

You must log in to post comments.

Your Answer

Post as a guest by filling out the fields below, or you may to post using your existing user account (register to create a user account if you do not already have one). Guest's questions will be moderated before being posted. NOTE: Your email address will not be published, nor will it be used for marketing purposes, etc. (as per our privacy statement).

Name*

E-mail*

Answer Details*

Screenshots