Yes, just phone Microsoft Support and ask for the specific hotfix.
If you don't ask any other support questions during the same call,
you will get the hotfix mailed to you without any costs.
But hotfix 823747 seems to address a very specific case. Are you
running Exchange server as well? The KB articles mentions Exchange
as part of the problem.
Otherwise, you might also want to check the TS FAQ at
http://www.microsoft.com/windowsserv...centers/termin
al/terminal_faq.mspx
Under connectivity:
Q. Sometimes when I connect to my terminal server, I see a black
screen. Why does this occur?
A. This typically occurs if there is a device between the client
and the server that is receiving packets but not passing them on.
One way around this problem is to change the MTU size for the
network adapter that is being used as a terminal server connection
to clients.
Ethernet uses a maximum MTU size of 1500. You can start with 500
and then slowly move up until you notice the problem to find the
correct value to set
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?RDIgLSBKb24gQ2FybmV5?=
<(E-Mail Removed)> wrote on 25 apr 2006 in
microsoft.public.win2000.termserv.clients:
> Hi,
>
> Looking for help
>
> I have a customer running Windows 2000 server, i connect to this
> server through a microsoft vpn connection and us mstsc with
> there ip address to connect and remotely administer the server.
> Lately i have tried connecting using this method and am
> presented with a black screen after about 2-3minutes the connect
> is severed with the general error message communication was
> broken blah blah blah.
>
> I found an article on the knowledge base (Article ID : 823747 )
> which describes a similar situation but i don't really
> understand it, has anyone had this same problem and if this
> article fixed the problem could you please explain it to me.
>
> The article recommends a hotfix to solve the problem do i just
> need to give the microsoft support number a call and order the
> hotfix?
>
> Any help on this matter would be greatly appriecated