Hello
I've just updated to Samba version 3.0.22 (previously v3.0.4a)
and get the following problem:
rpcclient enumdrivers fails with WERR_UNKNOWN_PRINTER_DRIVER
while rpcclient getdriver works just fine! Can this be?
$ rpcclient -c enumdrivers GUTENBERG
Password:
result was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Urs-Jakob Rueetschi wrote:
Hello
I've just updated to Samba version 3.0.22 (previously v3.0.4a)
and get the following problem:
rpcclient enumdrivers fails with WERR_UNKNOWN_PRINTER_DRIVER
while rpcclient getdriver works just fine! Can this
Gerald (Jerry) Carter wrote:
Urs-Jakob Rueetschi wrote:
Hello
I've just updated to Samba version 3.0.22 (previously v3.0.4a)
and get the following problem:
rpcclient enumdrivers fails with WERR_UNKNOWN_PRINTER_DRIVER
while rpcclient getdriver works just fine! Can this be?
$ rpcclient -c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Novosielski wrote:
EnumDrivers() does take a printer an as argument IIRC.
Not so, according to 'man rpcclient':
My stupid typing again. It'll get me in deep trouble one day
Meant to say does not take a printername
This is another one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
Ryan Novosielski wrote:
EnumDrivers() does take a printer an as argument IIRC.
Not so, according to 'man rpcclient':
My stupid typing again. It'll get me in deep trouble one day
Meant to say does not take a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Novosielski wrote:
Not personally familiar with doing traces -- I'm assuming I would use
tcpdump to capture the output and then run a trace on the output with
ethereal, or can it be used to do the entire thing? Will it still work
if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerald (Jerry) Carter wrote:
Ryan Novosielski wrote:
Not personally familiar with doing traces -- I'm assuming I would use
tcpdump to capture the output and then run a trace on the output with
ethereal, or can it be used to do the entire thing?
