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.

Hi,

Is it possible to publish applications if the Remote Desktop Services RDWEB are installed on a stand alone server Windows 2012 Standard?

Hello,

I have a problem with new active directory user accounts on a Server 2016 VM, RDS, Session Host, Connection Broker, Licensing Mgr, joined to an Active Directory domain.  All other existing accounts are set up the same way and work fine.  The new ones give:

Here's how things are set up:

The DemoUser account is a member of the Demo Users security group:

Here's the Demo Users group general tab:

This shows the Demo Users group is a member of the RD Users group:

Everything I've read tells me the user should be able to connect.   Please help!!!

Hi. We have a new WS2016 RDS deployment (VMs on Hyper-V):

 - 2x WS2016 RDGW in NLB

 - 2x RDCB in HA configuration

 - couple RDSH servers

The problem is that in 30-50% of the connection attempts via these gateways, the connection is stuck at the "Configuring remote session" message. The connection is never successfully estabilished when this happens and it is closed without any error couple minutes later. When you try again (or just immediatelly cancel the connection and reconnect), the connection may or may not go through.

When this problem happens, I can see there's single HTTP connection on the RDGW that accepted the connection with 0 bytes transferred in either direction. There are no related errors at this time.

Can anyone help? Btw. this problem also happens when connecting to a different single-host RDS deployment through these gateways.

I suspected the problem might be in the NLB, but removing either of the gateways from the NLB configuration (and from RDS farm) doesn't help, the issue is still there.

Rebooting the gateways helps for a short while (hours), but then the issue is back.

There are some other errors on the gateways, but these don't correlate to the connection attempts (event 210, source terminalservices-gateway: "Http transport: IN channel could not find a corresponding OUT channel" with no other details).

RDP clients are various ... W8.1, W10, Mac...

hello guys,

i'm having this problem only when trying to log into windows 2012 RDS servers(2003,2008 are fine) were space and backslash is added to the front of the UPN.

For example:

I save my UPN david@mydomain.com in my remote desktop connection settings. Then when i try to remote into my RDS windows 2012 servers this what is added in the username field " \david@mydomain.com" without the double quotes and therefore i get the error message "The user name or password is incorrect. Try again.". When i remove the space and backslash i can remote in just fine. I have looked everywhere and no one has been able to bring up solution. Please help!

yes

Can anyone point me in the right direction for documentation on RDS Licensing High Availability feature in 2019?

I started here:

https://docs.microsoft.com/en-us/windows-server/get-started-19/get-started-19

But I'm not having any luck finding information, design considerations, deployment how to's etc.

Hi There

I have a feeling that the issues I’m about to explain are somewhat related but I would like to know if anyone has had the same problems.

We have recently upgraded our 2008 RDS server to Server 2016 running.

The RDS server sits at our main branch and I have VPN's from other branches connecting to the server.

Everything is fine at the other branches except one, I keep getting calls telling me that the Remote Desktop has dropped with the following error.

"A licencing error occured while the client was atempting to connect (Licensing timed out).

Please try connecting to the remote computer again"

I have tried this on Windows 7 and Windows 10. I have also updated the RDS client on the Windows 7 systems.

I have looked on line and there isn't that much on this regarding this problem on Server 2016. If i switch back to my old 2008 Server everything works fine, no connection errors.

It can take a while before users can reconnect. I have checked my VPN's and there are no disruptions with the service, like I said if I connect my 2008 server I get no problems.

