Re: Crashing sessions on Win2003 Terminal Services

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bj?rnar B. (bbolsoy_at_hotmail.com)
Date: 11/11/04


Date: 11 Nov 2004 10:36:35 -0800

Hello Vera,

Well since the addition of the LJ2300, 2550 and 1150 drivers,
and doubleing the userbase, the problem worsend substantially.

I removed the 1150 driver yesterday, as it wasn't certified for
TS2003 by HP, but I just got feedback from a user which experienced
another crash today.

All other HP printerdrivers I have here are certified according to HP.

I also have a couple of other 3rd party drivers, such as an OKI5100C,
but it has been installed since day-1 and doesn't seem to have caused
any trouble. I've also been unable to find another driver substitute
for it that works, so far, or else I would swap it out.

The .inf solution is interesting, but it would mean customizing the
server, complicating setup, documentation etc. which I try my very best
not to do. Easier to change the local drivers on the client in my case,
as it's only about a dozen clients all in all.

Thank you for your feedback.

Regards...

"Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message news:<Xns959D9AA299C0veranoesthemutforsse@207.46.248.16>...
> Did you install any 3th party printer drivers on the server?
> Many of those are not TS-compatible and can creash your spooler
> service or the server.
>
> The remedy is to uninstall all 3th party drivers and instead map
> the printers to a native driver, by creating a custom
> ntprintsubs.inf file.
> Details here:
>
> 239088 - Windows 2000 Terminal Services Server Logs Events 1111,
> 1105, and 1106
> http://support.microsoft.com/?kbid=239088
>
> --
> Vera Noest
> MCSE,CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> *----------- Please reply in newsgroup -------------*
>
> bbolsoy@hotmail.com (Bj?rnar B.) wrote on 10 nov 2004:
>
> > Connection is ADSL in most cases.
> > It's been a problem for about three weeks, worsend when we
> > installed 6 new users with new color laserjet printers.
> >
> > NIC is Intel Pro/1000 CT.
> >
> >
> > Regards...
> >
> >
> >
> > cbdrako99 <cbdrako@hotmail.com> wrote in message
> > news:<8AD561DE-7F5E-4428-85F9-5ACD4192CF4F@microsoft.com>...
> >> Are the users local or are the connecting over a internet
> >> connection (VPN, WAN IP, Etc.) Also how long has this been
> >> happening? Is this a new server that has an Intel NIC Pro MT
> >> 1000?
> >>
> >> Chris
> >>
> >> "Bj?rnar B." wrote:
> >>
> >> > Hello,
> >> >
> >> > We have a serious problem with user sessions frequently
> >> > crashing on of our Win2003 TS setups. The symptoms are:
> >> > locked screen, "reconnecting box" and then a login window.
> >> > Any app or document in writing is lost, just as if it were a
> >> > fresh login.
> >> >
> >> > All clients are WinXP Pro with the latest RDP client and
> >> > normal local printer redirection.
> >> >
> >> > We suspect this is a printer issue as it happens randomly on
> >> > different setups, network types, company and locations, and
> >> > in some cases several users go down simoultaneously while
> >> > other times only individual users are affected.
> >> >
> >> > The eventlog shows up pretty scarse, with only printers
> >> > purging/deleting at the time of the incident.
> >> >
> >> > BTW, how does one set up more thorough eventlogging on
> >> > Win2003?
> >> >
> >> >
> >> > This got substantially worse after we added some new users
> >> > and Color LJ 3500 and LJ 2300 printerdrivers to the system.
> >> >
> >> > We've tried upgrading to the latest drivers and run Office
> >> > 2003 SP1 to no vail.
> >> >
> >> > Any tip is -greatly- appreciated.
> >> >
> >> >
> >> > Regards...



Relevant Pages

  • Re: BSoD on 2003 TS - varying error codes
    ... Another option is to completely wipe the server and reinstall from a known good image or from scratch. ... If the problem comes back then it is most likely faulty hardware. ... Possible Faulty Device Drivers ...
    (microsoft.public.windows.terminal_services)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Keep in mind that I have seen OEM drivers up there so given that you've blown that image away, I can't say for certain that the 'critical' was 100% pushed by Microsoft. ... External USB is no replacement for local drives. ... LOL I show my naivety here when I say that I showed great diligence in my blind application of any MS suggested resolution to "Critical Errors" on my Small Business Server Monitor Report. ... When I got the first BSOD, I booted from the orginal CD and chose to only restore the System files. ...
    (microsoft.public.windows.server.sbs)
  • SUMMARY - Re: Jumpstart x86 - not accepting -B insall_media=
    ... from drivers not being included in the Solaris install media. ... Jumpstart environment is to modify the miniroot that is used during the ... Locate this directory on your jumpstart server and backup your ...
    (comp.unix.solaris)
  • [2.6.30.1] Significant latency playing video file from NFS4 share
    ... No significant other processes running on either the client or the ... latencytop on the server does not show any significant latencies. ... # CPUFreq processor drivers ... # Core Netfilter Configuration ...
    (Linux-Kernel)
  • Re: BSoD on 2003 TS - varying error codes
    ... With regards to your note about Printer Drivers, I may be able to perform ... TS and are known to crash the printer spooler or the whole server. ... parameter3 00000000, parameter4 ffffffff. ...
    (microsoft.public.windows.terminal_services)