Y
Yann LEZY
Hello World !
I ran into this weird problem this morning :
- Win2k3 server sharing a laserjet printer connected to LPT1 on the network.
Security settings set to "everybody : print / manage cue / etc...kinda full
control".
- Vista laptop with local administrator profile logged in (no network / AD
user.)
1st thing is : I cant connect the server without having to log on the
server. I thought entering \\192.168.x.y\ would simply display the printers.
It doesn't. Nevermind, I created a dedicated user on the server.
So When I log onto the server with that username and pwd, _clic 'remember
password' checkbox_, I see the printer. Clic connect and it's now installed
on my vista laptop. I can print and everything works perfectly.
My real problem comes when the laptop get rebooted for some reason :
Everything seems to works fine until I decide to print. The document gets
into the spooler as if everything's ok... but nothing happens. The printer
won't print. Then after some time, it would raise an error 'couldn't
print'... good.
I can make it print by logging onto the server... say start/run :
\\192.168.x.y enter login and pwd... the printer now prints.
I did the same with the server administrator account. won't change anything.
I even manually inserted the server/login/pwd into the User account / manage
network password to _force_ the os to remember the authentication info...
that didn't work either.
the Vista Network profile is set to "private" and has folders and printers
shares options checked.
My question is "What can I do to have Vista relog automatically to the
server so that printer works without any user action at reboot ?"
I thought about setting an empty shared folder as a permanent network folder
and have it reconnect at reboot as a workaround but if anybody knows the
proper way to solve my problem, then I'll happily accept it
thanks for any help.
Yann
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 4466 (20090929) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.com
I ran into this weird problem this morning :
- Win2k3 server sharing a laserjet printer connected to LPT1 on the network.
Security settings set to "everybody : print / manage cue / etc...kinda full
control".
- Vista laptop with local administrator profile logged in (no network / AD
user.)
1st thing is : I cant connect the server without having to log on the
server. I thought entering \\192.168.x.y\ would simply display the printers.
It doesn't. Nevermind, I created a dedicated user on the server.
So When I log onto the server with that username and pwd, _clic 'remember
password' checkbox_, I see the printer. Clic connect and it's now installed
on my vista laptop. I can print and everything works perfectly.
My real problem comes when the laptop get rebooted for some reason :
Everything seems to works fine until I decide to print. The document gets
into the spooler as if everything's ok... but nothing happens. The printer
won't print. Then after some time, it would raise an error 'couldn't
print'... good.
I can make it print by logging onto the server... say start/run :
\\192.168.x.y enter login and pwd... the printer now prints.
I did the same with the server administrator account. won't change anything.
I even manually inserted the server/login/pwd into the User account / manage
network password to _force_ the os to remember the authentication info...
that didn't work either.
the Vista Network profile is set to "private" and has folders and printers
shares options checked.
My question is "What can I do to have Vista relog automatically to the
server so that printer works without any user action at reboot ?"
I thought about setting an empty shared folder as a permanent network folder
and have it reconnect at reboot as a workaround but if anybody knows the
proper way to solve my problem, then I'll happily accept it
thanks for any help.
Yann
__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 4466 (20090929) __________
Le message a été vérifié par ESET NOD32 Antivirus.
http://www.eset.com