Blank Screen after login to TS 2k3 SP2

April 23, 2008

Every now and then we have a problem on our Win2k3 SP2 server, and from that

moment on any new TS/RDP connection does not work...

After the login screen the desktop does not load, we just have the

background color of the screen and a mouse, but no icons, no taskbar, no

launches of startup programs.

W end up rebooting from a local account.

April 23, 2008

Re: Blank Screen after login to TS 2k3 SP2

And there's nothing in the EventLog when this happens?

Can you still connect to a shared folder on the server when this

happens?

Check if this helps, from:

Microsofts Terminal Services FAQ

http://www.microsoft.com/technet/community/en-

us/terminal/terminal_faq.mspx

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

Related articles:

314825 - How to Troubleshoot Black Hole Router Issues

http://support.microsoft.com/?kbid=314825

925280 - Changes in PMTU black hole router detection in Windows

Server 2003 and in Windows Vista

http://support.microsoft.com/?kbid=925280

_________________________________________________________

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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

on 23 apr 2008 in microsoft.public.windows.terminal_services:

> Every now and then we have a problem on our Win2k3 SP2 server,

> and from that moment on any new TS/RDP connection does not

> work...

>

> After the login screen the desktop does not load, we just have

> the background color of the screen and a mouse, but no icons, no

> taskbar, no launches of startup programs.

>

> W end up rebooting from a local account.

April 24, 2008

Re: Blank Screen after login to TS 2k3 SP2

Hello,

Thanks for the repply, I did find a lower limit on one of the networks, so I

applied a lower limit to the server.

But I don't know if it will be enough because some of the users get to the

server by a network that seems okay, and they still get the problem when it

happens.

The Event log has a lot of messages, because we have a lot of users that

have printers that have no equivalent driver wise on the server.

I did find though a few messages that could be linked : MsGina 1010, Userenv

1516 and 1517 in the Application events, and TermService 1041 in the System

events.

Thanks

"Vera Noest [MVP]" wrote:

> And there's nothing in the EventLog when this happens?

> Can you still connect to a shared folder on the server when this

> happens?

> Check if this helps, from:

>

> Microsofts Terminal Services FAQ

> http://www.microsoft.com/technet/community/en-

> us/terminal/terminal_faq.mspx

>

> 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

>

> Related articles:

>

> 314825 - How to Troubleshoot Black Hole Router Issues

> http://support.microsoft.com/?kbid=314825

>

> 925280 - Changes in PMTU black hole router detection in Windows

> Server 2003 and in Windows Vista

> http://support.microsoft.com/?kbid=925280

>

> _________________________________________________________

> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

> on 23 apr 2008 in microsoft.public.windows.terminal_services:

>

> > Every now and then we have a problem on our Win2k3 SP2 server,

> > and from that moment on any new TS/RDP connection does not

> > work...

> >

> > After the login screen the desktop does not load, we just have

> > the background color of the screen and a mouse, but no icons, no

> > taskbar, no launches of startup programs.

> >

> > W end up rebooting from a local account.

>

April 24, 2008

Re: Blank Screen after login to TS 2k3 SP2

And by the way, there are no shared folders I can make tests on.

"DaveMdf" wrote:

> Hello,

> Thanks for the repply, I did find a lower limit on one of the networks, so I

> applied a lower limit to the server.

>

> But I don't know if it will be enough because some of the users get to the

> server by a network that seems okay, and they still get the problem when it

> happens.

>

> The Event log has a lot of messages, because we have a lot of users that

> have printers that have no equivalent driver wise on the server.

>

> I did find though a few messages that could be linked : MsGina 1010, Userenv

> 1516 and 1517 in the Application events, and TermService 1041 in the System

> events.

>

> Thanks

>

> "Vera Noest [MVP]" wrote:

>

> > And there's nothing in the EventLog when this happens?

> > Can you still connect to a shared folder on the server when this

> > happens?

> > Check if this helps, from:

> >

> > Microsofts Terminal Services FAQ

> > http://www.microsoft.com/technet/community/en-

> > us/terminal/terminal_faq.mspx

> >

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

> >

> > Related articles:

> >

> > 314825 - How to Troubleshoot Black Hole Router Issues

> > http://support.microsoft.com/?kbid=314825

> >

> > 925280 - Changes in PMTU black hole router detection in Windows

> > Server 2003 and in Windows Vista

> > http://support.microsoft.com/?kbid=925280

> >

> > _________________________________________________________

> > 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

> > on 23 apr 2008 in microsoft.public.windows.terminal_services:

> >

> > > Every now and then we have a problem on our Win2k3 SP2 server,

> > > and from that moment on any new TS/RDP connection does not

> > > work...

> > >

> > > After the login screen the desktop does not load, we just have

> > > the background color of the screen and a mouse, but no icons, no

> > > taskbar, no launches of startup programs.

> > >

> > > W end up rebooting from a local account.

> >

April 24, 2008

Re: Blank Screen after login to TS 2k3 SP2

You can try to connect to \\servername\c$, which is the default

administrative share for the C: drive.

_________________________________________________________

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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

on 24 apr 2008 in microsoft.public.windows.terminal_services:

> And by the way, there are no shared folders I can make tests on.

>

> "DaveMdf" wrote:

>

>> Hello,

>> Thanks for the repply, I did find a lower limit on one of the

>> networks, so I applied a lower limit to the server.

>>

>> But I don't know if it will be enough because some of the users

>> get to the server by a network that seems okay, and they still

>> get the problem when it happens.

>>

>> The Event log has a lot of messages, because we have a lot of

>> users that have printers that have no equivalent driver wise on

>> the server.

>>

>> I did find though a few messages that could be linked : MsGina

>> 1010, Userenv 1516 and 1517 in the Application events, and

>> TermService 1041 in the System events.

>>

>> Thanks

>>

>> "Vera Noest [MVP]" wrote:

>>

>> > And there's nothing in the EventLog when this happens?

>> > Can you still connect to a shared folder on the server when

>> > this happens?

>> > Check if this helps, from:

>> >

>> > Microsofts Terminal Services FAQ

>> > http://www.microsoft.com/technet/community/en-

>> > us/terminal/terminal_faq.mspx

>> >

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

>> >

>> > Related articles:

>> >

>> > 314825 - How to Troubleshoot Black Hole Router Issues

>> > http://support.microsoft.com/?kbid=314825

>> >

>> > 925280 - Changes in PMTU black hole router detection in

>> > Windows Server 2003 and in Windows Vista

>> > http://support.microsoft.com/?kbid=925280

>> >

>> > _________________________________________________________

>> > 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> > wrote on 23 apr 2008 in

>> > microsoft.public.windows.terminal_services:

>> >

>> > > Every now and then we have a problem on our Win2k3 SP2

>> > > server, and from that moment on any new TS/RDP connection

>> > > does not work...

>> > >

>> > > After the login screen the desktop does not load, we just

>> > > have the background color of the screen and a mouse, but no

>> > > icons, no taskbar, no launches of startup programs.

>> > >

>> > > W end up rebooting from a local account.

April 24, 2008

Re: Blank Screen after login to TS 2k3 SP2

Seems you have some sort of network problem, preventing connection

to the users' home directory and profile load/unload errors.

Check these events on eventid.net:

http://www.eventid.net/display.asp?eventid=1010&eventno=3523

&source=MsGina&phase=1

http://www.eventid.net/display.asp?eventid=1516&eventno=2260

&source=Userenv&phase=1

http://www.eventid.net/display.asp?eventid=1041&eventno=4645

&source=TermService&phase=1

_________________________________________________________

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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

on 24 apr 2008 in microsoft.public.windows.terminal_services:

> Hello,

> Thanks for the repply, I did find a lower limit on one of the

> networks, so I applied a lower limit to the server.

>

> But I don't know if it will be enough because some of the users

> get to the server by a network that seems okay, and they still

> get the problem when it happens.

>

> The Event log has a lot of messages, because we have a lot of

> users that have printers that have no equivalent driver wise on

> the server.

>

> I did find though a few messages that could be linked : MsGina

> 1010, Userenv 1516 and 1517 in the Application events, and

> TermService 1041 in the System events.

>

> Thanks

>

> "Vera Noest [MVP]" wrote:

>

>> And there's nothing in the EventLog when this happens?

>> Can you still connect to a shared folder on the server when

>> this happens?

>> Check if this helps, from:

>>

>> Microsofts Terminal Services FAQ

>> http://www.microsoft.com/technet/community/en-

>> us/terminal/terminal_faq.mspx

>>

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

>>

>> Related articles:

>>

>> 314825 - How to Troubleshoot Black Hole Router Issues

>> http://support.microsoft.com/?kbid=314825

>>

>> 925280 - Changes in PMTU black hole router detection in Windows

>> Server 2003 and in Windows Vista

>> http://support.microsoft.com/?kbid=925280

>>

>> _________________________________________________________

>> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> wrote on 23 apr 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Every now and then we have a problem on our Win2k3 SP2

>> > server, and from that moment on any new TS/RDP connection

>> > does not work...

>> >

>> > After the login screen the desktop does not load, we just

>> > have the background color of the screen and a mouse, but no

>> > icons, no taskbar, no launches of startup programs.

>> >

>> > W end up rebooting from a local account.

May 19, 2008

Re: Blank Screen after login to TS 2k3 SP2

The problem happened again but this time I only got Userenv errors in the log.

Appart from that we get lots of deferent sorts of Printer errors for each

Printer that is on the client PC and we lack the drivers for on the server.

Is there a way to limit the mapping of the printers save the default printer

which they need ?

I have read somewhere that printer mapping errors could be a serious issue...

"Vera Noest [MVP]" wrote:

> Seems you have some sort of network problem, preventing connection

> to the users' home directory and profile load/unload errors.

> Check these events on eventid.net:

>

> http://www.eventid.net/display.asp?eventid=1010&eventno=3523

> &source=MsGina&phase=1

>

> http://www.eventid.net/display.asp?eventid=1516&eventno=2260

> &source=Userenv&phase=1

>

> http://www.eventid.net/display.asp?eventid=1041&eventno=4645

> &source=TermService&phase=1

> _________________________________________________________

> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

> on 24 apr 2008 in microsoft.public.windows.terminal_services:

>

> > Hello,

> > Thanks for the repply, I did find a lower limit on one of the

> > networks, so I applied a lower limit to the server.

> >

> > But I don't know if it will be enough because some of the users

> > get to the server by a network that seems okay, and they still

> > get the problem when it happens.

> >

> > The Event log has a lot of messages, because we have a lot of

> > users that have printers that have no equivalent driver wise on

> > the server.

> >

> > I did find though a few messages that could be linked : MsGina

> > 1010, Userenv 1516 and 1517 in the Application events, and

> > TermService 1041 in the System events.

> >

> > Thanks

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> And there's nothing in the EventLog when this happens?

> >> Can you still connect to a shared folder on the server when

> >> this happens?

> >> Check if this helps, from:

> >>

> >> Microsofts Terminal Services FAQ

> >> http://www.microsoft.com/technet/community/en-

> >> us/terminal/terminal_faq.mspx

> >>

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

> >>

> >> Related articles:

> >>

> >> 314825 - How to Troubleshoot Black Hole Router Issues

> >> http://support.microsoft.com/?kbid=314825

> >>

> >> 925280 - Changes in PMTU black hole router detection in Windows

> >> Server 2003 and in Windows Vista

> >> http://support.microsoft.com/?kbid=925280

> >>

> >> _________________________________________________________

> >> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

> >> wrote on 23 apr 2008 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Every now and then we have a problem on our Win2k3 SP2

> >> > server, and from that moment on any new TS/RDP connection

> >> > does not work...

> >> >

> >> > After the login screen the desktop does not load, we just

> >> > have the background color of the screen and a mouse, but no

> >> > icons, no taskbar, no launches of startup programs.

> >> >

> >> > W end up rebooting from a local account.

>

May 19, 2008

Re: Blank Screen after login to TS 2k3 SP2

Warnings about printers which cannot be redirected because there is

no driver on the server are not dangerous, just a nuisance.

The danger comes from trying to solve it by installing TS-

incompatible printer drivers.

But sure, you can only redirect the default printer:

911913 - How to redirect the default printer of a Terminal Services

client to a Windows Server 2003 Terminal Server session

http://support.microsoft.com/?kbid=911913

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

=?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

on 19 maj 2008:

> The problem happened again but this time I only got Userenv

> errors in the log. Appart from that we get lots of deferent

> sorts of Printer errors for each Printer that is on the client

> PC and we lack the drivers for on the server.

>

> Is there a way to limit the mapping of the printers save the

> default printer which they need ?

>

> I have read somewhere that printer mapping errors could be a

> serious issue...

>

> "Vera Noest [MVP]" wrote:

>

>> Seems you have some sort of network problem, preventing

>> connection to the users' home directory and profile load/unload

>> errors. Check these events on eventid.net:

>>

>> http://www.eventid.net/display.asp?eventid=1010&eventno=3523

>> &source=MsGina&phase=1

>>

>> http://www.eventid.net/display.asp?eventid=1516&eventno=2260

>> &source=Userenv&phase=1

>>

>> http://www.eventid.net/display.asp?eventid=1041&eventno=4645

>> &source=TermService&phase=1

>> _________________________________________________________

>> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> wrote on 24 apr 2008 in

>> microsoft.public.windows.terminal_services:

>>

>> > Hello,

>> > Thanks for the repply, I did find a lower limit on one of the

>> > networks, so I applied a lower limit to the server.

>> >

>> > But I don't know if it will be enough because some of the

>> > users get to the server by a network that seems okay, and

>> > they still get the problem when it happens.

>> >

>> > The Event log has a lot of messages, because we have a lot of

>> > users that have printers that have no equivalent driver wise

>> > on the server.

>> >

>> > I did find though a few messages that could be linked :

