G
Guest
One computer has problems connecting to certain terminal servers. The error
message it gets is "The remote computer diconnected the session because of an
error in the licensing protocol." I've looked through TechNet and none of
the articles and notes help because this is happening to just one Windows XP
Pro. All other computers are fine and all the servers are fine. The error
does not come up with all Terminal Servers. The only common that I have been
able to figure is that the workstation can connect to the Terminal Servers
that have the license server installed together but not the ones that have to
go over the network to another server. This does not matter whether it's on
the same subnet, over a router, behind a properly configured firewall,
through a vpn or straight over the Internet. (Yes I took the time to test it
though not the complete matrix of possibilities). The only change that was
made since it last worked was that the Cisco VPN client had to be upgraded
from version 4.6 to version 4.8 because it seemed to have broken after the
lastest MS critical patch was installed. I have tried uninstalling the vpn
client with no luck.
Anyone have any ideas what might be causing this or how to troubleshoot this?
Thanks.
message it gets is "The remote computer diconnected the session because of an
error in the licensing protocol." I've looked through TechNet and none of
the articles and notes help because this is happening to just one Windows XP
Pro. All other computers are fine and all the servers are fine. The error
does not come up with all Terminal Servers. The only common that I have been
able to figure is that the workstation can connect to the Terminal Servers
that have the license server installed together but not the ones that have to
go over the network to another server. This does not matter whether it's on
the same subnet, over a router, behind a properly configured firewall,
through a vpn or straight over the Internet. (Yes I took the time to test it
though not the complete matrix of possibilities). The only change that was
made since it last worked was that the Cisco VPN client had to be upgraded
from version 4.6 to version 4.8 because it seemed to have broken after the
lastest MS critical patch was installed. I have tried uninstalling the vpn
client with no luck.
Anyone have any ideas what might be causing this or how to troubleshoot this?
Thanks.