similar to: Samba 3.0.x to HP CIFS Server move

I have only this platform to try it on, but observe the following inconsistencies: (from the manpage for 'net'): RAP PRINTQ RAP PRINTQ LIST QUEUE_NAME Lists the specified print queue and print jobs on the server. If the QUEUE_NAME is omitted, all queues are listed. ...OK, so: [novosirj@njmsa ~]> /products/samba/bin/net rap printq list ljndemo No command: list

I run rpcclient without specifying an IP address and I get the following error: # /products/samba/bin/rpcclient //localhost -U novosirj Password: cli_full_connection: failed to connect to //LOCALHOST<20> (0.0.0.0) Cannot connect to server. Error was NT_STATUS_UNSUCCESSFUL ...the machine knows what localhost is otherwise: # telnet localhost Trying... Connected to localhost.umdnj.edu.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've had this problem for quite awhile. I'm attempting to go back through the Samba issues that have been driving me crazy during my move to a current release. Here is the issue: - --- # ./nmblookup RWJA-LM querying RWJA-LM on XXX.XXX.XXX.255 XXX.XXX.XXX.XXX RWJA-LM<00> - --- Looks good to me, though, really, it should be querying

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey all, Looking to upgrade from Samba 3.0.11 to HP CIFS/9000 2.03 (which is basically a patched Samba 3.0.22) on HP-UX 11i. Looking at simultaneously moving from smbpasswd as my passdb backed to tdbsam. Looks pretty idiot proof, and I think I should have very little trouble. However, here is one slight problem that I'm running into so far: #

I read this on the list awhile back -- am I mistaken: I thought that "passwd" did not accept the migrate command without a patch to smbpasswd... I can't remember exactly where I read that... can someone confirm or deny this? Was the patch mainstreamed? ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _|

I am using the pam_smbpass module, and I apologize if this is somewhat of a PAM problem, but the HP-UX PAM implementation leaves a lot to be desired so the docs are not always that helpful to me. When using pam_smbpass after an smbpasswd, I get two password changed lines, presumably because when smbpasswd uses PAM, it then re-calls the pam_smbpass module. Therefore, in addition to getting double

With 2.0.x, I believe, print job names were automatically massaged to remove evil characters such as "/" and "," etc. Now in 2.2.x, the job names are smbprn... etc. unless you specify (in LPRng's case) -J%J for the job name. However, the format of the job name is unrefined and is causing me trouble. Is there any way to get back the pre-2.2.x behavior without writing some

Does anyone know what could cause "Save As..." to be grayed out when you are working with the policy tool? Everything I've read just tells me to save an NTconfig.POL, but... for some reason, I can only save the policy to the local machine. Do I have to be logged in as a local user, or..? Thanks for the help. For anyone who is confused about policy implementation, a great resource is

I'm pulling my hair out with this. I see that the NT4 white-paper (very helpful and makes a lot of sense) says to make a Template user, set things the way you want them, and then copy their profile to the server. However, I try this, their profile comes out fine, I take care of all of the "Windows is now installing Office 2000" messages, and end up with a user where everything just

I cannot for the life of me get Samba 3.0.1 to display any queue information for more than a second or so. It looks very much like bug #660, but the changes say that 660 is resolved and has been since pre2 of 3.0.1. If this is the same bug, I beg to differ! Please tell me what information would be of use. The environment is an HP-UX 11.11 machine, 9000 N-class PA-RISC 2.0 arch server. I am using

This is a REALLY simple bug to fix, but I'm not sure of the best way to go about it or I would have written a patch already. The basic problem is that throughout the code, $(CC) is run with one of the arguments being $(DYNEXP). This is fine. However, in two places (one at 965 of Makefile.in where libsmbclient gets linked, and one at 1201 where pam_smbpass gets linked), $(DYNEXP) is used

I'm not sure what is doing this, so please help to to figure out what options I might need to review. My Samba admin password is, not surprisingly, not the same as the root password on the system. However, the Samba admin password keeps becoming the root password on the system (ie. I have a separate Samba admin password, but after awhile it will stop working and lo and behold, the real

I recently downloaded and installed v3.0.8 and installed it on HP-UX 11.11. Thankfully, all of the compile problems I reported in 3.0.2 are now gone (not sure why no one ever acknowledged my bug, but whatever). However, now my system is complaining that TCP_NODELAY is not a valid option. I did not turn it off during the compile, don't see it listed as an option, and worse than that, it is

Here is what I'm seeing after upgrading to 3.0.x: 1) Jobs no longer properly report their status, using LPRng's lpq. I see, instead, no listing for status and a listing for number of pages in the job. While that is also useful information, it does not allow me to act on jobs as I'd like to (resume/pause/etc). 2) Basically EVERY job that has ever printed via Samba on that printer

So far, bugs 2072 and 2140 have reported this condition. I was wondering if there was any movement on it. I know Richard Allen, author of 2140 and apparently the patch to bug 1065, had said he'd do some work on it. My "fix" for now has been ripping the #ifdef's out of config.h, but I still get a lot of complaints in the system log files about TCP_NODELAY, et. al: [2005/01/14

For Win2K, I've been using RunDLL32 printui.dll,printuientry to do a bunch of different printer related stuff (most notably, mapping printers and setting the default). Looks like NT4 doesn't have the same stuff. Is there anything classier I can use than NET USE under NT4 (without downloading something like Kixstart)? Thanks for your help. ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| |

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After a long hiatus from attention to Samba, I've started to compile the latest version (3.0.22) on HP-UX 11i for testing. I've noticed a couple of things. 1) For some reason, on my test system, every execution of any program that comes in the Samba suite drops "mon.out" files everyplace. Everything I can find about this says that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Noticed the following when conducting torture tests today: [2006/05/12 14:04:24, 0] printing/pcap.c:pcap_cache_reload(159) Unable to open printcap file /etc/printcap for read! ...which to me, was interesting, because I was not under the impression I was using load printers. Apparently, at some point, it became the default. That's fine, but I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm running HP's CIFS/9000 server (a patched Samba 3.0.22, basically), and am having odd problems with my smbpasswd file remaining locked by client PC's. I'm using the old smbpass backend, intending to switch to tdbsam. Just now, someone who runs smbpasswd to create accounts got an error message with an interrupted system call trying

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can anyone brighter than me think of an easy way to remove MANY users from an smbpasswd file (I have a list of users that can be removed, some of which may already be missing, some of which may be present)? I cannot use smbpasswd -x in a loop. Is there some easy way to do this? =R - -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan