Jan 14, 2020 Connecting a Windows 10 Pro to a Windows Server 2016 Essentials (TP3) with the Connector. Windows 10 is the ideal client for a Windows Server 2016 Essentials. Learn here how to use the Connector and join the client to the domain. Find answers to What are best practices for a Windows Server 2016 network with Mac OS X graphic design studio using Adobe Creative Suite products? From the expert community at Experts Exchange What are best practices for a Windows Server 2016 network with Mac OS X graphic design studio using Adobe Creative Suite products?
![]()
I can not get Licensing issue resolved on Essentials server for Remote access. While I'm familiar with Windows server, I'm less familiar with the Essentials SKU.The user has deployed Windows 2016 Essentials and completed the Access Anywhere wizard.It appears to deploy all the RDS roles, it configures it for per-user licensing and the essentials server is listed as the licensing server. There are no errors around the deployment other than the licensing notice. Licensing mode remains 'Remote Desktop for Administration'. I've noticed in the Technet forums where this was present on 2012 servers, but it seemed related to users who manually deployed the RDS role. In this case, everything was configured thru the Essentials wizard, so I assume here - all the roles should be deployed including the session host server.If this were a standard deployment we would load up the CALs and call it a day - but there should be no additional license configuration needed for an Essentials server.I've re-run the wizard and repaired the anywhere access - but nothing has changed.
Curious if anyone has hit this with 2016 and what they did to resolve it. Essentials will not work with the RDS roles at all, with the exception of RD Gateway. MS Support pointed me to the Server 2012 Licensing page, and referenced the fine-print, where is says '(8) Only the RD Gateway role service is installed and configured, other RDS role services including RD Session Host are not supported.' None of this is mentioned in any of the Remote Desktop Services licensing information, and it is also not mentioned in any way in the 2016 Essentials documentation.No way around it.
I'm currently having an issue with Windows Server 2016 essentials when trying to get anywhere access to work. I've forwarded port 80 and port 443 to the server and the setup has run smoothly. I'm working on this remotely through a computer that is set up on their network so if there are any issues I can just remote back into the computer and restart the server.I've tested the connect and the remote function and both seem to work on different networks. But when I try and connect a pc using the connector, something very strange happens. First of all, I enter the user's details and it looks to be connecting the right place (xxxx.remotewebaccess.com).Most of the time I get the 'the server is not available.
Try connecting this computer again' but sometimes it will just load indefinitely. I have tried this with multiple user accounts (Including Admins & Standard Users) but still no luck.Whenever I try and connect to the server using the connector, my remote desktop session disconnects and I am then effectively 'banned' from accessing the server (Besides remote desktop on a local machine nothing else will connect, not even the IP). I went to the anywhere access from a local machine and went to configure it again, but when doing so it says that either port 443 or port 80 is blocked.
So I restarted the server again, went back to the anywhere access section and went to re-configure and it went through the whole process with no issues. (Basically saying port 80 and 443 are open again). This keeps happening each time I try and connect a PC.I've never come across an issue like this before, so any help would be massively appreciated! I apologise if I have done anything incorrectly my end. Initially I thought it may be an issue with our external ip being 'blocked' by the router but according to BT this doesn't happen.Thank you in advance for your replies, I look forward to them!Cheers. Hi Kevin,Thank you for your suggestion, I tried to run the VPN setup but couldn't seem to get it to work. I think the setup requires that you have two NICS installed?In the end, the project was asked to be completed immediately so it resulted in me having to use a VPN service, in the end I used a free one called SoftEther VPN which seems to be working very well, I port forwarded 443 on the router connected to the server and also on the office router and things seem to be going very well. All users now have network drives (Which was the intention) but I can't seem to get the Windows server connector to work properly at all. Every time I try to connect using on the local network, the window just freezes and doesn't complete.alot of the time it will just kick up the 'Server Not Available' error. Any ideas what could be causing this?Also; Would just like to say thank you for your advice, it has been very helpful:).
Benfozzer wrote:I will have another shot at connecting it via the windows server VPN today, having it all in one place is preferable:) Thanks for your advice, I'll post any findings:)When trying to connect to the server (Even on a local network), using the I'm still experiencing the same issue (Even though I can access the public drives and even RDP from the machine). When typing in the user details, it hangs for about 2-3 mins.
![]()
Here's what it's saying from the local machine;What are your DNS settings on the workstations? Are you using the Essentials server for DNS or are you using something else?you should use the essentials for DNS and nothing else. In the DNS on essentials, set your forwarders to your ISP, Google, etc.Kevin. Benfozzer wrote:Have just had another look at setting up the Windows VPN, I'm getting the error when the 'Updating Network Connectivity Assistant Settings' and I'm getting the error 'No such host known'. I'm using the public IP address of the server for the hostname.Hmmm. What happens if you ping the IP and also ping the hostname? Do they resolve properly and respond?also, do you have the proper port open in your firewall for VPN traffic? Forwarded to essentials (if that is the endpoint)?Kevin.
Pinged the hostname, instant response. all received. pinged the ip and the same result. One thing I have noticed is that when I download the connector from it shows the IP at the end of the file name (Whereas, if I download the one from our server in the office the internal server name shows up) Would this have something to do with it at all?I've had a look around but can't seem to find anything about this that has worked for me:(I've set the DNS to the BT standard one that we were given by the ISP, so both the Client PC and Server are using the same DNS settings. Is this the right way of doing it?
Apologies if I'm being stupid, didn't do much networking during my time:(. Benfozzer wrote:Pinged the hostname, instant response. all received. pinged the ip and the same result. One thing I have noticed is that when I download the connector from it shows the IP at the end of the file name (Whereas, if I download the one from our server in the office the internal server name shows up) Would this have something to do with it at all?I've had a look around but can't seem to find anything about this that has worked for me:(I've set the DNS to the BT standard one that we were given by the ISP, so both the Client PC and Server are using the same DNS settings.
Is this the right way of doing it? Apologies if I'm being stupid, didn't do much networking during my time:(well using the incorrect DNS may be causing a lot of these issues. Review the for server essentials (yes older version) as most all of the info applies even to the current essentials 2016. Bring any other questions:)as far as the download filename - it doesn't matter.Kevin.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |