Windows Server 2003R2. Terminal Services is installed and started. Remote Desktop is Enabled. In the Terminal Services Manager session window, RDP-TCP is shown as being in a listening state. But when I run netstat -a, port 3389 does not show up. RD client cannot connect. Telnet or ssh to that port does not connect.

TCP is working fine: I can use logmein to view the server; I can VPN to the server, I can look at SMB shares once the VPN is up. No TCP filtering is active. The Windows Firewall is not active.

How can I get port 3389 going and be able to RDP in?

The registry is still showing port 3389 as the listening port.

I have removed and re-created the RDP-tcp port without any trouble and without success. The properties are set on defaults.

Remote Desktop devices in the device manager show as operating fine.

It used to work fine and just recently (sometime in January) it stopped working. As far as I know, no new software was installed at that time.

I have reviewed a bunch of stuff found in Google but none of it seems to help, so far.

I have three  groups of users, who access RDS Farm.

Group 1 = No printers & and no printers redirection

Group 2 = Only default printer redirection – Allow  

Group 3 = All redirected printers – Allow  

Is it possible, to tis implemented on  same RDS Server “farm”.

Hello everybody,

at a customer's site, there are several 2008 R2 terminal servers running. More often than we like ;-) the following symptoms occur:

• At RDP logon, users get the error message that the group policy service could not logon, and access denied. This leads to the abortion of the logon process.
• After that, the NTUSER.DAT of the roaming profiles is only 256 KB in size (usually, the NTUSER.DAT there is about 2 MB). If we mount such a small NTUSER.DAT, we see just a few keys.
• In the event log, there are entries that the class registry cannot be loaded.

NTUSER.DAT is already excluded from any anti-virus software. Does anybody have a clue about what happens there, or a tip how to diagnose it? Thanks in advance.

Best Regards, Stefan Falk

Ok so problem is there is a 2003 windows server in my office. Any computer phone etc. can connect to it via Remote desktop if they are in the LAN network. I have port forwarded 3389 , disabled firewalls , there is no antivirus software on the server.

BUT I cannon log in over WAN. Heres the problem.

I type in the WAN ip I connect with credentials.

This is what i get:

Connecting...

Negotiating credentials...

Then it just suddenly force closes.

Also tried from a Windows 8 PC , when trying to connect it INSTANTLY throws me an error saying:

This computer cant connect to the remote computer. If the problem continues contact etc..

No matter where i try , a pc , a laptop , a phone , a tablet it just force closes. I can see that the devices are able to see the server and are trying to connect , but the connection just force closes for no reason and no error is shown. Also I dont see anything in the event viewer on the server. The credentials are correct also. And the port is forwarded correctly.

Where could the problem be?

We have setup a Server 2012 R2 RDS deployment with remote-site RD Host Servers all pulling CALs from a central RD License Server. I am able to RDP five sessions into the first RD Session Host Server OK, and the RD License Diagnoser says all is well with the connection to the license server. However I am not seeing any licenses being issued by the central License Server for those five test users, even after a Refresh. The five test users are local to the RD Session Host Server, and not in AD. Do local accounts not show up in the License Server's RD Licensing Manager screen?  Do they not require the RD Session Host to 'pull' CALs from the License Server?  I am thinking I should be seeing the licenses being distributed to the five users and am concerned that I do not.

License Server 2012 R2 - Per User CALs - Joined to Active Directory

RD Host Server #1 with the five RDP sessions is 2012 R2 - Joined to Active Directory

Thanks in advance for any insights! 

I am running Windows 8.1 on both computers. The computer that I am running RDP from is a member of a Domain. The remote computer is a stand alone computer and I use my Microsoft account to connect to it locally (@Hotmail.com). My account password has not expired on either my Microsoft account or my Domain account. My Domain computer is also connected to my Microsoft account.

When I try to connect to the computer that is not part of the domain, I get the error:

This user account's password has expired. The password must change in order to logon.
Please update the password or contact your system administrator or technical support.

Any suggestions would be appreciated.

Luis

Lucho1970

Hi all,

Newbie question I'm afraid....

I have an application that I wish to host on a Server running 2012r2 with RDS and run on either a thin client or a touchscreen device running a thin client.

I only wish to run this one application and so my question is this:

Can I create a remoteapp and have the thin client run that without any desktop or do I have to use a virtual desktop

and autorun the application?

Any recommendations appreciated,

Thanks

Rich

High Guys,

i am trying to implement a Server 2012 Deployment with internal and external Access. I have Installed 2 Connection Brokers in HA Mode. One internal Web Interface and one external Interface with RD Gateway.

Internal Connection has no issues. Everything is running fine. But if i try to Access a Session Host from the Internet, i a get a Warning that the Identity of the Remote Computer could not be checked. What i found out is, that the RD Session Hosts use a self signed Certificate, witch could not be checked by Clients.. I can understand, that a Workgroup PC could not check. So i tryed to use Certificates from our internal CA. I installed the Root CA Cert in the Clients trusted root certification Authority store. And after installing the Certs on the RD Session Host i get the Message, that a Certificate revocation check could no be performed. This is shurly true, because i don´t publish revocation Information. The Cert fron the CA containes LDAP revocation Information, but the LDAP query can not be performed from the Internet. So i tried to remove all revocation Information from the Cert, but i had no success with that. I still get the Warining that a revoscation check is ot possible. 

So my question is, is it possible to use a internal CA for the Session Host Server certificates without any Revocation Information ? this would be my preffered solution. If this is not possible, can i use a Certificate with HTTP Only CDP Information, or do i have to implement OSCP ?

Thanks for your Feedback

Reiner

We're having some intermittent issues with our NAV RemoteApp client not opening correctly.  The page doesn't fully render and the window cannot be moved around the screen, the only solution is to end the mstsc process.  It looks like this:

I've found that this often happens if the user is listed as "disconnected" Under Server manager > Remote Desktop Service > Connections > QuickSessionCollection 

If I log the user off, they can launch the RemoteApp a 2nd time no problem.  As a workaround I created a GPO that immediately logs off a disconnected session.  This has resolved 90% of the occurrences for this problem but does still occasionally happen.

Network doesn't seem to be the cause as it happens on the local Gb LAN just as frequently as our VPN users and no packet loss is occuring between client and server.

Any suggestions?  Cheers!

Hi,

is there any chance to run Azure or some similar Microsoft RMD from Mac, or any other device? The thing is that in my work I use Windows computer, iPad and Android smartphone. I would like to have one constant RMD for all these systems. Is that even possible?

If I want to deploy a single 2012r2 rds as a session host on a lan do I need the gateway and brooker roles? I.e can't I just get the clients to connect directly to the RDS server?

Also Can I install the licensing server on a domain controller? & If so how can I get the DC to show up in the deployment wizard?

I am having issues running the cmdlet provided by Microsoft and I am unable to change the external FQDN so it matches my wild certificate.

https://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80

I am running a single server  environment. It used to be so easy to redirect on Windows 2008 Server but I can't figure it out what I am doing wrong on this new server.

I appreciate all of your help

We have one terminal server with Win Server 2012 R2, and one Linux file server. The Linux file server is also the Domain Controller.

The Windows server should be running terminal services for the business programs which need a Windows platform. We are continuously getting the following error message: "Remote Desktop Session Host server is within its grace period, but the RD Session Host server has not been configured with any license server".

When I try in the RD Licensing Diagnoser to connect to Remote Desktop Session Host Server, it shows the above error message.

The Windows server RD Licensing Manager has 20 Licenses installed, but shows as never issued.

The error message suggested resolution says "Configure a license server for the Remote Desktop Session Host server. If you have an existing license server, specify that license server for the RD Session Host server. Otherwise, install RD Licensing on a computer on your network and Configure RD Session Host server to use it". When I try to specify a Remote Desktop Session Host server by connecting to the Windows server, again the above message shows in the RD Licensing Diagnoser: "Configure a license server... to use it".

In the Server Manager program, when I attempt to Add Roles or Features, I get to Deployment Type, and it shows the RD Connection Broker to be the apparently correct server. I select 'Standard Deployment' and click Next. Error message shows: "Could not retrieve the deployment information from the RD Connection Broker server XXXX".

Please advise.

I have an in-house .NET application that have these symptoms.

1. When userA logs in from remote desktop and run the application, the application handles count keeps increasing (as seen in Performance monitor). When userA disconnects, the handle count stays as where it was, no longer increasing but also not decreasing.

2. When another user, UserB logs in from remote desktop session on the same machine where userA remote desktop session is running (with the application still running) but userA session already disconnected, the handle count of that application is not affected (no increase, no decrease).

3. When UserA logging again, or reconnect back to his session again, the handle count again start to increase further.

So, in summary whoever logs in and start that application as long as he is still logged in or disconnected but session still active, the application will keeps increasing handle count.

In Process Explorer, I am still multiple instants of "Desktop" and "\Default" as handle type and name respectively.

Based on these symptoms, can anyone suggest how I can go about to troubleshoot what is wrong?

Valuable skills are not learned, learned skills aren't valuable.

Hi all

I have a clusterd instance for HA connection Broker on a different port than 1433. My port is 1438. How can i specify in the string connection the different port? It's Possible?

Can do somelike this?

DRIVER=SQL Server Native Client 11.0;SERVER=SqlName:1438;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=SQL12GP

Thanks!

Hello

I configured3Servers:

-BROKER(RDGateway,RDLicensing,RDWeb Access,RDConnectionBroker)
-APP01(RDSession Host)
-APP02(RDSession Host)
I'm having problems opening the RemoteApps externallyon RDWebURL, but I navigatesuccessfullyon the site.

I can work and access applications internally.
I already open ports 80,443,445,3389,3391in licensing Remote Server Firewall (WindowsServer 2012R2).

Externally, I access without problemsRDWeb URL but when I open an application is not showing or execute anything(tested on Internet Explorer andGoogle Chrome).

The certificate also has no problem, I think.

Thank you.

Hello Team and thank you for all the efforts that you constantly make to keep this forum and related blogs updated and useful. I've learne a lot already and continue to enjoy your postings.

After reading numerous (and I mean Numerous) technet articles, blogs and forum posts about RDS, there are still a few questions remaining for me, which I hope you guys can shed a light on them:

1.I have a 2012R2 Virtualization host with GPU. I have installed Win 7 Enterprise SP1 with KB2592687 and all the prerequisits of KB2830477 , including the patch itself on the VM; and have added RemoteFX 3D adapter to the VM. I have enabled both transports in VMs group policy as well.

I have installed the Win7 Pro SP1 with all the aformentioned KBs as the client so I have full RDP8.1 support on my client side as well.

the problem is, that now I am able to rdp into the vm ONLY IF I manually set my experience setting on RDP client to "LAN 10Mbit". if I choose "automatic" or anything else besides that setting, the connection just drops silently without any errors being thrown. it will show the connection setting up to "securing remote session..." phase and bam! knocks out.

based on the forum posts that I'll paste at the end, it seems that it is something on win7, and win8 vms do not have this problem. I just wanted to confirm that as I could not find any official document stating this behaviour.

2.in case the above question is indeed a win 7 issue, so how much is the extent of RDP 8.0 support on windows 7? I am under the impression that by adding support for RDP 8.0 on widnows 7, you guys have FULL BLOWN support of RDP 8.0 on it INCLUDING automatic network speed detection, adaptive WAN and LAN network detection and optimization, RemoteFX over UDP connections and so forth. but the above issue , if by design and not by a bug, shows that none of those enhancements are available in windows 7 even with RDP8.0 installed.

