cancel
Showing results for 
Search instead for 
Did you mean: 

Users unable to print => only after two times of rebooting

alkafri
Occasional Contributor

Users unable to print => only after two times of rebooting

Hello,

we are using 2 kinds of Pulse Connection.
1-Admin_vpn 
2-always_on => with "Lock down" Option.

it works perfectly but by most of always_on Users, when they come back to work on office (localy in Network), they cannot printing anything to our network printers.
the users has to reboot thair PCs 2times to be able to print again (kind of looks like the VPN client is still holding some type of service or connection which then blcoks printing).
our users does not have admin rights locally to stop and start services.

Admin_vpn users does not have any print-Problem.


looking for some help pls
thanks

6 REPLIES 6
zanyterp
Moderator

Re: Users unable to print => only after two times of rebooting

did you unblock the print spooler in your lockdown exception list?
alkafri
Occasional Contributor

Re: Users unable to print => only after two times of rebooting

Hi,

 

yes, Direction Outrbound=>      <%windir%>\Sysnative\spoolsv.e...   Action is allowed

our environment support only 64-bit operating systems.

 

thx

 

zanyterp
Moderator

Re: Users unable to print => only after two times of rebooting

ok; thank you
if you have not done so, i would recommend opening a case with our support team
DerFalk
Contributor

Re: Users unable to print => only after two times of rebooting

we also have to whitelist the 32-bit to make it work

zanyterp
Moderator

Re: Users unable to print => only after two times of rebooting

thank you for adding that as an option/help, @DerFalk
alkafri
Occasional Contributor

Re: Users unable to print => only after two times of rebooting

i will try it.

 

thank you