• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

Windows 7 machine RDP/RemoteApp disconnects from Server after 3 seconds.....

B

Brad-Man

Member
Joined
Feb 15, 2013
Posts
18
I have several Servers set up to run an application for remote users to RemoteApp into.

I have 3 machines that once logged in and connected, the app starts running and then the session is disconnected.

This happens no matter what Server the particular Win 7 machine tries to connect to.

There are PLENTY OF USER CALS available.

It is not a user login problem, because the app starts and I can log in as that user from other machines w/no problem using the same RemoteApp file.

From that machine I try to log in to any of the servers via RDP using my credentials and the session starts up and then disconnects.

The only error message is that the session is disconnecting and Microssoft will try and contact if they can figure out why...or words to that effect.

So it appears to be an issue with a particular machine - although there are actually 3 machines having this issue.

Can anyone point me in the right direction as to what is happening?

Thanks,

Brad
 
More information for this situation:

The Servers are all 2012.

It makes no difference if the machines that won't connect use remoteapp or remote desktop.

The users have licenses assigned to them.

In looking through the RemoteDesktopServices - RdpCoreTS event log on one server I see a series of event ids at the time that one of the users having the issue created.

The next to last event id was 132 - A channel XPSRD has been connected between the server and the client using transport tunnel: 0. @ 11:00:44 AM
The next entry in this log is event id - 102 - The server has terminated main RDP connection with the client. @ 11:07:01 AM

Looking is the TerminalServices - RemoteConnectionManager event log I see the following:

event id 1149 - Remote Desktop Services: User authentication succeeded: @ 11:06:21 AM

Then there are 3 event id 1152 entries - Failed to create KVP sessions string. Error Code 0x8007007A @ 11:06:23 AM, 11:06:25 AM, 11:07:01 AM

I find these last strange as he has an assigned license and I have followed all instructions about making sure that the licencing server is set up with and in the proper groups.
 
All updates have been applied to both computers and still have the problem with them.

The user can go to a computer that another person has that can use RemoteApp from and log onto it as themselves and use RemoteApp with no problems, so this appears to be an individual machine issue and not a lilcensing/server issue.
 
Problem resolved, no thanks to Microsoft or gurus.

Old entries for nonexistent printers/print server causing the problem.

I logegd onto one of the computers as myself and had no issues using remoteapp.

I then logged on as the user having a problem and created a new RDP connection and did NOT redirect printers and no issues.

Went into registry and got rid of all invalid entries and good to go.
 
Brad-Man said:
Problem resolved, no thanks to Microsoft or gurus.

Old entries for nonexistent printers/print server causing the problem.

I logegd onto one of the computers as myself and had no issues using remoteapp.

I then logged on as the user having a problem and created a new RDP connection and did NOT redirect printers and no issues.

Went into registry and got rid of all invalid entries and good to go.
Click to expand...

Were the old printer entries on the client side or terminal server?

having same issue and I see the same entries in the logs. just before the connection breaks I see...

1. The network characteristics detection function has been disabled because of Client not supported..
2. Failed to create KVP sessions string. Error Code 0x8007007A
3.
Remote Desktop Services: Session has been disconnected:
User: domain\username
Session ID: 14
Source Network Address:
 
The old (usually redirected) printer entries are on the terminal server in that user's registry.
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
 
zcomputerwiz said:
The old (usually redirected) printer entries are on the terminal server in that user's registry.
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
Click to expand...

Thanks. I ended up running TCPView on the terminal server, saw that the spool service was sending a syn_sent to an old printer IP on the network. After removing the printer from my profile (where it was) the connection attempt did not go away. I changed the address for that printer port to the right one and restarted the print spooler. seems to have stop the syn_sent connection. Hope this fixes the RDP disconnects. :banghead:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top