Hello,
We have had the following setup working fine for about 2 years ..
Head office - SBS Server 2000 and Windows 2000 Server with 5 TS CALS
Remote Office - Windows 2000 Server & ISA server 2000
The remote office server makes a VPN connection over ISA to the head
office ISA server and all the remote Windows 98 users can access their
terminal server desktops on the head office 2000 TS server.
We had a crash on the head office SBS server a few weeks ago, it
wasn't recoverable so we changed the network to look like this ...
Head office - SBS Server 2003, Existing Windows 2000 Server for TS
access and 2 Windows 2003 servers for additional file and printer
sharing and also domain controllers.
Remote office - Windows 2003 Server and ISA Server SP1
Since doing this, the remote windows 98 users cannot log in to the
Windows 2000 Terminal Server. They can ping the server and indeed if
they go to the Windows 2003 server which they have on site, they can
access the Terminal Server from there. However, it times out from
their PC's.
The head office terminal server has this in the event logs ...
Event ID 1004: The terminal server cannot issue a client license.
This occasionally pops up as well
Event ID 50: The RDP protocol component X.224 detected an error in the
protocol stream and has disconnected the client.
Things I've tried doing to rectify
Setting the encryption level on the TS to low
Install a licence server on the SBS2003 server at head office. I can
see the licence server giving out grace licence's to the Windows 98
PC's!
One final thing, every now and again it looks like it may actually log
on to the TS and you see the Remote Desktop bar at the top of the
screen but it then fails with a connection broken message. We can ping
the server fine though from the workstation.
Please help if possible.
Thanks
Jon