Is there something that I can do from the Solaris print client to help resolve Windows print server
I received the following request from one of the application admins:
"They are *still* having issues with xxx... This seems to be a continuation of problems we've had for several months now. He asked if we would look around and see if we see anything strange from this morning. *Something* brought xxx down at about 8:27 a.m. this morning and again at 9:30 a.m. this morning. He *thinks* whatever it is is coming from a unix-based or mac-based system, but doesn't have any idea what the trigger is; whether it's a huge print job, or some weird code associated with the print job, or what... Anyway, he asked if we'd try
"They are *still* having issues with xxx... This seems to be a continuation of problems we've had for several months now. He asked if we would look around and see if we see anything strange from this morning. *Something* brought xxx down at about 8:27 a.m. this morning and again at 9:30 a.m. this morning. He *thinks* whatever it is is coming from a unix-based or mac-based system, but doesn't have any idea what the trigger is; whether it's a huge print job, or some weird code associated with the print job, or what... Anyway, he asked if we'd try
0