|
|
| Windows 7 + Royal TS + Terminal Services |
|
|
Hi Hope you can help,
I am receiving this error below when i try to use Royal TS to connect to a terminal services session. This works fine on XP and Vista with 1.5.1 and any of the 1.6 versions including 1.6.8.
I paid for a licence wondering wheter it was a old version issue with Win7 but it has not resolved the issue. Basically i connect to a server with Terminal Services manager in stalled and then use that server to connect to our clients as TS requires you to already be in a remote session to connect to a client.
When this happens it disconnects both the TS session and the server connection.
Running Windows 7 Professional 32bit with 4GB of ram, all Windows updates applied.
Any info i can supply that will help me resolve this issue just reply!
Thanks for any help or advice.
Regards,
Andy
Royal TS Version: 1.6.8.36439
RDP Version: 7
Operating System: Microsoft Windows NT 6.1.7600.0 (Microsoft Windows 7 Professional )
Current Culture: English (United Kingdom)
Monitor Count: 1
Visual Styles: True
Severity: Information
Time Stamp: 23/12/2009 14:01:41
Action: Disconnect
Item ID:
Item Name:
Item Type: Remote Desktop Client
Local User:
Local Host:
Remote User:
Remote Host:
Message: Remote desktop client was disconnected: 3334 - Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.
Details:
|
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Just a quick add to this, i forgot to mention that this doesn't happen as soon as i connect it can take 1-2 seconds up to a 10 seconds before disconnect.
Regards,
Andy |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Hi Andy!
I read your post twice and it's still not 100% clear what you are trying to do, what exactly is failing and where it's working and where not. So let me summarize what I understood.
You want to connect to an existing session, not a new one. A new one is working but an existing one not.
This is working on XP and Vista but not on Win7; you get the 3334 error.
Here a few things to check:
Can you repro this issue on other Win7 clients as well (just to rule out that something with this specific box is going one)?
Is it working when you use the standard mstsc.exe on Win7 where it is not working with Royal TS?
Open up the connection properties of the connection in question and try different authentication level settings and see if this changes something?
cheers,
Stefan Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
| StefanKoell wrote
Hi Andy!
I read your post twice and it's still not 100% clear what you are trying to do, what exactly is failing and where it's working and where not. So let me summarize what I understood.
You want to connect to an existing session, not a new one. A new one is working but an existing one not.
|
I hope this is clearer, if it's not i suppose i could make a screencast or screenshots.
So to connect to a clients Terminal Service Session i need to be within another RDP Session so i would :
Laptop ( Connect to one of our servers to create a RDP session using Royal TS ) --> RDP Session ( I now open Terminal Services Manager and look for the client i want to connect to and select 'Remote Control' --> now in remote session ( Between 2 and 10 seconds both RDP sessions are terminated )
| StefanKoell wrote
This is working on XP and Vista but not on Win7; you get the 3334 error.
|
Yes this is correct
| StefanKoell wrote
Here a few things to check:
Can you repro this issue on other Win7 clients as well (just to rule out that something with this specific box is going one)?
|
I have ran this on 2 seperate laptops with Win7 and had the same issue, one was running the RC and the other Full release same issue.
StefanKoell wrote
Is it working when you use the standard mstsc.exe on Win7 where it is not working with Royal TS?
|
Yes this works fine, sorry i knew i had forgot to add something to my post.
Open a remote desktop connection, click connect and do the same as above and connect via TS manager, tested again this morning and no disconnection after 5-10 mins.
StefanKoell wrote
Open up the connection properties of the connection in question and try different authentication level settings and see if this changes something?
|
No changes, still fails.
Is there any way of getting any more Verbose error logging to see what else is happening ?
Regards,
Andy
|
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Hi Andy,
I just tried to repro the issue on my Win7 machine and it seems that it's working fine for me. Here is what I tried:
I created a remote desktop session.
I created a second remote desktop session with Royal TS, where I opened the remote desktop services manager.
Right-clicked on the first session I opened and chose Remote Control.
I was able to remote control the first session after I allowed it for several minutes without any error.
My setup might be different than your, because I haven't much resources to do extensive tests. My setup:
Server: W2K8 R2 English in Terminal Service Admin mode.
Both users I used to test were admins.
Client was Win7 x64, most recent patch level.
What server OS do you have? Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Hi There, I have just upgrade to Win 7 prof and I get exactly the same thing. Using Royal ts from laptop I connect to a windows 2000 terminal server. using tsadmin, when I try to remote control a user, it jsut disconnects me.
I have search the web and seems to be something to do with mstscax.dll, but when I followed the advice from other forums, Royalts says incorrect version and I need to upgrade this file.
Sean |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Hi Sean,
I know that there are issues with the remote control functionality in the ActiveX control - I also informed Microsoft about those issues. It would be helpful if you can share what advice exactly you followed and what exact error message you get (you may investigate the activity log).
cheers,
Stefan Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
When I try to remote control the log shows
"Remote desktop client was disconnected: 3334 - Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again"
I did some testing this morning and I did remote successfully to three users. All my users only have dump terminals, I do have a few different vendors and seems that it only happens to particular brands but not sure what the difference as the specs are the same. Maybe using a different version of RDP.
The Dll file version number i have is 6.1.7600.16385
Advice I found was to copy the dll file from a vista installation. I couldn't find any vista install's so downloaded from web. Found version 6.0.6000.16386. Royalts errored with "you must use version 6 or higher"
When I was working on XP I could remote control to ALL of my thin clients, so something has changed in windows 7 version.
When I use Windows 7 - mstsc it does the same thing, so problem does not lie with RoyalTS.
Sean
|
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Thanks for the clarification, Sean. Copying those dlls from other OS is very dangerous and can break your machine. Remote desktop is deeply integrated into the OS and uses lot's of the OS infrastructure (security and encryption frameworks) which are very different from each other from OS to OS...
cheers,
Stefan Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Stefan,
Just wondering if you have had any luck from Microsoft soft with this problem ?
Makes it difficult to support staff at the moment.
thanks
sean |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Here is the symptom I often see:
Windows 7 Business x64 edition
Royal TS 1.6.8.36439
9/10 times things work fine, but I do get the message that says I dont have the right version of rdp client, I close royal ts, reclick on rdp session and it lets me in fine:
http://screencast.com/t/NDBmOTMy |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Very interesting behavior. Can you have a look at the activity log (via the view menu) after you get the message and send me the details? It would also be interesting if you can check the latest beta of Royal TS 1.6.9 from (http://www.code4ward.net/rtsbeta/rtsbeta.zip ). Download and extract the package in some directory, start RTSApp.exe. Before you use the beta, always make a backup of your .rts files!
cheers,
Stefan Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Hi,
Downloaded beta, remote control still failed. Data from log below.
Royal TS Version: 1.6.9.34052
RDP Version: 7
Operating System: Microsoft Windows NT 6.1.7600.0 (Microsoft Windows 7 Professional )
Current Culture: English (Australia)
Monitor Count: 1
Visual Styles: False
Severity: Information
Time Stamp: 6/04/2010 12:00:45 PM
Action: Disconnect
Item ID:
Item Name:
Item Type: Remote Desktop Client
Local User:
Local Host:
Remote User:
Remote Host:
Message: Remote desktop client was disconnected: 3334 - Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.
Details:
I do have another problem but is with Windows 7 but thought I would mention. I have cleared log, and upon running exe I get the following. I cannot do file and exit, each time I have to go to task manager and kill royalts. I am an administrator on both Local computer and domain but still get the below, maybe you have some advice ?
Sean
Activity log configured
Message:
Cannot create event source: Source Royal TS Application already exists on the local computer.
Details:
System.ArgumentException: Source Royal TS Application already exists on the local computer.
at System.Diagnostics.EventLog.CreateEventSource(EventSourceCreationData sourceData)
at System.Diagnostics.EventLog.CreateEventSource(String source, String logName)
at code4ward.RoyalTS.Log.Add(LogEntry logEntry)
Message:
Cannot create event message: Cannot open log for source 'Royal TS Application'. You may not have write access.
Details:
System.InvalidOperationException: Cannot open log for source 'Royal TS Application'. You may not have write access. ---> System.ComponentModel.Win32Exception: The interface is unknown
--- End of inner exception stack trace ---
at System.Diagnostics.EventLog.OpenForWrite(String currentMachineName)
at System.Diagnostics.EventLog.InternalWriteEvent(UInt32 eventID, UInt16 category, EventLogEntryType type, String[] strings, Byte[] rawData, String currentMachineName)
at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte[] rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID)
at code4ward.RoyalTS.Log.Add(LogEntry logEntry)
Message:
Application initialized.
Details:
|
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
Hi Sean,
I already informed MS about that issue. Haven't heard anything yet.
Regarding your other issue:
In most cases one or more configuration files are corrupt. That may happen when you install Windows Updates and reboot your machine while Royal TS is running.
Try to delete the configuration files of Royal TS (it's recommended to backup the old files first).
Search for the following files in your user profile and rename/delete them:
code4ward.RoyalTS.ApplicationSettingsData.xml
code4ward.RoyalTS.RTSConnection.xml
code4ward.RoyalTS.TaskSettingsData.xml
cheers,
Stefan Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
I pinged them several times about that and haven't heard anything yet. I strongly suggest, that anyone experiencing problems in that area go to the Terminal Services Team Blog (http://blogs.msdn.com/rds/), they have an email link on the right allowing you to leave a note for the team. The more people complaining the better the chance that we get heard.
cheers,
Stefan Join Royal TS on Facebook |
|
|
|
 |  |
|
|
| Re: Windows 7 + Royal TS + Terminal Services |
|
|
We have this problem to. But... On XP machine's.
We found out this is a bug in the latest RDP client versions.
The session disconnects when you use the new RDP client (v 6.1.7600 protocol 7.0) to connect to sessions using an older protocol. ( <5.1) |
|
|
|