Re: Terminal Server hangs

Thanks Vera... Just for clarity Non-Native means drivers that were not on
the original install of 2003 server or drivers that were specifically
develped for 2003 Server but not on the original install? I was told by
another MS employee that installing 3rd party printer drivers is just
fine...that is why I have so many. This TS is a server for cusomters who
have a lot of different printers. I guess I have a lot of work ahead of me.

"Vera Noest [MVP]" wrote:

> You have already pinpointed the problem to a misbehaving printer
> driver. Did you install any non-native printer drivers on the
> server?
> Installing 3th party printer drivers on a TS is *not* recommended.
> Most of these drivers are not completely TS compatible, and are
> known to crash the printer spooler or the whole server.
> The best you can do is to uninstall these drivers completely.
>
> If your client printers are not autocreated, check the EventLog to
> find the reason. If the server doesn't recognize the printer, map
> the printer to a native driver on the server, by creating a custom
> ntprintsubs.inf file. Details are explained here:
>
> 239088 - Windows 2000 Terminal Services Server Logs Events 1111,
> 1105, and 1106
> http://support.microsoft.com/?kbid=239088
>
> You can check the recommended native driver substitution for your
> local printers here:
>
> Client Printer Autocreation Matrix
> http://www.printingsupport.com/matrix.htm
>
> Also check to see if your Group Policy or local policy is set to
> "Prevent Users from installing Print Drivers".
> If this is NOT enabled, a user with a newer signed driver will
> unknowingly and automatically propagate its' driver to the terminal
> server, which means that your servers will use different driver
> versions, even though you didn't intentionally install newer
> drivers.
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> =?Utf-8?B?SnVzdGlu?= <Justin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
> 13 apr 2005 in microsoft.public.windows.terminal_services:
>
> > I am a having a wierd problem with one of our 2003 Terminal
> > Servers. The Terminal Server all sudden seems to stop
> > responding to connection requests from outside the LAN. I can
> > connect fine to the server from within the LAN but outside users
> > just get the grey background screen. WHen this happens and I
> > open terminal services manager the Term Server with the problem
> > shows up with a yellow question mark on and is says gathering
> > info about this server, nothing ever happens and terminal server
> > manger may only show 2 or 3 of the currently logged in users for
> > that server on the left side of the screen. When you try to
> > close TS Manger it hangs. Also at the same time you cannot get
> > Task Manager to show up on the screen, you see the icon in the
> > bottom right but nothing else. ALso Printer and Faxes wont come
> > up either. Now I have found that if I go in and restart the
> > print spooler that it will fix the Printers and Faxes and Task
> > Manager problem, but the TS stays out to lunch for a few more
> > minutes....then poof it comes right back to life acting normal.
> > I beleive I am looking for a problem with a printer driver and
> > TS. And it seems to be the right set of event occur like a user
> > with a certain printer lgos in or something. What ever it is it
> > seems like some process just wont die until it times out and I
> > need to figure out what it is....it is driving me insane. Can
> > anyone point me to a good tool to help trouble shoot this or
> > just any help??????
>
.

Relevant Pages

  • Re: Terminal Server with SBS 2K3
    ... when a normal user logs on the terminal server ... have enough permission to install and uninstall printer drivers. ... If the printer driver for Windows 2003 server is not ...
    (microsoft.public.windows.server.sbs)
  • Re: Changing from App mode to Remote Admin mode via registry
    ... applications on the terminal server. ... Remote admin mode is simply activated by going ... Microsoft MVP - Terminal Server ... We'd like to do this because our application doesn't install right now in ...
    (microsoft.public.windows.terminal_services)
  • Re: Changing from App mode to Remote Admin mode via registry
    ... You can detect if your application is running in a remote ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Remote Administration mode for a Win2K3 terminal server without ... users not to install from a remote session? ...
    (microsoft.public.windows.terminal_services)
  • Re: RIS vs Altiris RapidDeploy/Install
    ... My school is part of the school district's 2003 AD. ... Each school has a 2003 member file server for each domain. ... choose the unattended XP or 2000 install most appropriate for their ... You can also use the OEM method to have drivers install during the ...
    (microsoft.public.windows.server.active_directory)
  • Windows Server 2003 - RIS help needed using RIPREP and NIC drivers
    ... Windows Server 2003 RIS is installed and working on my server. ... Incoroporated with those images I have the nic, video, and audio drivers ... HP machines are mainly using the Broadcom NIC drivers. ... Now I want to install additional software on these ...
    (microsoft.public.windows.server.setup)