>> > MsGina 1010, Userenv 1516 and 1517 in the Application events,

>> > and TermService 1041 in the System events.

>> >

>> > Thanks

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> And there's nothing in the EventLog when this happens?

>> >> Can you still connect to a shared folder on the server when

>> >> this happens?

>> >> Check if this helps, from:

>> >>

>> >> Microsofts Terminal Services FAQ

>> >> http://www.microsoft.com/technet/community/en-

>> >> us/terminal/terminal_faq.mspx

>> >>

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

>> >>

>> >> Related articles:

>> >>

>> >> 314825 - How to Troubleshoot Black Hole Router Issues

>> >> http://support.microsoft.com/?kbid=314825

>> >>

>> >> 925280 - Changes in PMTU black hole router detection in

>> >> Windows Server 2003 and in Windows Vista

>> >> http://support.microsoft.com/?kbid=925280

>> >>

>> >> _________________________________________________________

>> >> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> >> wrote on 23 apr 2008 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Every now and then we have a problem on our Win2k3 SP2

>> >> > server, and from that moment on any new TS/RDP connection

>> >> > does not work...

>> >> >

>> >> > After the login screen the desktop does not load, we just

>> >> > have the background color of the screen and a mouse, but

>> >> > no icons, no taskbar, no launches of startup programs.

>> >> >

>> >> > W end up rebooting from a local account.

May 19, 2008

Re: Blank Screen after login to TS 2k3 SP2

Hi, thanks for the reply, but is there a way to have that effect buy adding

settings to the server and not to the client computers ?

I have read on a forum that when a client connects the registry of all users

is updated with all his printers, could that be a problem if some of the user

sessions are sessions that did not close correctly ?

Thanks for the input.

"Vera Noest [MVP]" wrote:

> Warnings about printers which cannot be redirected because there is

> no driver on the server are not dangerous, just a nuisance.

> The danger comes from trying to solve it by installing TS-

> incompatible printer drivers.

> But sure, you can only redirect the default printer:

>

> 911913 - How to redirect the default printer of a Terminal Services

> client to a Windows Server 2003 Terminal Server session

> http://support.microsoft.com/?kbid=911913

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> *----------- Please reply in newsgroup -------------*

>

> =?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

> on 19 maj 2008:

>

> > The problem happened again but this time I only got Userenv

> > errors in the log. Appart from that we get lots of deferent

> > sorts of Printer errors for each Printer that is on the client

> > PC and we lack the drivers for on the server.

> >

> > Is there a way to limit the mapping of the printers save the

> > default printer which they need ?

> >

> > I have read somewhere that printer mapping errors could be a

> > serious issue...

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Seems you have some sort of network problem, preventing

> >> connection to the users' home directory and profile load/unload

> >> errors. Check these events on eventid.net:

> >>

> >> http://www.eventid.net/display.asp?eventid=1010&eventno=3523

> >> &source=MsGina&phase=1

> >>

> >> http://www.eventid.net/display.asp?eventid=1516&eventno=2260

> >> &source=Userenv&phase=1

> >>

> >> http://www.eventid.net/display.asp?eventid=1041&eventno=4645

> >> &source=TermService&phase=1

> >> _________________________________________________________

> >> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

> >> wrote on 24 apr 2008 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > Hello,

> >> > Thanks for the repply, I did find a lower limit on one of the

> >> > networks, so I applied a lower limit to the server.

> >> >

> >> > But I don't know if it will be enough because some of the

> >> > users get to the server by a network that seems okay, and

> >> > they still get the problem when it happens.

> >> >

> >> > The Event log has a lot of messages, because we have a lot of

> >> > users that have printers that have no equivalent driver wise

> >> > on the server.

> >> >

> >> > I did find though a few messages that could be linked :

> >> > MsGina 1010, Userenv 1516 and 1517 in the Application events,

> >> > and TermService 1041 in the System events.

> >> >

> >> > Thanks

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> And there's nothing in the EventLog when this happens?

> >> >> Can you still connect to a shared folder on the server when

> >> >> this happens?

> >> >> Check if this helps, from:

> >> >>

> >> >> Microsofts Terminal Services FAQ

> >> >> http://www.microsoft.com/technet/community/en-

> >> >> us/terminal/terminal_faq.mspx

> >> >>

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

> >> >>

> >> >> Related articles:

> >> >>

> >> >> 314825 - How to Troubleshoot Black Hole Router Issues

> >> >> http://support.microsoft.com/?kbid=314825

> >> >>

> >> >> 925280 - Changes in PMTU black hole router detection in

> >> >> Windows Server 2003 and in Windows Vista

> >> >> http://support.microsoft.com/?kbid=925280

> >> >>

