Remote Control on Terminal Service session

-

dear support,
when i'm using terminal service remote control feature, i'm disconnected error message: "

because of protocol error, session disconnected. please try connecting remote computer again."

my context:
 - 2 windows 2003 severs tse
 - 1 windows 7 client rdp 6.1 client => administrator
 - wyse clients lastest forwares versions => users

when administrator take control of sessions (terminal server management console on windows 2003 server), error message appears.
if i'm using rdp 6.0 client, connexion ok.

how can take connexion or debug it?

thanks helping
jean-luc chandezon [mct]

hi kudrat, hi lionel,

and thank helping.

i've seen thant have not reply... apologize..

i've updated wyse clients, , problem solved. have not find explanations issue, works...

many thanks,

jean-luc chandezon [mct]


Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

Generating Event ID 91, 44 with CA (In Event Viewer with source as Certsvc)

-
hi we in process of migrating win 2003 ad win2008 r2. when noticed logs found many errors , warning alerts ca below --could not connect active directory. certificate services retry when processing requires active directory access. (event id 91)----certificate services sagia ca can not open certificate store @ cn=ntauthcertificates,cn=public key services,cn=services in active directory's configuration container. (event id 94, warning)--                                                                                            ...
Read more

Group policy default policy cannot be edited because network name not found

-
hey everyone, i have been having issues on , off domain. pdc crashed (the domain controller). started old server , made domain controller , forced roles over. repaired pdc , elevated back. although appeared work found cannot rid of other dc because pdc can no longer contact domain things group policy or else. start secondary , domain magically reachable. although while secondary down can ping domain , replies ip of pdc appears pdc has no control on anything. questions following. 1. gpos created before crash no longer work. rebuilt sysvol , default problem can't edit default domain policy. don't believe having replication problems new repairing domains setting them , maintaining them of education came from.  2. if pdc gpo management console can't access gpos can secondary not have installed? 3. why domain unreachable if no dcs online when shutdown secondary. thanks in advance , try edit dc diag log right there on fails want narrow of out guys concentrate on...
Read more

Problem when changing update source

-
hi all, we use win server 2008 r2 enterprise , wsus 3.2. until last friday, downoloading updates microsoft's website. had change the source wsus server in our headquarters (not being replica server). started problem: our product , classification changed, downloading lot of updates hadn't ever downloaded. now, when try modify update soure (to microsoft's web site again) set option console falls down - database error - , copying error clipboard, have message bellow: the wsus administration console unable connect wsus server database.     verify sql server running on wsus server. if problem persists, try restarting sql.     system.data.sqlclient.sqlexception -- maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32). info:spsetconfiguration - synctomu or upstreamservername config value changed - no reset source .net sqlclient data provider stack trace:    @ microsoft.updateservices.ui.admi...
Read more