windows server 2008 r2 remote desktop issue with roaming clients
- by Patrick D'Haese
I have the following situation : a Dell windows server 2008 R2 computer, with remote desktop services installed. I have installed a java application making use of a PostgreSql database, and made this application available for clients using RDP. Clients are standard Win XP pc's and Psion Neo handheld devices running Windows CE 5 Pro.
The application works fine for clients on standard XP pc's connected directly via cat 5E Ethernet cable to a Dell Powerconnect 2816 switch. The Psion Neo clients connect wireless to the network via Motorola AP6532 access points. These access points are connected via a POE adapter to the same switch as the XP pc's. The Psion devices can connect without any problem and very quickly to the server and to the application using RDP. So far, so good.
When the Psion devices move around in the warehouse, and they roam from one access point to the other, the RDP session on the client freezes for approx 1 minute, and then it automatically resumes the session. This freezing is very annoying for the users.
Can anyone help in solving this issue?
Update (August 9) :
After re-installing the access points we have a working situation, but only when connecting to the RDP host :
* via a Win Xp SP3 laptop
* via a Symbol MC9190 Win CE 6 mobile device
When roaming we notice a small hick-up less then 1 second, what is very acceptable.
With the Psion NEO it's still not working, when roaming the screen freezes from 2 to 30 seconds.
The RDP client on the win xp sp3 laptop and the symbol mc9190 is version 6.0.
The RDP client on the neo is version 5.2.
I have changed the security layer on the RDP host to RDP security layer (based on forums on the internet), because older RDP clients seem to have issues with the RDP 7.1 protocol on the Win server 2088 R2.
Psion adviced us to do some network logging activity on the different devices.
We made this logging via wireshark, and based on this the conclusion of Psion is that the server fails in handling tcp-requests.
Can anyone give me a second opinion by analysing the wireshark loggings.
Thanks in advance.
Regards
Patrick
