Slow local printing on Terminal Server
#1
Slow local printing on Terminal Server
Got the following problem at the moment.
Windows 2000 Advanced Server, remote XP clients on ISDN (128k) via terminal services
Clients log in ok and automatically create print queues, the job spools ok to the server but takes ages to get back to the local printer. Quite often takes 10 minutes to print or drops the job altogether.
Was fine on Citrix on NT4, but slow as a dog on Windows 2000.
Any pointers appreciated.
Windows 2000 Advanced Server, remote XP clients on ISDN (128k) via terminal services
Clients log in ok and automatically create print queues, the job spools ok to the server but takes ages to get back to the local printer. Quite often takes 10 minutes to print or drops the job altogether.
Was fine on Citrix on NT4, but slow as a dog on Windows 2000.
Any pointers appreciated.
#4
Yes was ICA before now RDP. Various size print jobs, doesn't seem dependant on the size, I've watched 10Mb prints spool to the server before evaporating, but so have 30k ones. It's behaving better after sp4 i.e. fairly clean event logs, was riddled with errors before that. If it was reliable but slow, then I could accept it, but the punters are obviously seeing it as a step backwards. Other than that, general performance is fine e.g. in Outlook.
Stumped
Stumped
#5
Scooby Regular
What connection are the local printers? LPT or USB?
Are the drivers on the 2000 server being matched OK with the remote clients?
It's been a few years since I worked on thin-client (spent 2 years doing nothing but). It was mainly Citrix solutions though.
Stefan
Are the drivers on the 2000 server being matched OK with the remote clients?
It's been a few years since I worked on thin-client (spent 2 years doing nothing but). It was mainly Citrix solutions though.
Stefan
#6
LPT printers, I think the drivers are ok as you get an event log error when someone connects with an unknown printer e.g. deskjet 980 and the virtual print queue doesn't get created. Networked printers print instantly, so it's sending back the raw data to the local printer that's the problem. Pretty hard to troubleshoot as it's out of your hands at that point. Maybe the LPT port is timing out. I've been assuming my server was fecked till now, but I'll look more into the client side tomorrow as I reckon the server is doing its bit.
#7
Scooby Regular
There's an issue in general with local printing and the LPT timeout. Not sure if it's relevant on TS.
You could try this - http://www.resortdata.com/Customers/...OS/K000036.htm
Stefan
You could try this - http://www.resortdata.com/Customers/...OS/K000036.htm
Stefan
Trending Topics
#8
I saw that article today, but I took it to mean that the port would time out sooner if I reduce the value, so I dismissed it. Having re-read it I think it means the opposite. I'll certainly be giving it a go tomorrow - with a value of -3000 so they just have to think about printing and it's there. Sorry I digress ....... the 15 years old Balvenie is taking hold! Cheers for the pointer.
Fopp
Fopp
#9
Stefan - looks like it was just bandwidth - moving from Citrix and NT4/Office 97 at 800x600 to XP and Office XP at 1024x768 on Terminal Services on the same connection was just too much. Dropped the screen res back down to 800x600 again and it's usable again. Not great, but it works. No chance of broadband for these very remote users for some time.
Cheers
Fopp
Cheers
Fopp
Thread
Thread Starter
Forum
Replies
Last Post
KK3960
General Technical
3
07 October 2015 12:33 PM