The other problem I have is with printing... Damn am I having problems with printing..:(

All my printers use TCP/IP ports and I have never had any problems with Server 2008, but with Server 2016 it can sometimes take up to 3 mins before I get a print. On the odd occasion it will work and i can get a print out within about 15 secs. These are text prints no pictures just text.

On the old server it would print within 2-3 seconds.

When it does decide to print I will always get an error then after about 1 min I will get another error then it will print. The error is just a general 'Error printing on (printer name). The print queue shows the status as printing then as printing-error that eventually it will print.

I’ve tried a few different drivers and I can get the printer to print eventually.

Any help would be greatly appreciated.

I have 2 Terminal Servers (TS4 and TS5) both running Remote Desktop Services. However, I can only see the connections on TS4 for both Terminal Servers. On TS5, I cannot see any of the connections.

Here is what I see on TS4

Here is what I see on TS5:

Hi,

Is there a way to restrict Remote Desktop Users from copying executable files to RD Server? FSRM blocks all users.

Thanks.

Hello,

we are running a RemoteApp environment using RDS Gateway running on Windows Server 2016 Standard. Our problem is that clients running on Windows 10 are not able to connect to RemoteApp at all. After entering the credentials, the login window pops up again after 1 second (it's an endless loop). 

An entry with the Server IP to our internal server name was created in the hosts file. Pinging it also works fine.

RDP Client logs show the following (unfortunately in German):

Clients running on Mac OS are able to connect just fine.

Thanks in advance for any help!

I am using windows 2008 R2..

RDP role installed..  I can connect with more than 10 users.

but Roaming user can't use printer.

This has been going on for years and I've just accepted it, but it seems too weird and makes auditing difficult.  We have 5 load-balanced terminal servers and 2 connection brokers.  Once a week, I audit all 7 servers for event ID 4625.  The week that Windows Updates have been staged through our WSUS, I get literally hundreds of 4625 Events on the Connection Brokers.  The events pop up 8 at a time within 1 second.  The terminal servers themselves don't have any issues.

This is an event from one of the Connection Brokers:

An account failed to log on.

Subject:
	Security ID:		NULL SID
	Account Name:		-
	Account Domain:		-
	Logon ID:		0x0

Logon Type:			3

Account For Which Logon Failed:
	Security ID:		NULL SID
	Account Name:		<CNBRKR COMPUTER NAME>
	Account Domain:		<DOMAIN>

Failure Information:
	Failure Reason:		Unknown user name or bad password.
	Status:			0xc000006d
	Sub Status:		0xc0000064

Process Information:
	Caller Process ID:	0x0
	Caller Process Name:	-

Network Information:
	Workstation Name:	<CNBRKR COMPUTER NAME>
	Source Network Address:	fe80::39b9:306b:5224:fd9
	Source Port:		62951

Detailed Authentication Information:
	Logon Process:		NtLmSsp 
	Authentication Package:	NTLM
	Transited Services:	-
	Package Name (NTLM only):	-
	Key Length:		0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
	- Transited services indicate which intermediate services have participated in this logon request.
	- Package name indicates which sub-protocol was used among the NTLM protocols.
	- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

After the Windows Updates are installed, the 4625 events go back to normal where my users can't remember their passwords.

Any ideas?

Hello,

In our environment, we have an application published RemoteApps on the RDWeb page. This RemoteApp from the application there is a print button which will call a Batch file on the Terminal server.

Example:  User with a receipt printer attached to his workstation. goes the RDWeb and logins. Launches the RemoteApp then the user wants to print which will trigger batch file in the background and it should print on the local receipt printer. But this scenario is not working.

However, the same goes to RDWeb and logins. Goes to connect to Remote PC gives the Session host server name and then gets the RDP session and from there the User launches the same Application and then select the Print option which also calls the Batch file which is printing on the local receipt printer.

FYI all the plug and play devices, ports and others pnp devices are allowed. Please suggest if I have to make any changes in the Published app

I don't understand why it is not printing from the Published app and it is working from full RDP session

These are the settings given for Collection

On RemoteApp Parameters. Do I need to change anything

Pls suggest me any ideas



Shekar

Hello, we have 25 Windows 2008 R2 servers not joined to a domain, they are in workgroup, but they can communicate with each other over the network. We use Remote Desktop Licenses - per User, and actually we installed licenses on each server. Some server needs more licenses, some less, so we'd like to optimize Licenses use by installing the Remote Desktop Licensing Server Service on a centralized server, and setting each Windows 2008 R2 server to point to that as Licensing Server.

Do you know if this is possible, since they are in workgroup? Or is there another way?

Thank you

Valeria

Hi,

Anybody can help me to find a backup system for this server OS please....

Windows Server@Standard

Copyright (c) 2007 Microsoft Corporation. All rights reseved.

Service Pack 2

I googled a famous backup software but cannot see a compatible for this server OS version.

I need to have an automatic running scheduled backup for the data on server.

Thanks.

Hi,

we host multiple clients with highly standardized environments but on the servers of a single customer i have the following behaviour:

• a User logs on to the RDS Server
• the User Profile Service (profsvc) writes the assigned FTAs (in this case protocols) into the user registry (observed in procmon)
• the User gets promted for which application to use for opening assigned type

The associations xml is right since it works with every other customer. The only FTAs (or protocols) included are http and https.

The values get written to the correct reg key: HKU\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\http(s)\UserChoice

There ProgID and Hash are also written but it seems like the Hash is wrong.

If i set the default Program in the dialog (OpenWith), another Hash is written and this Hash seems to be correct since opening Hyperlinks works then. But since UsrClass.dat doesn't roam after a logoff the settings are gone.

If I take a hash value that has been set through the OpenWith dialog that is working and replace it with the hash set from profsvc it also works.

I read that the generation of the hash also includes the timestamp of the reg key. If this is true replacing the hash with an older version should not work right?

Since this behaviour only occurs on one of our clients i do not rule out the possibility of customizations made by the customer but i can not find any further clues to pin down the culprit. 

Said Server is a 2012 R2 with latest patches, Citrix VDA 7.6, Citrix UPM 5.5. The issue occurs on all tested clients (Win7, Win10, IGEL ThinClients)

What are other areas i could look or tools i could use to do any further analysis? My traces so far involved monitoring the activity on said registry keys and the mentioned associations.xml in procmon. In both cases only svchost with UserProfileService on the Stack accessed said items.

Thanks in advance!

associations.xml:

<?xml version="1.0" encoding="UTF-8"?><DefaultAssociations><Association ApplicationName="Internet Explorer" ProgId="IE.HTTP" Identifier="http"/><Association ApplicationName="Internet Explorer" ProgId="IE.HTTPS" Identifier="https"/></DefaultAssociations>

Stack of the RegSetValue Operation on the hash on User login:
0	ntoskrnl.exe	RtlEqualUnicodeString + 0x1f00	0xfffff8033d425d80	C:\WINDOWS\system32\ntoskrnl.exe
1	ntoskrnl.exe	SeAssignSecurity + 0x2d77	0xfffff8033d45d5cf	C:\WINDOWS\system32\ntoskrnl.exe
2	ntoskrnl.exe	setjmpex + 0x6523	0xfffff8033d1d51a3	C:\WINDOWS\system32\ntoskrnl.exe
3	ntdll.dll	NtSetValueKey + 0xa	0x7ffaead70d5a	C:\WINDOWS\SYSTEM32\ntdll.dll
4	KERNELBASE.dll	RegCreateKeyExW + 0x187	0x7ffae8161477	C:\WINDOWS\system32\KERNELBASE.dll
5	KERNELBASE.dll	RegSetValueExW + 0x141	0x7ffae8161601	C:\WINDOWS\system32\KERNELBASE.dll
6	SHELL32.dll	OpenRegStream + 0x2daf	0x7ffae97924df	C:\WINDOWS\system32\SHELL32.dll
7	SHELL32.dll	Ordinal714 + 0x32ad	0x7ffae9840f2d	C:\WINDOWS\system32\SHELL32.dll
8	SHELL32.dll	SHGetFolderPathAWorker + 0x74b	0x7ffae98568fb	C:\WINDOWS\system32\SHELL32.dll
9	SHELL32.dll	SHGetFolderPathAWorker + 0xa5c	0x7ffae9856c0c	C:\WINDOWS\system32\SHELL32.dll
10	SHELL32.dll	SHGetFolderPathAWorker + 0x904	0x7ffae9856ab4	C:\WINDOWS\system32\SHELL32.dll
11	SHELL32.dll	SHGetFolderPathAWorker + 0x148a	0x7ffae985763a	C:\WINDOWS\system32\SHELL32.dll
12	SHELL32.dll	SHGetFolderPathAWorker + 0xdde	0x7ffae9856f8e	C:\WINDOWS\system32\SHELL32.dll
13	SHELL32.dll	Ordinal891 + 0x17a36	0x7ffae98c6ae6	C:\WINDOWS\system32\SHELL32.dll
14	profsvc.dll	profsvc.dll + 0x4ad8	0x7ffae59b4ad8	c:\windows\system32\profsvc.dll
15	profsvc.dll	profsvc.dll + 0x499b	0x7ffae59b499b	c:\windows\system32\profsvc.dll
16	profsvc.dll	UserProfileServiceMain + 0xe69	0x7ffae59c2079	c:\windows\system32\profsvc.dll
17	profsvc.dll	UserProfileServiceMain + 0x16f1	0x7ffae59c2901	c:\windows\system32\profsvc.dll
18	profsvc.dll	profsvc.dll + 0x7d3d	0x7ffae59b7d3d	c:\windows\system32\profsvc.dll
19	profsvc.dll	profsvc.dll + 0x68da	0x7ffae59b68da	c:\windows\system32\profsvc.dll
20	ntdll.dll	TpSimpleTryPost + 0x1be	0x7ffaeacf679e	C:\WINDOWS\SYSTEM32\ntdll.dll
21	ntdll.dll	RtlFreeUnicodeString + 0x17ed	0x7ffaead18e8d	C:\WINDOWS\SYSTEM32\ntdll.dll
22	KERNEL32.DLL	BaseThreadInitThunk + 0x22	0x7ffae8c213d2	C:\WINDOWS\system32\KERNEL32.DLL
23	ntdll.dll	RtlUserThreadStart + 0x34	0x7ffaeacf54f4	C:\WINDOWS\SYSTEM32\ntdll.dll

I have a windows server 2012R2, and have 2 local account for remote purpose (account A : with administrator group, account B : not in administrator group)

when remote from a windows 7, everything works fine,

but when remote from a windows 10,

1) only the account B is able to connect

2) the account A fail with the following message : The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contract your system administrator or technical support. 

