As an updatee to my last post, things are still not working! The drivers
did get added but I'm still not sure whether I achieved this via the Add
Printer Wizard or despite error messages the rpcclient adddriver did
work. I did wonder if the lsa_io_sec_qos: length c does not match size 8
error is because the printer name is too long, especially as when I
tried a shorter name such as HP2300 - with no spaces the files did end
up in the correct directory!!
I therefore attempted the setdriver command and still get error messages
such as WERR_ACCESS_DENIED. Looking at Google I can see lots of posts
and the suggestion that use client driver = yes in smb.conf should be
altered to use client driver = no . Well I tried this with no success
and even tried once again with the add printer wizard but this time I am
unable to change any of the properties. I also tried changing the
permissions on the /etc/cups/printcap file but it made no difference.
I am starting to conclude that either these commands do not work at all
or I am being remarkably thick! I suppose it is possible that the
rpcclient binary is corrupt or the version I am using has a bug in it. I
would very much like to hear if anyone has succeeded in getting this
process to work, particularly with PCL5/6 based printers.
As a alternative, I would consider downloading and compiling Samba but I
am curious as to how I can identfy what option were specified when the
packages were built i.e.is it possible to query the packaged version and
identify the compile options originally used.
Regards,
Chris
Christopher Moss
Murray McIntosh O'Brien
Wellesley House
204 London Road
Waterlooville
PO7 7AN
023 9223 1006
-----Original Message-----
From: chris [mailto:chris@mmo-accountants.co.uk]
Sent: 07 July 2004 17:24
To: 'samba@lists.samba.org'
Subject: Point and Print
I recently posted regarding problems configuring Samba. These have all
been fixed but I am now struggling with the point and print facility. I
have attempted to upload the drivers from Windows XP workstations but
this seems to do nothing. So plan B was to manually copy the files to
the appropriate print$ share folder, so far so good. The problem I now
have is that the rpcclient utility simply doesn't work.
Without a debug level set I either get a usage prompt or a DOS code of
0x0000003
If I set debug to level 3 it produces the following error:
added interface ip=10.0.0.3 bcast=10.0.0.255 nmask=255.255.255.0
Password:
Connecting to host=localhost
Connecting to 127.0.0.1 at port 445
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x60890215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
lsa_io_sec_qos: length c does not match size 8
I have Googled with this error and noticed a number of posts but so far
not found an answer
The printer concerned is an HP 2300 PCL6 which has a whole string of
file dependencies (48 files in total). The result being that I've had a
lot of trouble with quoting errors (Unix skill still abit rusty) but I
seem to have got to the bottom of that problem.
N.B. System is Suse 9.1 running Samba 3.0.4 - (update downloaded this
morning to see if it would solve the problem). Printing is via Cups -
not sure of the version.
I would greatly appreciate any help with this problem as it is driving
me mad!!!
Regards,
Chris
Christopher Moss
Murray McIntosh O'Brien
Wellesley House
204 London Road
Waterlooville
PO7 7AN
023 9223 1006
-------------------------------------------------------------------------------------------------------------------
Disclaimer
Privileged or confidential information may be contained in this message.
If you are not the addressee of this message please notify the sender
by return and delete it, and you may not use, copy, disclose or rely
on the information contained in it. Internet e-mail may be susceptible
to data corruption, interception and unauthorised amendment for which
Murray McIntosh O'Brien does not accept liability. Likewise whilst we
have taken reasonable precautions to ensure that this e-mail and any
attachments have been swept for viruses, Murray McIntosh O'Brien
does not accept liability for any losses caused as a result of viruses.
Statements in this message that do not relate to the business of Murray
McIntosh O'Brien are neither given nor endorsed by it or the Directors
of Murray McIntosh O'Brien. A list of the Directors of Murray McIntosh
O'Brien is available for inspection at our offices.
----------------------------------------------------------------------------------------------------------------------
