J
Jason Hodge
I have a customer who is running a Windows 2000 SBS
(Service Pack 3) server with Terminal Services set up in
Application Server Mode. The problem I am having is as
follows:
Occasionally printers get "stuck", and won't delete. They
just sit there after the user logs off, and cannot be
deleted until the server is restarted. Then another user
connects, and the ts port that the "stuck" printer is
assigned is reassigned to the new users, resulting in two
printers being assigned to the same ts port (eg. ts006).
The stuck printer is still stuck, unable to be deleted,
and the new printer can't print. The job appears in the
print queue, then just sits there, no error messages, and
can be deleted fine. I have a number of TS servers out
there, and this is the only one I'm having a problem like
this on. I've been beating my head on a wall for a while
now, and need some fresh input. Anyone have any ideas?
Thanks.
Jason Hodge
Centurion Computer Systems of Tampa, Inc.
(e-mail address removed)
(Service Pack 3) server with Terminal Services set up in
Application Server Mode. The problem I am having is as
follows:
Occasionally printers get "stuck", and won't delete. They
just sit there after the user logs off, and cannot be
deleted until the server is restarted. Then another user
connects, and the ts port that the "stuck" printer is
assigned is reassigned to the new users, resulting in two
printers being assigned to the same ts port (eg. ts006).
The stuck printer is still stuck, unable to be deleted,
and the new printer can't print. The job appears in the
print queue, then just sits there, no error messages, and
can be deleted fine. I have a number of TS servers out
there, and this is the only one I'm having a problem like
this on. I've been beating my head on a wall for a while
now, and need some fresh input. Anyone have any ideas?
Thanks.
Jason Hodge
Centurion Computer Systems of Tampa, Inc.
(e-mail address removed)