Networks Remote Desktop Connection Crashes Print Spooler - SOLVED

Discussion in 'Hardware' started by Arthur2Sheds, 20 Mar 2006.

  1. Arthur2Sheds

    Arthur2Sheds Jackson

    Joined:
    19 May 2003
    Posts:
    817
    Likes Received:
    1
    We are running Windows Server 2003 with XP Pro for the workstations on our network.

    Everything is running fine until I decide to remote into the server from one of the workstations. I can get onto the server, do what I need, and close the session. Immediately the print spooler crashes on the server. If I remote in again, start the print spooler service, and close the session, all is fine again.

    If I look in the Printers folder on the server, I see the 7 network printers that should be installed. What's weird is I also see 7 duplicate entries for the same printers, this time with the computer name of the workstation I'm remoting from attached to the printer name. For example:

    Printers Folder

    Printer 1 on ServerName
    Printer 1 on WorkstationName
    Printer 2 on ServerName
    Printer 2 on WorkstationName
    etc.



    Any ideas on how to stop this?

    Thanks!
     
    Last edited: 20 Mar 2006
  2. CaseyBlackburn

    CaseyBlackburn Network Techie

    Joined:
    27 Jul 2004
    Posts:
    1,846
    Likes Received:
    0
    I believe the duplicates are from the settings you use in connecting, in the Options mode, click onto the Local Resources tab, and unclick printers. That should solve that, I have no clue about the other though.
     
  3. Arthur2Sheds

    Arthur2Sheds Jackson

    Joined:
    19 May 2003
    Posts:
    817
    Likes Received:
    1
    You're a genius!

    There are apparently two settings for this. One is on the server itself under Administrative Tools, and one on the logon box when you first attempt to connect to the server with the Remote Desktop Connection.

    I had already done one of them, so doing the other fixed both problems.

    Thanks!
     
  4. CaseyBlackburn

    CaseyBlackburn Network Techie

    Joined:
    27 Jul 2004
    Posts:
    1,846
    Likes Received:
    0
    Glad it is sorted, and I dare not call myself a genius, I just know my way around, and explore all the possible settings of every piece of software I try and see what they do.
     
  5. Robert Gosney

    Robert Gosney What's a Dremel?

    Joined:
    2 Mar 2007
    Posts:
    2
    Likes Received:
    0
    In your post you stated there is a place in the Administrative Tools to cause an effect on Remote Desktop printers. Are you referring to the Terminal Server Configuration Snap in module or someplace else. Please bear in mind, I am looking at Windows 2000 Server, not 2003, but I have had the same issues the the Remote Desktop connections to the Terminal server.

    Thanks! Bob Gosney
     
  6. Arthur2Sheds

    Arthur2Sheds Jackson

    Joined:
    19 May 2003
    Posts:
    817
    Likes Received:
    1
    Welcome to the forums, Bob Gosney!

    Yes, I was referring to the Terminal Server Configuration doobob. With 'Connections' selected on the left side, I right-clicked my RDP-Tcp connection in the main panel and under Properties went to the Client Settings tab. I had unchecked the 'Connect client printers at logon' box.

    So are you saying you're still having the same issues even with both of these options correctly set? Maybe we can help you troubleshoot further with some more information.

    Good luck!
     
  7. Robert Gosney

    Robert Gosney What's a Dremel?

    Joined:
    2 Mar 2007
    Posts:
    2
    Likes Received:
    0
    Thanks!

    Thanks, but having used the two methods you outlined, it is all corrected!

    Once again, thank you for the input and guidance!!

    Bob Gosney
     
  8. Arthur2Sheds

    Arthur2Sheds Jackson

    Joined:
    19 May 2003
    Posts:
    817
    Likes Received:
    1
    Glad you're all sorted. Stick around!
     
Tags:

Share This Page