C
Cary Shultz
Howdy! Howdy!
This is in continutaion to my previous post from last
week. it was getting rather long so I decided to start
another one. thank you to Vera for following this for the
past several days.
In a nutshell, it looks like when there are several larger
print jobs within a few minutes of each other the TS
freezes, which in turn causes the clients to freeze. I
then have to manually 'push the button' as the TS will sit
there for a good chunk of time.
Anyway, I believe that I have narrowed it down to the
printing issue. This seems to be the only thing in common.
Except for replacing all of the print drivers on the TS
and then on the clients, is there anything that I can do
to try to stop this freezing? I ask as the two remotes
Sites are a bit away from here ( Blacksburg and Richmond -
I am in Roanoke ) and I can not trust the users to do
this....
I have been looking at the ntprint.inf file on the TS but
am not really sure for what I am looking. I have been
doing a lot of research on this and I realize how
important it is for the printer on the client to match
exactly the printer in the ntprint.inf file.
Here is something to ponder: there was a 681 page print
job at 11:32 this morning. When I asked my contact at the
company having this issue she contacted the 'guilty
party'. It turns out that it was 'only' 168 pages or so.
We are seeing this quite often where the log indicates 300
pages ( for example ) and it is really only 60 ( for
example ). This tells me that something ain't right in
Terminal Server land. There are really no event ids to
speak of ( cleared up mostly all the 1000 errors that we
were all of a sudden getting by applying the two patches
from MS - Thank you, Vera! ). Has anyone seen this???
Thank you all!
Happy Thanksgiving!
Cary
This is in continutaion to my previous post from last
week. it was getting rather long so I decided to start
another one. thank you to Vera for following this for the
past several days.
In a nutshell, it looks like when there are several larger
print jobs within a few minutes of each other the TS
freezes, which in turn causes the clients to freeze. I
then have to manually 'push the button' as the TS will sit
there for a good chunk of time.
Anyway, I believe that I have narrowed it down to the
printing issue. This seems to be the only thing in common.
Except for replacing all of the print drivers on the TS
and then on the clients, is there anything that I can do
to try to stop this freezing? I ask as the two remotes
Sites are a bit away from here ( Blacksburg and Richmond -
I am in Roanoke ) and I can not trust the users to do
this....
I have been looking at the ntprint.inf file on the TS but
am not really sure for what I am looking. I have been
doing a lot of research on this and I realize how
important it is for the printer on the client to match
exactly the printer in the ntprint.inf file.
Here is something to ponder: there was a 681 page print
job at 11:32 this morning. When I asked my contact at the
company having this issue she contacted the 'guilty
party'. It turns out that it was 'only' 168 pages or so.
We are seeing this quite often where the log indicates 300
pages ( for example ) and it is really only 60 ( for
example ). This tells me that something ain't right in
Terminal Server land. There are really no event ids to
speak of ( cleared up mostly all the 1000 errors that we
were all of a sudden getting by applying the two patches
from MS - Thank you, Vera! ). Has anyone seen this???
Thank you all!
Happy Thanksgiving!
Cary