Mr. Ferguson,
I wanted to thank you for the support; as I was having a rather esoteric
problem with a local printer on our network I felt it only common courtesy
to try any tips I saw that seemed even vaguely relevant prior to posting my
question and request for help. This tip absolutely did not seem relevant,
but it worked anyway. If you have nothing else to do at the moment or are
simply interested in providing an answer, here's the problem I was running
into. I think you'll see why I didn't think this would be relevant. I would
LOVE to hear the explanation behind this.
I manage a small (36 nodes) network at a downtown Denver hotel. One of the
PCs is located in the lobby for the use of the concierge and any guests who
wish to use it. The concierge's network account has limited access, with no
network access, but he is set up as a local machine administrator (necessary
due to a franchise hotel information system program he uses as part of his
job). The PC is an IBM Netvista, the printer is a Lexmark M410.
The problem arose some time ago when the printer stopped working. The user
(lzittle) was unable to print anything to the printer, and removing and
reinstalling the printer (using the generic MS drivers and the latest
Lexmark drivers) did nothing. The PC was perfectly capable of automatically
finding and installing the printer, but no test page or prints of any kind
were allowed. The twist to this is that I was able to log on as a different
network user (one who had not yet been set up on the machine, and thus had
no "special" rights) and print with no difficulty.
Given that it seemed to be a user-related issue, I renamed the user's
profile (lzittle.old) and recreated his profile, importing his various
settings. This did fix the issue for a limited time (perhaps two weeks) but
the problem recently resurfaced, prompting my search on the newsgroup. Your
tip fixed it, but it baffles my mind how what seems to be a user-related
issue is solved by a machine-related fix?
