Network printer access code error

[Hoss]

This printer on a network had to be unplugged, server was rebooted. I assume no setting were messed with.



A client pc using Win ME can't print to a networked printer. Deleted then added the printer. Sees it fine on the network. (Win NT on the server) Upon printing - an error message comes up saying "access code error." From the server I have enabled sharing and given all pc's full access. The server and all other pc's can print to this printer fine. The printer then sets to offline.
To the right of the printer it states something like "user intervention required."

What else can I try?

Thanks so much for any help

[Trinity]

To clarify: The printer is hooked to the server and does not have it's own IP, correct?

Is there a reason the workstation is running ME? Anyway to upgrade it to 98, NT, or XP?

[Ace]

My only guess is it's a user/password thing.

Can you go //servername/printername from your address bar on the ME machine?

My guess is you'll get the same kind of error. ME and (98) for that matter are retarded if the server comes back that the user/password is wrong, it doesn't prompt you for it again. I'd guess it's something silly like on the ME machine it's trying with a username and blank password and on the server you have a username with a set password.

[law.of.averages]

Some places create a special user 'printer' and set the ME printer to connect as that user...

Other places create a user on the server with the same name / password as the ME user...

You can also change the printer share parameters on the server, but I'd need more details about the server to walk you through that one

[BeerNut]

This may sound a bit rediculous but:
Is the printer name 8 characters or less (no spaces)?

I ran into this problem a little while ago using a 98 machine... ME might have same problem. I could see the printer fine, but got an error when sending a job.
When I renamed the printer (for the network share) to a name under 8 characters, and reconnected to it on the new share, it worked like a charm.

[Hoss]

Appreciate the help. This is a small office for a place I used to work. Their computer guy left. I'm pretty much a neophyte when it comes to business networks.

The printer is connected to the server, not another pc.
Everything was working fine but someone threw a bottle through the window and got glass everywhere. They disconnected the printer and rebooted the server for some reason. I don't know what settings were messed with as they tried to fix it themselves after their pc's wouldn't print.
What "parameters" were you refering to Law?
I pinged the server to all the pc's and they were fine.
I gave full permission for both printers to all pc's.
I thought the password might be it too but they say they log on fine using the same pass they always have.
One pc has Me, another has 2000 and another had XP pro lol.
Any help is sure appreciated. I'm going back over there Mon.

[law.of.averages]

Is it by chance a USB printer? It may not be shared anymore if they didn't connect it to the exact same port that it was in.

[Hoss]

Yes it is usb

Beer it has a long printer name. Elsmithdispatch01

but it worked fine before...

[BeerNut]

Hoss,
Have you re-installed the printer completely at the PC having the problem?
If not, try this... Delete the printer in question at the ME machine, add-it new by browsing to it on the network, and for good measure capture the next LPT port available on the machine and assign it to the network path for the printer (should be LPT1 if there are no local printers).

See this thread:
http://discussions.virtualdr.com/showthread.php?t=35924

It looks like simply re-installing the printer should fix it... I personally like assigning an LPT port to the older 95 kernel OS's (95, 98, ME), as it solves printing problems in lower level and older programs.