Terminal Services Client

We have recently installed a new Server Running SBS 2000
and started using Terminal Services (from a Windows 2000
machine) and Remote Desktop (from 2 XP Pro Machines).

It was working fine, until approximatetly the ending of
the 90 day trial period.

I have activated the Server's Terminal Server Licence and
was told we need to buy the CAL's - which have been
installed.

I am able to get to the Network by VPN - but both TS and
RD come up 'Busy' (originally it came up 'Timed out',
restarted the Server and now it only comes up with Busy!).

After re-speaking to Microsoft, they have confirmed we
don't actually need the CAL licences (but thats a side
issue) - any idea whats gone wrong, as, as far as I can
tell, the only 'thing' that has occured is the expiring
the the trial period (Server in question is a Dual Xeon
2.4, with 2Gb, which never goes above 710Mg in use and
about 5% processor usage, so it isn't busy*)

Thanks

Paul

* - While writing this message, Server has a 1Gb card -
but is running though a 10/100 Switch, so a bottleneck
could be occuring there....but it was working fine
beforehand (so unlikely!).

Javier
Wed Apr 28 20:46:27 CDT 2004

What do you mean that the server comes up "Busy"? Can you post the exact
error?

BTW-> Remote Desktop Connection (client) is the new name for the windows TS
client... so it is basically the same thing. I'm assuming that you are
trying to connect all 3 machines to the Win2k TS box (which is the one you
are having problems with).

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"Paul Howard" <anonymous@discussions.microsoft.com> wrote in message
news:581501c42d36$edb8c650$a301280a@phx.gbl...
>
> We have recently installed a new Server Running SBS 2000
> and started using Terminal Services (from a Windows 2000
> machine) and Remote Desktop (from 2 XP Pro Machines).
>
> It was working fine, until approximatetly the ending of
> the 90 day trial period.
>
> I have activated the Server's Terminal Server Licence and
> was told we need to buy the CAL's - which have been
> installed.
>
> I am able to get to the Network by VPN - but both TS and
> RD come up 'Busy' (originally it came up 'Timed out',
> restarted the Server and now it only comes up with Busy!).
>
> After re-speaking to Microsoft, they have confirmed we
> don't actually need the CAL licences (but thats a side
> issue) - any idea whats gone wrong, as, as far as I can
> tell, the only 'thing' that has occured is the expiring
> the the trial period (Server in question is a Dual Xeon
> 2.4, with 2Gb, which never goes above 710Mg in use and
> about 5% processor usage, so it isn't busy*)
>
> Thanks
>
> Paul
>
> * - While writing this message, Server has a 1Gb card -
> but is running though a 10/100 Switch, so a bottleneck
> could be occuring there....but it was working fine
> beforehand (so unlikely!).

Mike
Thu Apr 29 03:42:18 CDT 2004

Are you running TS in Application Server mode, or Remote Administration?

Mike

"Paul Howard" <anonymous@discussions.microsoft.com> wrote in message
news:581501c42d36$edb8c650$a301280a@phx.gbl...
>
> We have recently installed a new Server Running SBS 2000
> and started using Terminal Services (from a Windows 2000
> machine) and Remote Desktop (from 2 XP Pro Machines).
>
> It was working fine, until approximatetly the ending of
> the 90 day trial period.
>
> I have activated the Server's Terminal Server Licence and
> was told we need to buy the CAL's - which have been
> installed.
>
> I am able to get to the Network by VPN - but both TS and
> RD come up 'Busy' (originally it came up 'Timed out',
> restarted the Server and now it only comes up with Busy!).
>
> After re-speaking to Microsoft, they have confirmed we
> don't actually need the CAL licences (but thats a side
> issue) - any idea whats gone wrong, as, as far as I can
> tell, the only 'thing' that has occured is the expiring
> the the trial period (Server in question is a Dual Xeon
> 2.4, with 2Gb, which never goes above 710Mg in use and
> about 5% processor usage, so it isn't busy*)
>
> Thanks
>
> Paul
>
> * - While writing this message, Server has a 1Gb card -
> but is running though a 10/100 Switch, so a bottleneck
> could be occuring there....but it was working fine
> beforehand (so unlikely!).