search for: enumforms

...0 max_recv: 4280 373 1.066368 192.168.40.46 192.168.40.2 SPOOLSS OpenPrinterEx request, \\CORN\rawPrinter 374 1.066719 192.168.40.2 192.168.40.46 SPOOLSS OpenPrinterEx response 375 1.069332 192.168.40.46 192.168.40.2 SPOOLSS EnumForms request, level 2 376 1.069450 192.168.40.2 192.168.40.46 SPOOLSS EnumForms response, level 2[Malformed Packet] 377 1.072267 192.168.40.46 192.168.40.2 SPOOLSS EnumForms request, level 1 378 1.072429 192.168.40.2 192.168.40.46...

..., Everyone -- How can I create a custom printer form for use on the printers shared by Samba? I tried to add a printer form via the "Server Properties" gizmo from a Win2k Pro client, but I get "Form formname could not be added. Operation could not be completed." When I do an enumforms <printername> via rpcclient to the Samba server, I get an NT_STATUS_UNSUCCESSFUL. If I do this against our WinNT 4.0 server with printers, it gives me the list. Is there some funky hack I can use? This is becoming critical because I NEED to move the printers on this server to something els...

...et a custom form to a tray (such as a form named "Letterhead" for the letterhead, "Letter" for plain, etc). I understand (maybe wrongly) that paper form support is in Samba, but when I use rpcclient to work with them, nothing works--I am returned the following: rpcclient $> enumforms L201-Lab rpc_api_pipe: cmd 26 on pipe 70ed failed to return data. result was NT_STATUS_UNSUCCESSFUL I also tried to work with the forms via the "Server Properties" of my print server via Network Neighborhood (or My Network Places), and I was still unsuccessful (no surprise there to me :)...

...> about that bug, but maybe the Subject was not taken by you. The Samba > 2.2.5 Printing subsystem misses Paper Forms larger than the DIN A2 > format, and I was not able to add forms through the "Server Properties" > and also I did not found out how to use the addform/setform/enumforms > rpcclient commands. I've got it in my queue. I'm working on exporting printer settings via the registry RPC's right now to help in debugging problems like this. As soon as I get done (hopefully this week), I'm back on fixing spoolss bugs. These two are first on the list....

I have heard something about a 'known bug in 2.2.4' so this might already be known. If so, I just want to get confirmation... I have a new samba 2.2.4 running on a RH7.2 box, running solely as printserv. The spoolss printing functionality is working fine: uploading drivers works ok (aside from a few APW quirks if you change drivers). I'm using CUPS as unix printing backend. The

I'm currently having a problem with the new released Samba 2.2.5: I cannot print anymore on my shared printer. What is strange is that It worked fine with samba 2.2.4, but now I got an access denied whenever I try to access the printer... /var/spool/lpd/samba is chmod 777 and the username is in the group lp Here is part of my smb.conf: [global] workgroup = HOME netbios name =