asked on

Terminal Services - Disconnected when Remote Controlling

I have two Windows Server 2008 R2 Datacenter Edition with Terminal Services Role installed. Both are using the same GPO. On only one of the servers, when I open tsadmin.msc and try to remote control a user’s session the users session is immediately disconnected. I have tested using Windows 7 and XP with the same result. The Windows 7 client Network level authentication is supported and on the XP machine it isn't. I see in the event view the application popup where I am requesting control. The only other log entry that I can see would be in the security log. Any ideas?

The Windows Filtering Platform has blocked a bind to a local port.

Application Information:
	Process ID:		492
	Application Name:	\device\harddiskvolume1\windows\system32\svchost.exe

Network Information:
	Source Address:		0.0.0.0
	Source Port:		59965
	Protocol:		17

Filter Information:
	Filter Run-Time ID:	0
	Layer Name:		Resource Assignment
	Layer Run-Time ID:	36

Open in new window

rgautier

Does the machine have a local firewall policy that the other machine does not? Try disabling Windows Firewall on the target machine and trying again - that will help narrow it down.

DowntownIT

ASKER

Group policy is setting all three of the firewall profiles of the TS to off. As for both clients, the firewall is disabled. I am able to remote control using our other TS.

rgautier

Has someone enable IP Filtering (not part of the firewall product) under the network card on that machine?

DowntownIT

ASKER

Where would I check that?

rgautier

If you're not using IPSec or Windows Firewall, disable the BFE Service under Service Manager - see if this resolves the issue. You can disable it later if you do decide to actually do filtering - but it looks like this is a known bug that others have had issues with.

DowntownIT

ASKER

The security log error is gone but problem remains.

rgautier

Interesting - so the error message isn't necessarily linked to your problem - but is just indicative of the errors that others are seeing (reference link: http://social.msdn.microsoft.com/Forums/en/wfp/thread/774026e6-a771-418a-b531-22183ef399f8 ) with respect to the IP Filtering not configuring correctly during install..

To play it safe, I'd re-enable BFE (as I'm unsure what else it may affect in your environment) - and if I can think of any other suggestions, I'll try to post them...

rgautier

Also - in terminal services configuration manager - check the option 'Restrict each user to a single session' and make sure it's not set to 'yes'?

rgautier

Also - please read this article, which MAY be related to your issue:
http://social.technet.microsoft.com/Forums/en/winserverTS/thread/87fc497a-27fd-4a76-ab59-ea5fe01c9091

If it is not, please identify the differences in your situation - and/or try the possible fixes identified.

DowntownIT

ASKER

check the option 'Restrict each user to a single session' and make sure it's not set to 'yes'
on both TS's it is set to yes, I changed it on the TS that isn't able to remote control with the same result. I will look through that link now

Thanks

DowntownIT

ASKER

I tried this with no luck

Windows Server 2008 R2

1. Logon to the Remote Desktop Services Session Host computer as an administrator
2. Start--Run gpedit.msc
3. In the left pane, under Computer Configuration, navigate to following:

Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment

4. In the right pane, double-click on Set compression algorithm for RDP data
5. Select Enabled, and choose Balances memory and network bandwidth
6. Click OK to save the change

rgautier

I'm sorry, I don't have any other suggestions for you at the moment.

ASKER CERTIFIED SOLUTION

brent_caskey

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer