A Windows 2000 network printer...

Soldato
Joined
4 Jun 2005
Posts
3,781
When I install a network printer it requires authentication so I enter a user and pass and all is fine.

Once the computer is rebooted (that I installed the printer on) I have to double click the printer so that it connects otherwise it wont connect and I will have no printer.

Afaik, this is the only method I can use right now. On NT, you just share the printer and turn on the print server. There was no need for any logging in or anything.

Has anyone had this same situation, if so do you know a method where it can just be a simple *turn on server* and then when you turn on the other computers the printer will already be connected rather than having to double click the icon..?
 
are you setting the printer up so it directly connects to the print server, like the JetDirect or Intel Pro PS? Or are you going via a server first where the printer is installed on?
 
hybrid said:
are you setting the printer up so it directly connects to the print server, like the JetDirect or Intel Pro PS? Or are you going via a server first where the printer is installed on?

Through a server were the printer is installed on.
 
right clcik printer, sharing, enable.. choose name..


go to different pc (networked to this one)

start, run

\\firstpcname\printername

click , yes, ok whatever when they come up, and printer is mapped..
 
The 'loggin in' occurs because the credentials on the 'client' pc do not exist or are not the same as credentials on the 'server' pc. either change both usernames and passwords to be the same, or add a new user to the 'server' pc with the same username/password as the 'client'.
 
bledd. said:
right clcik printer, sharing, enable.. choose name..


go to different pc (networked to this one)

start, run

\\firstpcname\printername

click , yes, ok whatever when they come up, and printer is mapped..


Yes but sometimes it fails to connect. After a reboot that is.

csmager said:
The 'loggin in' occurs because the credentials on the 'client' pc do not exist or are not the same as credentials on the 'server' pc. either change both usernames and passwords to be the same, or add a new user to the 'server' pc with the same username/password as the 'client'.

Thats what I thought because thats how its meant to be. I'll just keep doing trial and error. Must be doing something wrong!
 
The source of the problem was permissions under security, after allowing certain controls it works fine now :)

Thanks for help anyway guys ^^
 
Back
Top Bottom