Windows Server 2003 SP2, DC with TS license server (Device CALs)
Windows Server 2003 SP2, Terminal Server (member server)
(TS server recently replaced with new hardware.)
Wyse Terminals with various firmware on different remote sites.
Wyse terminals are connecting to the TS over site-to-site VPNs.
Recently we setup a new remote site with Wyse V30LE (FW 5.88) terminals.
We are able to connect these terminals to the Terminal Server on the first
initial connection, but if we log off and try to log back in,
we are unable to do so. It basicly says it can’t establish a connection. (Connection IS ok though, ping works etc.)
Nothing is logged in event viewer on the Terminal Server regarding this issue.
On the license server, we see that the device is issued a license.
To be able to log in again, we have to manually delete the TS CAL on the Wyse Terminal.
Has anyone experienced this? Is there are workaround without having to delete the TS CAL all the time?
I have to add, the strange thing is, if we bring a problematic Wyse Terminal to another remote site, the terminal connects ok every time! This would you make think there is a problem with the VPN connection or a firewall issue, but wouldn’t this affect the first initial login as well, making it not work? This also contratics that there might be a problem on the Wyse Terminal itself, since it works on another site.
We have also tested with WXPPROSP3 clients connecting with RDP6, they connect fine all the time.