Lizzyosully
asked on
Remote Desktop / Print spooler
We have a print server with approx 15 different printers installed and shared out on this server. The Os is server 2003 SP2. This server also runs McAfee EPO AV Software.
I't will not let me remote desktop in to this server, then if I restart the print spooler it will let me RD to this server. Then randomly, the same thing happens again and I have to repeate restarting the print spooler. Have tried various things like uninstalling A/V, In terminal services Configuration, unticking connect client printers at logon. etc...
Any ideas would be appriciated.
I't will not let me remote desktop in to this server, then if I restart the print spooler it will let me RD to this server. Then randomly, the same thing happens again and I have to repeate restarting the print spooler. Have tried various things like uninstalling A/V, In terminal services Configuration, unticking connect client printers at logon. etc...
Any ideas would be appriciated.
ASKER
Thanks clesius but I already tried that option, ticked and unticked.
Do you get any kind of error message when trying to connect?
Also, are you setup in 'Remote Desktop for Administration' mode - or actual Terminal Server mode? I don't like to assume on this.
Never seen this either, but I wonder also if you have any older WinNT 4 based print drivers (that use kernel mode) and are very dangerous. I suppose they could be causing a problem with you connecting. Try going under Printers and Faxes on the 2003 Server - and click File > Server Properties > Drivers. If any say Windows NT 4 - it's a kernel mode driver. Try removing these, restarting the print spooler, and try again.
And one last suggestion, have you tried temporarily disabling printers period on the SERVER side configuration for TS? START > Administrative Tools (or via Control Panel) > Terminal Services Configuration > Connections > RIGHT-CLICK on RDP-TCP > Properties > Client Settings - make sure 'Use connection settings from user settings' is UNCHECKED - and also uncheck 'Connect client printers at logon' and 'Default to main client printer'. See what that does just temporarily.
Really interested to know though if you get an error message or not when trying to connect. Try doing a raw connection to the TS port from a command prompt (RUN > CMD > ENTER) .. then 'telnet serveriphere 3389' ... your prompt should clear the command window and blink the cursor at the top. If it fails connection, then something else might be going on.
Also, are you setup in 'Remote Desktop for Administration' mode - or actual Terminal Server mode? I don't like to assume on this.
Never seen this either, but I wonder also if you have any older WinNT 4 based print drivers (that use kernel mode) and are very dangerous. I suppose they could be causing a problem with you connecting. Try going under Printers and Faxes on the 2003 Server - and click File > Server Properties > Drivers. If any say Windows NT 4 - it's a kernel mode driver. Try removing these, restarting the print spooler, and try again.
And one last suggestion, have you tried temporarily disabling printers period on the SERVER side configuration for TS? START > Administrative Tools (or via Control Panel) > Terminal Services Configuration > Connections > RIGHT-CLICK on RDP-TCP > Properties > Client Settings - make sure 'Use connection settings from user settings' is UNCHECKED - and also uncheck 'Connect client printers at logon' and 'Default to main client printer'. See what that does just temporarily.
Really interested to know though if you get an error message or not when trying to connect. Try doing a raw connection to the TS port from a command prompt (RUN > CMD > ENTER) .. then 'telnet serveriphere 3389' ... your prompt should clear the command window and blink the cursor at the top. If it fails connection, then something else might be going on.
Have you tried other users?
Lizzy, have you tried any of the above?
ASKER
Hi Kmruss
Thank you very much for your detailed answer. There was a number of old NT drivers still installed and I removed them yesterday. All has been working well so far, I would like to wait another day before I can definalty say that was the correct answer as I have gone a day or so before with all being ok and then the problem reoccurs again. Will get back to you in a day or so and let you know.
Thank you very much for your detailed answer. There was a number of old NT drivers still installed and I removed them yesterday. All has been working well so far, I would like to wait another day before I can definalty say that was the correct answer as I have gone a day or so before with all being ok and then the problem reoccurs again. Will get back to you in a day or so and let you know.
Great - let me know if that worked for you. Good to know for my reference too - as I had never seen it actually not allow logon - however I learned long ago the hard way (someone else told me too I think) not to use any of the older NT4 based drivers.
ASKER
HI Kmruss
Unfortunalty yesterday it happened again not being able to connect to the print server via remote desktop. I have now tried the second suggestion on your post will get back and let you know how I get on.
Unfortunalty yesterday it happened again not being able to connect to the print server via remote desktop. I have now tried the second suggestion on your post will get back and let you know how I get on.
Okay Lizzy - two things: Let me know if you get an error message at all (you should get SOME error message eventually - even if it's the long 3 answer one about 'check with your administrator, etc.') - and let me know how the telnet does.
I'm wondering if you're having a similar issue with your 'metric' setup like I did - you don't have more than one default gateway specified do you ?
Also, have you tried pinging the server's IP address to see if the server's internet connection is cutting out? (or yours?) ping serverip -w 3000 -t (all lower-case will ping until you hit CTRL-C and with a 3 second timeout which should show any excessive latency/lag)
I'm wondering if you're having a similar issue with your 'metric' setup like I did - you don't have more than one default gateway specified do you ?
Also, have you tried pinging the server's IP address to see if the server's internet connection is cutting out? (or yours?) ping serverip -w 3000 -t (all lower-case will ping until you hit CTRL-C and with a 3 second timeout which should show any excessive latency/lag)
ASKER
Hi There
Just wanted to let you know how strange and bizzare the world of windows can be sometimes.
I know it has been a while since I have posted this question but here laid the problem.
I changed the settings for the screen resoulution and it has not happened since.
Does anyone this this is strange apart from me?
Just wanted to let you know how strange and bizzare the world of windows can be sometimes.
I know it has been a while since I have posted this question but here laid the problem.
I changed the settings for the screen resoulution and it has not happened since.
Does anyone this this is strange apart from me?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Edit your Remote Desktop Connection properties. Go to the "Local Resources" tab and uncheck the "Printers" box under "Local devices and resources".
Let me know how it goes.