Terminal Server

Hello there,

This is strange but it looks like since I upgraded my
client PC to SP4, some strange things started happening
(BSOD, sudden shutdown) and at the end I cannot establish
connection with my SBS through TS. It worked flawlessly.
"Client could not connect to Terminal server. The server
may be too busy. Please try again later."

I did not change anything on the server and I assume it
should be OK.

Do you have any clue how to fix this problem?

Thanks,

Grey
Thu Jul 10 06:31:01 CDT 2003

Have you rebooted the server. As in sometimes TS hangs/stops and a reboot
will fire it back up.

--
Grey
SBS ROCKS MVP


www.smallbizserver.com


"Mladen" <mladen@mail.com> wrote in message
news:072c01c34665$e97891a0$a101280a@phx.gbl...
> Hello there,
>
> This is strange but it looks like since I upgraded my
> client PC to SP4, some strange things started happening
> (BSOD, sudden shutdown) and at the end I cannot establish
> connection with my SBS through TS. It worked flawlessly.
> "Client could not connect to Terminal server. The server
> may be too busy. Please try again later."
>
> I did not change anything on the server and I assume it
> should be OK.
>
> Do you have any clue how to fix this problem?
>
> Thanks,
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.493 / Virus Database: 292 - Release Date: 6/25/2003

rayfong
Thu Jul 10 17:24:34 CDT 2003

Can't really say SP4 create the problem, but SP4 did require a reboot and
the reboot may let Exchange to grab 3389 before terminal server.

329155 "The Server May Be Too Busy" Error Message If Terminal Services
http://support.microsoft.com/?id=329155

Ray Fong
Microsoft SBS Product Support

This posting is provided "AS IS" with no warranties, and confers no rights.


>
>Reboot did not help. I fixed that by following Q154596
>HOWTO: Configure RPC Dynamic Port Allocation to Work w/
>Firewall
>
>After that it was OK, but still I do not understand why
>SP4 created this problem?
>
>