> >> >> _________________________________________________________

> >> >> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

> >> >> wrote on 23 apr 2008 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > Every now and then we have a problem on our Win2k3 SP2

> >> >> > server, and from that moment on any new TS/RDP connection

> >> >> > does not work...

> >> >> >

> >> >> > After the login screen the desktop does not load, we just

> >> >> > have the background color of the screen and a mouse, but

> >> >> > no icons, no taskbar, no launches of startup programs.

> >> >> >

> >> >> > W end up rebooting from a local account.

>

May 19, 2008

Re: Blank Screen after login to TS 2k3 SP2

No, the RedirectDefaultPrinterOnly registry entry must be created

on the client.

I don't understand what you mean with the second part of your post.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

*----------- Please reply in newsgroup -------------*

=?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

on 19 maj 2008:

> Hi, thanks for the reply, but is there a way to have that effect

> buy adding settings to the server and not to the client

> computers ?

>

> I have read on a forum that when a client connects the registry

> of all users is updated with all his printers, could that be a

> problem if some of the user sessions are sessions that did not

> close correctly ?

>

> Thanks for the input.

>

> "Vera Noest [MVP]" wrote:

>

>> Warnings about printers which cannot be redirected because

>> there is no driver on the server are not dangerous, just a

>> nuisance. The danger comes from trying to solve it by

>> installing TS- incompatible printer drivers.

>> But sure, you can only redirect the default printer:

>>

>> 911913 - How to redirect the default printer of a Terminal

>> Services client to a Windows Server 2003 Terminal Server

>> session http://support.microsoft.com/?kbid=911913

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> *----------- Please reply in newsgroup -------------*

>>

>> =?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> wrote on 19 maj 2008:

>>

>> > The problem happened again but this time I only got Userenv

>> > errors in the log. Appart from that we get lots of deferent

>> > sorts of Printer errors for each Printer that is on the

>> > client PC and we lack the drivers for on the server.

>> >

>> > Is there a way to limit the mapping of the printers save the

>> > default printer which they need ?

>> >

>> > I have read somewhere that printer mapping errors could be a

>> > serious issue...

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Seems you have some sort of network problem, preventing

>> >> connection to the users' home directory and profile

>> >> load/unload errors. Check these events on eventid.net:

>> >>

>> >> http://www.eventid.net/display.asp?eventid=1010&eventno=3523

>> >> &source=MsGina&phase=1

>> >>

>> >> http://www.eventid.net/display.asp?eventid=1516&eventno=2260

>> >> &source=Userenv&phase=1

>> >>

>> >> http://www.eventid.net/display.asp?eventid=1041&eventno=4645

>> >> &source=TermService&phase=1

>> >> _________________________________________________________

>> >> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> >> wrote on 24 apr 2008 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > Hello,

>> >> > Thanks for the repply, I did find a lower limit on one of

>> >> > the networks, so I applied a lower limit to the server.

>> >> >

>> >> > But I don't know if it will be enough because some of the

>> >> > users get to the server by a network that seems okay, and

>> >> > they still get the problem when it happens.

>> >> >

>> >> > The Event log has a lot of messages, because we have a lot

>> >> > of users that have printers that have no equivalent driver

>> >> > wise on the server.

>> >> >

>> >> > I did find though a few messages that could be linked :

>> >> > MsGina 1010, Userenv 1516 and 1517 in the Application

>> >> > events, and TermService 1041 in the System events.

>> >> >

>> >> > Thanks

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> And there's nothing in the EventLog when this happens?

>> >> >> Can you still connect to a shared folder on the server

>> >> >> when this happens?

>> >> >> Check if this helps, from:

>> >> >>

>> >> >> Microsofts Terminal Services FAQ

>> >> >> http://www.microsoft.com/technet/community/en-

>> >> >> us/terminal/terminal_faq.mspx

>> >> >>

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

>> >> >>

>> >> >> Related articles:

>> >> >>

>> >> >> 314825 - How to Troubleshoot Black Hole Router Issues

>> >> >> http://support.microsoft.com/?kbid=314825

>> >> >>

>> >> >> 925280 - Changes in PMTU black hole router detection in

>> >> >> Windows Server 2003 and in Windows Vista

>> >> >> http://support.microsoft.com/?kbid=925280

>> >> >>

>> >> >> _________________________________________________________

>> >> >> 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?RGF2ZU1kZg==?=

>> >> >> <DaveMdf@discussions.microsoft.com> wrote on 23 apr 2008

>> >> >> in microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > Every now and then we have a problem on our Win2k3 SP2

>> >> >> > server, and from that moment on any new TS/RDP

>> >> >> > connection does not work...

>> >> >> >

>> >> >> > After the login screen the desktop does not load, we

