Blue screen @ TS Login - Hotfix KB826139

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Gert Thomaes - 24 Aug 2005 20:04 GMT

Hello, my problem is as follows; when connecting to the TS-Server on my
Win2K3 Standard Server (Dutch), no matter which user account or from which
client machine I keep getting a blue screen with nothing on it. The only
thing that I can do is close the session by using the control box of the
mstsc application. It seems like the client is waiting for something although
the hourglass is changed back to the regular pointer. I found out that this
is only the case if I initiate a new session, because when I do a local login
on the server and then take over this session with "mstsc -console" on some
client it works flawless.
Due to the fact that this not occurs the first time I connect to the TS,
that it's so for all accounts and on any client machine in the network,
through portforwarding or VPN, I can conclude that this is a TS server issue.
Plus that this started after installing SP1 (Dutch).
I found a hotfix which resembled my case; KB826139 but it came to my
attention that this fix was included is SP1 (not from an official MS website,
if anyone could confirm this?)
Please help me out here, since this is rather annoying because the server is
located at a company of a client and this makes administration of his server
quite difficult.

---
Gert Thomaes

Reply to this Message

Vera Noest [MVP] - 24 Aug 2005 20:40 GMT

I can definitively confirm that the hotfix described in KB 826139
is part of SP1. This is documented here:

824721 - Windows Server 2003 Service Pack 1 list of updates
http://support.microsoft.com/?kbid=824721

You can also compare the date and time of the services.exe
mentioned in the hotfix with the timestamp of your services.exe.
Yours should be the same or newer.

Now about your problem: I know of only one problem which was
introduced with SP1, not sure if it matches your problem, though:

898060 - Network connectivity between clients and servers may not
work after the installation of security update MS05-019 or Windows
Server 2003 Service Pack 1
http://support.microsoft.com/?kbid=898060

But interestingly, the workaround for this problem is to decrease
the MTU size, and this is also listed as the solution to the
problem (long before SP1) in the Terminal Services FAQ
http://www.microsoft.com/windowsserver2003/community/centers/termin
al/terminal_faq.mspx

<quote>
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
</quote>

So I would definitively give it a try.

In case the above doesn't help: is there anything in the EventLog
on the server? What kind of TS user profiles are you using, local
profiles or roaming profiles? Can you enabled verbose logging of
the user environment:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833
_________________________________________________________
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?R2VydCBUaG9tYWVz?= <lightningocc@hotmail.com.nospam>
wrote on 24 aug 2005 in microsoft.public.win2000.termserv.clients:

> Hello, my problem is as follows; when connecting to the
> TS-Server on my Win2K3 Standard Server (Dutch), no matter which
[quoted text clipped - 20 lines]
> ---
> Gert Thomaes

Reply to this Message

Gert Thomaes - 25 Aug 2005 15:53 GMT

Thank you for your quick response, I can't test the things you mentioned just
yet. I need to do this at the location due to the nature of the problem.
However I don't think MTU is the problem since the problem also accurs while
on the LAN itself.
Also I will see if the event log has anything to tell me if I enable verbose
logging, I'll keep you posted.
And again thanks for the quick response!

Kind regards,
Gert Thomaes

"Vera Noest [MVP]" schreef:

> I can definitively confirm that the hotfix described in KB 826139
> is part of SP1. This is documented here:
[quoted text clipped - 78 lines]
> > ---
> > Gert Thomaes

Reply to this Message

fstephan - 26 Aug 2005 11:07 GMT

compare this citrix issue:
http://support.citrix.com/kb/click.jspa?categoryID=118&externalID=CTX107051&sear
chID=-1

Reply to this Message