and in the server event log, it show the following

I had further try to put account B into administrator group, then it show the same error as of account A and fail to remote desktop in windows 10. this is weird that at the same time i could do the remote connection from windows 7, just not in windows 10.

I could not get any clue why things work fine in windows 7 but not in windows 10. Please help, i would like to make windows 10 also can be remote to the server using a admin account. thanks

We have completed RDS deployment and now trying to add RD Gateway role. The wizard fails with no information. Checking the event logs and it says the role was successfully installed, but it is not. Have enabled debug logs and checking RdmsUI-trace.log, it also says the role was successfully installed, but it is not.

According to this article, we should also have an RDMSDeploymentUI.txt file in Windows\Logs, but none has been created (yes registry entry is added and server has been rebooted multiple times).

Have run the wizard several times, including several reboots and get the same every time. When adding the RD Gateway role, the instructions on certificate is exceedingly confusing, conflicting itself. We don't want to use a self-signed certificate - we have a proper certificate, but it's not clear whether we can specify the real certificate or must use a temporary self-signed certificate initially. In any case, I have tried both, specifying the actual public certificate common name we will use (rds.ourdomain.co.uk) as well as the local server name (our-rds.domain.local). Same failure every time.

With zero information on why the wizard says it failed while other parts say it succeeded, but didn't because the role is most definitely not installed, how can we determine what the issue is?

For information, this 2016 server is a member server on a network controlled by an SBS 2011 box, if that has any bearing.

Adam@Regis IT