>> >> >> > just have the background color of the screen and a

>> >> >> > mouse, but no icons, no taskbar, no launches of startup

>> >> >> > programs.

>> >> >> >

>> >> >> > W end up rebooting from a local account.

August 8, 2008

Re: Blank Screen after login to TS 2k3 SP2

Hello,

I did not have the opportunity to do anything about printers on client

computers.

But, I have set reboots that launch if the Server is inactive for over 30

minutes, maximum once every 4 hours during daytime, a true reboot at night.

These reboots don't change anything, I still have the problem coming up...

I've also installed a VNC to connect in the console account, when the

problem happens, without having to use TS. It worked and I tried to look

around for clues, but the memory and processor were okay, no overload, I

tried relaunching the TS Listener, but it did not change anything... went and

look at the services, but nothing struck me as needing to be rebooted, except

Terminal Server Services but that service can't be modified.

In the Event log the only thing I had was Userenv 1524, 1516, 1517 and

TermServDevices 1111.

What is really hard to grasp is that all my searches for the TS Blank screen

problem point to hotfixes that are already included in SP1, and I'm in SP2,

should I remove SP2 ? Just to see if it had been fixed in SP1 and

unstabilized again in SP2 ?

"Vera Noest [MVP]" wrote:

> No, the RedirectDefaultPrinterOnly registry entry must be created

> on the client.

>

> I don't understand what you mean with the second part of your post.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> *----------- Please reply in newsgroup -------------*

>

> =?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

> on 19 maj 2008:

>

> > Hi, thanks for the reply, but is there a way to have that effect

> > buy adding settings to the server and not to the client

> > computers ?

> >

> > I have read on a forum that when a client connects the registry

> > of all users is updated with all his printers, could that be a

> > problem if some of the user sessions are sessions that did not

> > close correctly ?

> >

> > Thanks for the input.

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Warnings about printers which cannot be redirected because

> >> there is no driver on the server are not dangerous, just a

> >> nuisance. The danger comes from trying to solve it by

> >> installing TS- incompatible printer drivers.

> >> But sure, you can only redirect the default printer:

> >>

> >> 911913 - How to redirect the default printer of a Terminal

> >> Services client to a Windows Server 2003 Terminal Server

> >> session http://support.microsoft.com/?kbid=911913

> >>

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

> >> TS troubleshooting: http://ts.veranoest.net

> >> *----------- Please reply in newsgroup -------------*

> >>

> >> =?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

> >> wrote on 19 maj 2008:

> >>

> >> > The problem happened again but this time I only got Userenv

> >> > errors in the log. Appart from that we get lots of deferent

> >> > sorts of Printer errors for each Printer that is on the

> >> > client PC and we lack the drivers for on the server.

> >> >

> >> > Is there a way to limit the mapping of the printers save the

> >> > default printer which they need ?

> >> >

> >> > I have read somewhere that printer mapping errors could be a

> >> > serious issue...

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> Seems you have some sort of network problem, preventing

> >> >> connection to the users' home directory and profile

> >> >> load/unload errors. Check these events on eventid.net:

> >> >>

> >> >> http://www.eventid.net/display.asp?eventid=1010&eventno=3523

> >> >> &source=MsGina&phase=1

> >> >>

> >> >> http://www.eventid.net/display.asp?eventid=1516&eventno=2260

> >> >> &source=Userenv&phase=1

> >> >>

> >> >> http://www.eventid.net/display.asp?eventid=1041&eventno=4645

> >> >> &source=TermService&phase=1

> >> >> _________________________________________________________

> >> >> 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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

> >> >> wrote on 24 apr 2008 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > Hello,

> >> >> > Thanks for the repply, I did find a lower limit on one of

> >> >> > the networks, so I applied a lower limit to the server.

> >> >> >

> >> >> > But I don't know if it will be enough because some of the

> >> >> > users get to the server by a network that seems okay, and

> >> >> > they still get the problem when it happens.

> >> >> >

> >> >> > The Event log has a lot of messages, because we have a lot

> >> >> > of users that have printers that have no equivalent driver

> >> >> > wise on the server.

> >> >> >

> >> >> > I did find though a few messages that could be linked :

> >> >> > MsGina 1010, Userenv 1516 and 1517 in the Application

> >> >> > events, and TermService 1041 in the System events.

> >> >> >

> >> >> > Thanks

> >> >> >

> >> >> > "Vera Noest [MVP]" wrote:

> >> >> >

> >> >> >> And there's nothing in the EventLog when this happens?

> >> >> >> Can you still connect to a shared folder on the server

> >> >> >> when this happens?

> >> >> >> Check if this helps, from:

> >> >> >>

> >> >> >> Microsofts Terminal Services FAQ

