Is there additional logging I can turn on RDS01 that will show me why it is not letting the client connect? Per your issue, I advise you check the network settings on the RDS01 server, such as upgrade the NIC driver, check the NIC settings, check if the nework routers or firewall have blocked the connection. Please check whether the is occupied by other applications or you have changed the default RDS port to others.
Please check whether you are using the domain users or the local users for the RDP connection. To recap, loaded a new install Windows R2 64 bit server.
Activated and ran Terminal Server without installing license for days. It worked for days. Any of my WYSE clients could see the server. No issues there. I have the server set to use the lowest level security for the RDP connection just as it was before license installed , and it worked fine.
I am installing Service Pack 3 on the legacy XP machine, and will be installing a bunch of updates. Unfortunately, my client cannot go out and replace 6 WYSE boxes at this time. The solutions mentioned here are not working, now trying to downgrade Windows. We can't replace the 80 industrial Terminals because of licensing issues A few sites has Reatil licenes and there works fine, as soon as Open licenses has been installed the RPD 5 stops working.
The second thing not sure if releated we orderd for the 2 of the sites extra retaile licenses and we replaced the open with it. We found the same problem after the chane. It is quite urgent for us as we can not deploy any more to new cutomers especially as most customers has been moved to Windows R2 servers. All the firewall has been deactivated , all the sugetsed things has been tried.
Our assumption is either that there is incompatibility with the protocol. Note i tested today and i thought i made it working , but not i forgot to redicrect in the RDP host condifguration to use the licenses. Also having the same issue. I'm not seeing anything helpful in the event viewer.
My user count is no where near exceeding my CALs. I'm running out of ideas and time. Any updates? Apparently I was not the only one nor the OP; however, apparently this is not an issue for MS as no one has posted anything but us. We experience the exact same issue with Windows CE 5.
As soon as we turn on the licensing server, those devices failed to connect to servers that had been working during the grace period. They can still connect to other servers via RDP, just not any running RDS that have the license server configured. Took out the licensing server so none was specified and still unable to connect. Microsoft has not been much help, any solutions out there? I have the same problem. Just after specifying the server licence. Old thin client rdp 5.
I have 3 servers currently affected one of which is running Server x In order to keep my customer happy I've had to build them a new RDS Server so have a grace period of days again to ensure that this works. The 3 potential resolutions appear to be. I raised a ticket with Microsoft. They say it's due to a non supported client version. Not what I was hoping for but it will hopefully resolve the issue. The result is: as soon as I enable on the RDS server to connect to a specified TSE licence server to use user CAL, the mobile device fail to connect with error " Because of a security error, the client could not connect to the Terminal server ".
This should confirm i have read on other post about cals on R2 this the same on server : "contact with MS we found this behavior is by design and comes from the new RDS R2 CALs The new CALs have a length certificate and there for no client earlier than version 6 can handle these". We have got exact the same issue, anyone a solution? Same issue with an Intermac Handheld running Windows Mobile 6.
Could connect prior to installing Cals. Now can't. Error is "Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network and then try connecting again. The license manager is installed on the RDP Host. Today By my side, the only way to get handcompter to work with tse open usercal, is to have RDS licenceserver and RDS service on the same server.
Running R2. I could live with that solution as then the handheld would function. Are you running R2 or vanilla ? Ok, I might be onto something here. The common thing between the problematic ones are that the Server machine is not on a Domain. All of the problematic servers have an error in the event log as shown below:. Ensure that there is network connectivity between the license server and AD DS.
One of our customers was able to get this to work by installing the license on a different machine on their domain and then point the RDP server's licensing to that machine even though the RDP server isn't on the domain. Microsoft also told me it was due to an old version of Remote Desktop Mobile. Well, I get the same error with a handheld running, Win CE 5. I also tried the registry item as stated above and deleting the potential 'corrupt' registry items but it did nothing.
Uninstalled Remote services, deleted registry items, reinstalled, and got the same error. If you don't have 2 servers, maybe you can try installing AD DS to resolve it? I'm still trying to resolve the two other customers but if anybody can use this information to solve their problem, please let us all know so we can get to the bottom of this.
For me it is Windows Sp2 datacenter edition, all of them are members of domain. One remark is when issue occur when connceting the RDS server without licence services i've nothing in the event logs. I solved the problem by connectigt the new remote desktop server instead of his own license server to another license serve we have running since in another location.
DAMN Microsoft please give us an official reply!! Microsoft support did not offer any further assistance other than to go to the thin client vendor. It sounds like from Alessandro's message that using a server as the licensing server means the additional security check has not required and clients below version 6.
Alessandro, can you confirm the Licensing Server you have used is based on Windows or not r2. Thanks in advance!
I'm a lucky man because i have ten windows CE barcode Reader that are working well since when we had an old windows server then in with switch all the infrastructure on a brand new Windows R2 servers infrastructure In the meanwhile the server was updated to SP1 and everything is working good. So for now we have 1 license server installed on the main office on a Windows R2 SP1 server patched to SP1 after the installation that is working and a second license server installed from a HP CD Windows R2SP1 that won't work with oldest device.
So what i'm thinking is that if I install from a SP1 CD i don't have below compatibility if I upgrade the below compatibility is mantained. The bad news is that if I connect a working Remote desktop server to the "wrong" License server it start not working and i cannot revert this situation even if I disconnect from the license server and connetc to another or even if i remove and reinstall the Remote Desktop Role. It seems that the access to the "wrong" License Server changes some configuration on the terminal server and his behavior.
I used EricWy solution above and it worked. I'm wondering what happens when we add more licenses to the server but I guess I'll cross that bridge when I get there. It would be nice if Microsoft would have participated in researching the solution to their problem. Thanks Eric. I expected a update for this issue. Its a License problem. All new RDP clients can connect. But its hard to update a specific hardware with windows CE 5.
I asked the supplier and the manufactuer. This issue makes us trough back to the windows server instead want to go over to the newer r2 sp1. Also I think the lack of Microsoft's help on this issue is pretty poor, do they realize that businesses rely on simple things like Remote Desktop?
Presuming that it's going to work when I can reboot the server We have two new r2 boxes both setup as independent licensing and RD servers with new licences, peer to peer network. HP WinCE 5. The thin clients happily connect to one server and not the other.
They are set up identically as far as I can figure, both new from scratch. Firewalls off still. Problems with Mac clients connecting to both machines resolve with fix found elsewhere - either or both of new RDP client 2. The solution for us was to disable the NLA. INI file. We added there. If this is the case, it should support NLA. Dell Wyse OS 7. That protocol version does not support NLA. Went through the uninstall, deactivation, reactivation and reboots Your solution nailed it!
I make the process but when I reboot the machine all the registry keys return and the RDP 5. W e had the same problem with older terminals after cloning a R2 rds server and sysprep it. The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because of a security error, the client could not connect to the remote computer.
Verify that you are logged onto the network and then try connecting again". Healthcare and Life Sciences. Internet of Things IoT. Enabling Remote Work. Small and Medium Business. Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
You don't have to do anything else. That's why it's important to deploy the policy first , before installing the clients. Regarding updates, it's important to have the clients point to Microsoft Update not windowas update if you select the check box in fcs policy that allows computers to get updates from MU in case WSUS is unavailable, you are opting-in MU on your clients automatically.
Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access.
0コメント