Start a discussion

I am having the EXACT same infuriating issue as Joe. Here are the steps I have taken so far with no luck.

I am trying to connect a client PC to my Windows Server 2016 Std. domain (With Server Essentials Role) via the client connector software "https://servername/connect". After entering the end user credentials the connector hangs for about 5 minutes and then gives the following error "The server is not available. Try connecting this computer again."

I checked that Server and client time/date are in sync

I am able to ping the server via name and IP. When I ping by name it responds with it's IPV6 address (not sure if this is normal).

I pointed client manually to server for DNS

Removed client connector software from add/remove programs, rebooted and tried again with no luck

Renamed the client to a name with no hypens or ASCII characters

I ran the commands listed in the following KB article: https://support.microsoft.com/en-us/help/2828269/the-web-configuration-file-may-become-corrupted-when-you-run-the-sfc-c

I later ran through the IIS procedure Mariette suggested earlier in the post, remove the client connector and rebooted again, still no luck. I also tried running the connector with the domain admin user/pass- that didn't help either.  

Any help would be greatly appreciated as I am SURE many people are going through this as well. Thanks.

This topic can be closed. You led me in the right direction. In the end, it was a certificate issue. My guy imported the cert multiple times creating multiple certificates with the same name. All is working locally and even remote domain join is working as expected.

Thank you for your help.

I finally had time to try the last request of installing DHCP on the Server instead of using the router. I have done this and the result are still the same. Any other ideas?

Thanks in advance.

I have done this and I still fail. When I enter the Domain Admin credentials or any other domain accounts that are administrators, I do not get the dialog box that you showed in your last post. I am familiar with that dialog box as I do that all the time on my own WSE domain and am always prompted. Instead of that dialog, I go directly to the dialog in the attachment.

And run the connector with Domain Admin credentials when you are asked for credentials. Ignore the warning as in the screenshot.

I just realized that I did not run the connector again as you asked. I ran the connector and I am still failing "Server not found". The logs look pretty much like they did yesterday. I can attach them again if you need them.

Mariette,

I do indeed get an error. If I enter the credentials to "Connect As", everything passes.

Hello Joe,

I have done a bit more research on the logs you attached earlier and I would like you to try this:

1. Open IIS Manager from the Server Manager,
2. In the left column choose WSS Certificate Web Service,
3. In the right column choose Basic Settings,
4. A little window will popup with a 'Test settings' button, click that. Does it throw a warning that the path is inaccessible? If so, continue to step 5 and close the Test Connection window
5. Click Connect as and choose Specific User and click set. In the box type the domain admin credentials in the format domain\admin and your password. Click OK
6. Click the Test Connection button again and see if the error is gone.
7. Try to run the Connect software again.

Thanks for the info. I would agree that it is a DNS issue since for some reason when the connector software starts it finds the WSE server by IP and does not give me the opportunity to use FQDN. Strange, because pinging the IP with -a returns the server name. 

Well, you can put anything in as a forwarder as long as it is a name server. I just put Google in or any name server outside of your premise. But the router will work also but I do not see a benefit because you should use your DNS server on your WSE for anything that is local.

Unfortunately this didn't work either. I have a question though in regards to forwarders. Almost everything I have read says I need to put a forwarder in for the router. Is this necessary and could it be a problem?

Thanks in advance.

I am beginning to think that there is an issue with IIS on your server but before we are going into this there is one thing you could try. Can you add forwarders in your DNS server properties? See screenshots. After this run on the client from an elevated command prompt ipconfig /flushdns and ipconfig /registerdns. Now try to run the connector again.

Just an FYI, removing the connector and re-installing did not work. I didn't expect it to, but it was worth a try.

Can you try to set DNS suffix on the network adapter of the client to MEDIQUICKINC.local and then run the connector?

What I do not understand is this:

[code=markup][6384] 170628.082949.0290: ClientSetup: Standard Ouptput: Server:  mqi-td340-dc.MEDIQUICKINC.local

[6384] 170628.082949.0290: ClientSetup: Standard Ouptput: Address:  192.168.1.10

[6384] 170628.082949.0290: ClientSetup: Standard Ouptput: 

[6384] 170628.082949.0290: ClientSetup: Standard Ouptput: Name:    MQI-TD340-DC.mediquickinc

[6384] 170628.082949.0290: ClientSetup: Standard Ouptput: Addresses:  198.105.254.63

[6384] 170628.082949.0290: ClientSetup: Standard Ouptput:       198.105.244.63[/code]

It seems that MQI-TD340-DC.mediquickinc and that is without the .local suffix. Where does that come from? Do you have some router that has also the local domain named like 'mediquickinc'? Do you recognize the IP address 198.105.254.63? What is it?

Is this a default WSE 2016? What else is installed?

This is completed, however, the message remains the same. I have attached the client log files.
 

Here you go.
 

Easiest way for me to troubleshoot this is if you post the output of ipconfig /all > server.txt and ipconfig /all > client.txt. Attach those text files to your answer and I will have a look.