Hello, Adding to my previous msg, debug level 7 finally gave me some output. In my smbd.log i am seeing the following whenever i try to upload printer drivers: getpeername failed. error was transport endpoint is not connected I've looked in to other methods of doing this, imprints doesn't seem to be supported, cupsaddsmb won't work with vendor supplied drivers, and to date i haven't been brave enough to try out rpcclient, i'm not sure of the syntax and have concerns about the case of these drivers. So, i need to get this working. If anyone has seen this error i'd appreciate any suggestions. Thanks. Dave.
Dale Schroeder
2007-Mar-30 19:10 UTC
ham,[Samba] error was re: disappearing printer drivers
Dave, See if either of these two links are able to help you: http://readlist.com/lists/lists.samba.org/samba/0/1622.html http://blog.aplpi.com/ Good luck, Dale Dave wrote:> Hello, > Adding to my previous msg, debug level 7 finally gave me some > output. In my smbd.log i am seeing the following whenever i try to > upload printer drivers: > > getpeername failed. error was transport endpoint is not connected > > I've looked in to other methods of doing this, imprints doesn't seem > to be supported, cupsaddsmb won't work with vendor supplied drivers, > and to date i haven't been brave enough to try out rpcclient, i'm not > sure of the syntax and have concerns about the case of these drivers. > So, i need to get this working. If anyone has seen this error i'd > appreciate any suggestions. > Thanks. > Dave.
On Friday 30 March 2007, Dave wrote:> I've looked in to other methods of doing this, imprints doesn't seem to be > supported, cupsaddsmb won't work with vendor supplied drivers, and to date > i haven't been brave enough to try out rpcclient, i'm not sure of the > syntax and have concerns about the case of these drivers. So, i need to get > this working. If anyone has seen this error i'd appreciate any suggestions.To install vendor supplied Windows drivers from Windows clients using cups and samba create a raw queue in cups for the printer, reload samba so that it is aware of the printer. Make sure that "use client driver" is the default value of "no" (testparm -sv | grep 'use client'). Then carefully follow the instructions in the classical print section of the howto (yes, works just fine for cups): http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/classicalprinting.html#id358732 If you have the proper rights all should be fine. Chris