3(which might be related to 2). is setting the client experience to "LAN 10mbit" the ONLY way of having remotefx kicking in in windows 7?

before installing the RDP 8 on the win 7 VM the VM was actually able to fulfill any experience setting including "automatic network detection" but per articles below , no logs of RemoteFX was shown on the VM but rather RDP graphics module were there UNLESS you set the client manually to LAN 10; in which case you'd see RemoteFX kicking in.again , after installing RDP 8 on win7VM, all the other modes ceased to work but LAN 10 so instead of this setting being "optional" now it is "mandatory" if you want to RDP into that VM.

4.does having a GPU in a win 2012r2 SESSION HOST make any difference for enabling RemoteFX for RDPing into that host? I've read contradicting articles on how Session Hosts will or will not use the GPU.

5.will dxdiag on a session host detect and report DirectX features of RemoteFX as dxdiag on a VM with RemoteFX will? if not then how can I verify that RemoteFX is working (besides the log entries of course) and actually doing anything usefull on my session host? I could not see any noticeable imporvements in the youtube videos streamed from the remote host, nor could see dxdiag being any different before and after RemoteFX getting enabled on my session host.

I very much prefer to have my CAD application installed on a session host rather than VMs on virtualization hosts, but I don't know if that would work if DirectX features are not reported to the application while using it remotely; or even I will get any improvement in general by adding a GPU to session host. (I've already enabled the "use default hardware for remotefx" group policy and I need a mean to verify that too).

6.reverting to win7 and 2008r2, the technet articles below tell me to look for event ID 2 to verify RemoteFX being in action. but it seems that there won't be any event ID 2s anymore after you upgrade to DTLS and RDP 8.0. is that the case? if it is indeed, then the technet articles should be updated as well. also it should be noted that which event IDs to look for from that point on to verify Remote FX. also the same thing for event ID 1000 or 1001 for session hosts.

I really appreciate if you answer me on this issues. I believe a new blog entry with explicit answers to these question will benefit quite a few people as well. below are the links and the blog entrie and technet articles I refered to in my questions.

Regards

Sassan

https://social.technet.microsoft.com/Forums/windowsserver/en-US/d38014b2-256d-4d36-8067-9a7a7a79dacf/client-cannot-connect-to-vm-when-remotefx-enabled?forum=winserverTS

https://social.technet.microsoft.com/Forums/windowsserver/en-US/51476a11-4961-40d9-96a1-a24ae0ae58b6/possible-bug-remote-desktop-rejects-nonremotefx-clients?forum=winserverTS

http://blogs.msdn.com/b/rds/archive/2012/10/09/remote-desktop-protocol-8-0-update-for-windows-7-sp1-enabling-a-great-wan-user-experience-for-windows-7-sp1-virtual-desktops.aspx

http://social.technet.microsoft.com/wiki/contents/articles/16652.remotefx-vgpu-setup-and-configuration-guide-for-windows-server-2012.aspx

http://technet.microsoft.com/en-us/library/ff817587

http://technet.microsoft.com/en-us/library/ff817580

http://support.microsoft.com/kb/2863663

Same issue as here but supplied bandaid BS not working:

http://social.technet.microsoft.com/Forums/en-US/472f249a-e441-4b3d-9735-820647b9fab5/folder-shortcuts-are-not-included-in-start-screen-layout-gpo-rds-2012-r2?referrer=http%3a%2f%2fsocial.technet.microsoft.com%2fForums%2fen-US%2f472f249a-e441-4b3d-9735-820647b9fab5%2ffolder-shortcuts-are-not-included-in-start-screen-layout-gpo-rds-2012-r2%3fforum%3dwinserverTS&prof=required

We export a start screen as XML that includes a folder shortcut. On importing it the folder shortcuts are not present (but are in the xml).

We have tried copying the shortcut file into the all users start as found in the linked thread. This doesn't work.

This is a bug and needs an immediate fix/work around from Microsoft. You made us go buy Enterprise for this sole reason, you better make this work.