> >> >> >> http://www.microsoft.com/technet/community/en-

> >> >> >> us/terminal/terminal_faq.mspx

> >> >> >>

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

> >> >> >>

> >> >> >> Related articles:

> >> >> >>

> >> >> >> 314825 - How to Troubleshoot Black Hole Router Issues

> >> >> >> http://support.microsoft.com/?kbid=314825

> >> >> >>

> >> >> >> 925280 - Changes in PMTU black hole router detection in

> >> >> >> Windows Server 2003 and in Windows Vista

> >> >> >> http://support.microsoft.com/?kbid=925280

> >> >> >>

> >> >> >> _________________________________________________________

> >> >> >> 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?RGF2ZU1kZg==?=

> >> >> >> <DaveMdf@discussions.microsoft.com> wrote on 23 apr 2008

> >> >> >> in microsoft.public.windows.terminal_services:

> >> >> >>

> >> >> >> > Every now and then we have a problem on our Win2k3 SP2

> >> >> >> > server, and from that moment on any new TS/RDP

> >> >> >> > connection does not work...

> >> >> >> >

> >> >> >> > After the login screen the desktop does not load, we

> >> >> >> > just have the background color of the screen and a

> >> >> >> > mouse, but no icons, no taskbar, no launches of startup

> >> >> >> > programs.

> >> >> >> >

> >> >> >> > W end up rebooting from a local account.

>

August 8, 2008

Re: Blank Screen after login to TS 2k3 SP2

No, I would *not* uninstall SP2, that will only give you more

problems. And if it was a bug reintroduced in SP2, it would be a

known problem by now.

Do you still get these 2 events: MsGina 1010, TermService 1041?

You'll have to solve those profile load and unload errors first,

could well be that they are the cause of the problem.

Check these out:

935642 - Error message and the terminal server roaming profile is

not loaded when you log on to a Windows Server 2003-based terminal

server

http://support.microsoft.com/?kbid=935642

944984 - The user profile may not be correctly unloaded when you

log off from a Windows Server 2003-based computer, and event 1517

is logged

http://support.microsoft.com/?kbid=944984

_________________________________________________________

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?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com> wrote

on 08 aug 2008 in microsoft.public.windows.terminal_services:

> Hello,

> I did not have the opportunity to do anything about printers on

> client computers.

>

> But, I have set reboots that launch if the Server is inactive

> for over 30 minutes, maximum once every 4 hours during daytime,

> a true reboot at night. These reboots don't change anything, I

> still have the problem coming up...

>

> I've also installed a VNC to connect in the console account,

> when the problem happens, without having to use TS. It worked

> and I tried to look around for clues, but the memory and

> processor were okay, no overload, I tried relaunching the TS

> Listener, but it did not change anything... went and look at the

> services, but nothing struck me as needing to be rebooted,

> except Terminal Server Services but that service can't be

> modified.

>

> In the Event log the only thing I had was Userenv 1524, 1516,

> 1517 and TermServDevices 1111.

>

> What is really hard to grasp is that all my searches for the TS

> Blank screen problem point to hotfixes that are already included

> in SP1, and I'm in SP2, should I remove SP2 ? Just to see if it

> had been fixed in SP1 and unstabilized again in SP2 ?

>

> "Vera Noest [MVP]" wrote:

>

>> No, the RedirectDefaultPrinterOnly registry entry must be

>> created on the client.

>>

>> I don't understand what you mean with the second part of your

>> post. _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> *----------- Please reply in newsgroup -------------*

>>

>> =?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> wrote on 19 maj 2008:

>>

>> > Hi, thanks for the reply, but is there a way to have that

>> > effect buy adding settings to the server and not to the

>> > client computers ?

>> >

>> > I have read on a forum that when a client connects the

>> > registry of all users is updated with all his printers, could

>> > that be a problem if some of the user sessions are sessions

>> > that did not close correctly ?

>> >

>> > Thanks for the input.

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Warnings about printers which cannot be redirected because

>> >> there is no driver on the server are not dangerous, just a

>> >> nuisance. The danger comes from trying to solve it by

>> >> installing TS- incompatible printer drivers.

>> >> But sure, you can only redirect the default printer:

>> >>

>> >> 911913 - How to redirect the default printer of a Terminal

>> >> Services client to a Windows Server 2003 Terminal Server

>> >> session http://support.microsoft.com/?kbid=911913

>> >>

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

>> >> TS troubleshooting: http://ts.veranoest.net

>> >> *----------- Please reply in newsgroup -------------*

>> >>

>> >> =?Utf-8?B?RGF2ZU1kZg==?= <DaveMdf@discussions.microsoft.com>

>> >> wrote on 19 maj 2008:

