https://server-name/connect doesn't take me to the software
When I try to install the connection software for WSEE using https://server-name/connect it doesn’t take me to the webpage to install the connection software it takes me the main website for my domain. I checked out my other install of WSEE and it does the same thing.
I try to browse to https://server-name/connect and it automatically bounces to https://realcompanywebsite.com
Any idea what I did wrong and how I can fix it?
Peter
- PeterMac asked 4 months ago
- You must log in to post comments.
Sounds like you may have enabled a site redirection within IIS.
What version and edition of Windows Server are you currently using?
Do you have WSE RemoteApp installed? If so, did you enable its “Redirect ‘Default Web Site’ to ‘/remote’” setting on the “Security” subtab of the “Remote Desktop Sessions Settings” task that’s located on the “WSE REMOTEAPP” page of the server Dashboard? If so, then you might want to try disabling that setting and see if doing that resolves the issue for you (although I can’t imagine it causing that to happen).
Lastly, you might want to try performing a Repair of Anywhere Access just to see if that helps any (by clicking the “Settings” link up in the top right-hand corner of the main server Dashboard window, clicking on the “Anywhere Access” tab, and then clicking on the “Repair” button).
- Mike answered 4 months ago
- last edited 4 months ago
- You must log in to post comments.
Server 2022, standard.
No RemoteApp installed
Did the repair anywhere access and it still goes to the main website for the domain.
I will have to check out the site redirection within IIS.
- PeterMac answered 3 months ago
- You must log in to post comments.
No IIS redirects except for one for remote.domainname.com. If I go into the IIS manager on the server and go to the Default Web Site and tell it to browse it goes to remote.domainname.com just like it should. Going to any of subwebsites under the default takes me to domainname.com, I can see it go to localhost/connect before it flips to domainname.com
- PeterMac answered 3 months ago
- You must log in to post comments.
More interesting stuff.
If I go to
https://remote.domainname.com/connect it goes to the proper website so I can download the connection software
However the connection software when it runs cannot find the server with either remote.domainname.com, NetBios name or even when I type in the IP address.
Unfortunately I don’t know what it is trying to find to continue
- PeterMac answered 3 months ago
- You must log in to post comments.
Glad to hear that you managed to get the redirection issue resolved (care to share how you did it just in case others happen to run into a similar issue?).
As for the connector software not being able to locate the server… Have you tried setting the preferred IPv4 DNS server address within the network adapter settings/options, and adding the .NET Framework security settings, on the client (and then reboot) just as I’ve mentioned under the 8/25/2019 bullet point over here?
- Mike answered 3 months ago
- last edited 3 months ago
- You must log in to post comments.
Well I didn’t make any changes, I still can’t go to
https://server-name/connect it still kicks over to https://domainname.com
What I did was go to
https://remote.domainname.com/connect and that allowed me to download the software
client PC is set to use the AD as the DNS server and only the AD. I will checkout the .NET security settings
- PeterMac answered 3 months ago
- Interesting… Well, I’m not able to replicate that behavior over here and so I’m not really sure what could be causing it then. :- O
- You must log in to post comments.
Just to provide context, this is a server that was upgraded from SBS 2011 to Server 2022 using the migration kit from the people over at Server-Essentials and then adding your WSEE bit to things. To make things even more interesting we use a wildcard security cert.
- PeterMac answered 3 months ago
- Ah well that’s probably why you’re seeing the issues then. I typically recommend that folks start out with a brand new/clean (i.e. straight out-of-the-box) install of Windows Server in order to avoid such problems. Otherwise, if you’re forced to upgrade, then it’s always best to in place upgrade from anything pre-2016 to 2016, and then make sure everything in Essentials works properly before then in place upgrading 2016 on up to 2019/2022/2025.
- You must log in to post comments.
I must admit I have never done an in place upgrade of a server. I will have to give that a try when 2025 comes out
- PeterMac answered 3 months ago
- My bad… I assumed that you did an in place upgrade when you actually did a domain migration. Regardless, I still highly recommend a brand new clean install over a domain migration or an in place upgrade.
- You must log in to post comments.
So good news, updating the .NET security settings fixed the connector issue. It now will install (I haven’t actually installed it yet but it seems to be able to now).
Thanks for the help.
- PeterMac answered 3 months ago
- That’s good to hear. Thanks for letting everyone know that it worked for you. ;- )
- What security settings have you changed? On my case, all my pages are 404ed.
- You must log in to post comments.
I added the following reg file to both server and workstation (and rebooted). That fixed the connector software running for me at the workstation.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
“SystemDefaultTlsVersions”=dword:00000001
“SchUseStrongCrypto”=dword:00000001
- PeterMac answered 3 months ago
- You must log in to post comments.
