search for: print_server_name

...s : SUCCESS - 0. I have applied the following fix after researching similar errors in the samba archives to no avail Procedure: 1. Edit the registry observing usual caution. 2. Locate the key HKEY_CURRENT_USER\Printers\DevModePerUser 3. Remove all VALUES for Network printers of the form: \<print_server_name ><printer_queue_name> 4. Locate the key HKEY_CURRENT_USER\Printers\DevModes2 5. Remove all VALUES for Network printers of the form: \<print_server_name><printer_queue_name> I still get these errors on the client Can anyone help further Thanks in advance Steve

A small update: Fiddled some more with Windows 10 and that works, too. Windows 7 still doesn't see the printer in Print Management, not even on a second, freshly installed client. I have set up the printer now from Windows 8.1 and configured some printer preferences and installed the printer on a Windows 7 client. That works. However, I would really like to configure the printer form Windows

...please open a bug report against Samba 4.7 (see https://wiki.samba.org/index.php/Bug_Reporting) and include the information from this thread and a level 10 debug log. Thanks. As a workaround, on Win 7 you can still assign drivers without using the Print Management console: - Start / Run - Enter \\print_server_name\, click "OK" - Press the "View remote printers" button There you can right-click to printers and manage them same as in the console. Win7 was the last version where you can manage printer this way. Anyway, please open the bug report. Regards, Marc

Hi, I have setup samba server on my linux box (Fedora Core 4 with latest samba, just updated via RHN) and has configured file sharing via samba for this server and connecting to it from my windows xp box. So far, everything works fine and it is very fast. Then, I configured a printer, and shared it via samba. And, I can see+connect to it from Windows XP and can even print. But, everything

...during the bug report. :-) > > For anyone finding this via Google, as Marc pointed out, the > workaround seems to be: > > As a workaround, on Win 7 you can still assign drivers > without using > > the Print Management console: > > - Start / Run > > - Enter \\print_server_name\, click "OK" > > - Press the "View remote printers" button There you can > right-click to > > printers and manage them same as in the console. Win7 was the last > > version where you can manage printer this way. > Alternatively, you can use Windows 10...