>> >>

>> >> > The problem happened again but this time I only got

>> >> > Userenv errors in the log. Appart from that we get lots of

>> >> > deferent sorts of Printer errors for each Printer that is

>> >> > on the client PC and we lack the drivers for on the

>> >> > server.

>> >> >

>> >> > Is there a way to limit the mapping of the printers save

>> >> > the default printer which they need ?

>> >> >

>> >> > I have read somewhere that printer mapping errors could be

>> >> > a serious issue...

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> Seems you have some sort of network problem, preventing

>> >> >> connection to the users' home directory and profile

>> >> >> load/unload errors. Check these events on eventid.net:

>> >> >>

>> >> >> http://www.eventid.net/display.asp?eventid=1010&eventno=35

>> >> >> 23 &source=MsGina&phase=1

>> >> >>

>> >> >> http://www.eventid.net/display.asp?eventid=1516&eventno=22

>> >> >> 60 &source=Userenv&phase=1

>> >> >>

>> >> >> http://www.eventid.net/display.asp?eventid=1041&eventno=46

>> >> >> 45 &source=TermService&phase=1

>> >> >> _________________________________________________________

>> >> >> 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?RGF2ZU1kZg==?=

>> >> >> <DaveMdf@discussions.microsoft.com> wrote on 24 apr 2008

>> >> >> in microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > Hello,

>> >> >> > Thanks for the repply, I did find a lower limit on one

>> >> >> > of the networks, so I applied a lower limit to the

>> >> >> > server.

>> >> >> >

>> >> >> > But I don't know if it will be enough because some of

>> >> >> > the users get to the server by a network that seems

>> >> >> > okay, and they still get the problem when it happens.

>> >> >> >

>> >> >> > The Event log has a lot of messages, because we have a

>> >> >> > lot of users that have printers that have no equivalent

>> >> >> > driver wise on the server.

>> >> >> >

>> >> >> > I did find though a few messages that could be linked :

>> >> >> > MsGina 1010, Userenv 1516 and 1517 in the Application

>> >> >> > events, and TermService 1041 in the System events.

>> >> >> >

>> >> >> > Thanks

>> >> >> >

>> >> >> > "Vera Noest [MVP]" wrote:

>> >> >> >

>> >> >> >> And there's nothing in the EventLog when this happens?

>> >> >> >> Can you still connect to a shared folder on the server

>> >> >> >> when this happens?

>> >> >> >> Check if this helps, from:

>> >> >> >>

>> >> >> >> Microsofts Terminal Services FAQ

>> >> >> >> http://www.microsoft.com/technet/community/en-

>> >> >> >> us/terminal/terminal_faq.mspx

>> >> >> >>

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

>> >> >> >>

>> >> >> >> Related articles:

>> >> >> >>

>> >> >> >> 314825 - How to Troubleshoot Black Hole Router Issues

>> >> >> >> http://support.microsoft.com/?kbid=314825

>> >> >> >>

>> >> >> >> 925280 - Changes in PMTU black hole router detection

>> >> >> >> in Windows Server 2003 and in Windows Vista

>> >> >> >> http://support.microsoft.com/?kbid=925280

>> >> >> >>

>> >> >> >> _______________________________________________________

>> >> >> >> __ 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?RGF2ZU1kZg==?=

>> >> >> >> <DaveMdf@discussions.microsoft.com> wrote on 23 apr

>> >> >> >> 2008 in microsoft.public.windows.terminal_services:

>> >> >> >>

>> >> >> >> > Every now and then we have a problem on our Win2k3

>> >> >> >> > SP2 server, and from that moment on any new TS/RDP

>> >> >> >> > connection does not work...

>> >> >> >> >

>> >> >> >> > After the login screen the desktop does not load, we

>> >> >> >> > just have the background color of the screen and a

>> >> >> >> > mouse, but no icons, no taskbar, no launches of

>> >> >> >> > startup programs.

>> >> >> >> >

>> >> >> >> > W end up rebooting from a local account.

Sign In

Blank Screen after login to TS 2k3 SP2

Recommended Posts

Guest DaveMdf

Popular Days

Popular Days

Guest Vera Noest [MVP]

Guest DaveMdf

Guest DaveMdf

Guest Vera Noest [MVP]

Guest Vera Noest [MVP]

Guest DaveMdf

Guest Vera Noest [MVP]

Guest DaveMdf

Guest Vera Noest [MVP]

Guest DaveMdf

Guest Vera Noest [MVP]

Similar Content

Login screen image

Windows 11 Login Screen Problem

Mousepad works on login screen, but not after login

Blank grey screen on windows 10 old hp laptop

Mouse and Keyboard not working after login

Browse

Activity

Site Info