because of a protocol error, your session will be disconnected.
Hi everyone
I am in the process of discontinuing our current physical terminal server running Server 2003 SP2 and moving this system into our virtual Hyper-V environment.
The virtual box is already set up, all updates are applied. I am using the same operating system with all updates applied.
I am using the same WYSE terminal to connect to both servers via RDP. WYSE, virtual and physical servers all reside on the same subnet.
CHALLENGE:
When connected to the virtual terminal server from WYSE terminals, my session disconnects after a short while with the following message:
"Because of a protocol error, this session will be disconnected."
Connecting from WYSE to physical TS runs just fine.
Now, I can connect to the virtual TS from my XP PRO computer via RDP just fine with no disconnection problem. Therefore, there is something about WYSE and the new virtual OS set up that it doesn't like.
There is quite a bit on the web related to this issue, but some users have Windows 7, some - XP environment. We use a mix of XP Pro and WYSE terminals. So far, I have noticed this issue with WYSE terminals only.
THank you
I am in the process of discontinuing our current physical terminal server running Server 2003 SP2 and moving this system into our virtual Hyper-V environment.
The virtual box is already set up, all updates are applied. I am using the same operating system with all updates applied.
I am using the same WYSE terminal to connect to both servers via RDP. WYSE, virtual and physical servers all reside on the same subnet.
CHALLENGE:
When connected to the virtual terminal server from WYSE terminals, my session disconnects after a short while with the following message:
"Because of a protocol error, this session will be disconnected."
Connecting from WYSE to physical TS runs just fine.
Now, I can connect to the virtual TS from my XP PRO computer via RDP just fine with no disconnection problem. Therefore, there is something about WYSE and the new virtual OS set up that it doesn't like.
There is quite a bit on the web related to this issue, but some users have Windows 7, some - XP environment. We use a mix of XP Pro and WYSE terminals. So far, I have noticed this issue with WYSE terminals only.
THank you
IanTh
have you spoken to wyse tech support?
ASKER
no, I haven't. I still believe that the solution is somewhere within Windows Server 2003 OS. I am using the same WYSE terminal to connect to two machines - one physical and one virtual. Both have the same OS installed from the same CD. However, the physical server was set up some 4-5 years ago by a different gentleman.
This makes me believe, that there may be a setting that has to be turned on or off(or changed) that will fix the issue.
ON THE OTHER HAND, Â since my XP PRO machine with the newest RDP client connects without issues, the problem may as well be with the RDP version used by WYSE...
This makes me believe, that there may be a setting that has to be turned on or off(or changed) that will fix the issue.
ON THE OTHER HAND, Â since my XP PRO machine with the newest RDP client connects without issues, the problem may as well be with the RDP version used by WYSE...
rdp has changed so that could be the problem
ASKER
do you mean RDP on the virtual server?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
RDP v5.5 in coupe with the newest firmware fixed the protocol issue.