similar to: Point 'n' Print, issues after upgrade to 3.0.6

Has anybody done such a thing as this? I'm looking to make this transition as smooth as possible. I have the new fileserver up and running, and I'm using rsync to keep the Novell data current on the Samba server. Any words of advice on transferring the users and groups and permissions over to the new server in the least painful way possible? I have some idea that Novell uses LDAP

Hi all, I have been working on this for days to no avail. I am unable to join any machine to my domain. I think the server's machine password got corrupted but don't know how to change it. From the PDC, I try: oink:/usr/local/src/samba-3.0.12/source # net join PDC Password: Could not connect to server CORPSRV The username or password was not correct. From a member server, I try:

Samba 3.0.6 I have successfully gotten other printers to work using the 'point-n-click' method for downloadable drivers. However, playing with one printer leads to failed results. I have created the CUPS port/printer, added it to samba and then used the Windows APW to upload the drivers. After upload, the print properties windows readjusts for the new printer options - I have checked

Hi, I recently did a complete upgrade and reinstall of one of our Samba servers. No problem, I backed up all the data, the Samba configuration files, and the secrets.tdb. Just compiled 3.0.8 on the new server (which has the same hostname), copied the smb.conf to /usr/local/samba/lib and copied th secrets.tdb to /usr/local/samba/private. Started Samba, did 'net getlocalsid' and it

Hi, If anyone is successfully using the HP LJ8500 driver that comes with Windows XP in your print$ share in Samba 3.0.x, can you please mail me privately. I understand the issues I am seeing are probably not Samba related. In case they ARE Samba related, here is the main issue. Printing color graphics onto an envelope from MS Word 2000. The first time an envelope is printed, the background

Not sure if this is where I should ask about this, but if I try to run any of the smbldap-* scripts, I get the following kind of output: oink:/usr/local/sbin # ./smbldap-populate Using builtin directory structure erreur LDAP: Can't contact master ldap server (IO::Socket::INET: Bad protocol 'tcp') at /usr/local/sbin//smbldap_tools.pm line 153. I feel like this must be from a typo

Hi, I've just moved a second Samba domain to LDAP -- it works great! However, the first domain is now dead in the water. It refuses to autenticate, and from the logs it looks like it's not find the SambaDomainName entry in the LDAP tree. Here is a diagram of how my LDAP tree is set up. dc=mycompany,dc=com |___ ou=computers |___ ou=people |___ ou=groups |___ sambaDomain=domain1 |___

I am using Samba PDC with OpenLDAP2 and smbldap-tools. As part of my logon.bat, I call a script called ifmember.exe. This script can list out the groups a user is a member of. It is reporting that my root user is a member of the group 'engr.' I don't know if this is a bug with ifmember.exe or if it's an issue in Samba or in LDAP. Here is some relevant data:

Can someone verify that testparm in 3.0.7 always reports the [printers] share as browseable = no ? I think this is a bug in 3.0.7. It might be affecting smbclient listing of printer shares too. Misty

When I used smbldap-populate way back when I set up my LDAP server, I got two sambaDomainName objects in my LDAP tree -- one for the domain name (CORP) and one for the PDC Netbios name (CORPSRV). My Windows XP systems complain that they can't find the PDC for the domain CORPSRV. I am wondering if I even need the second sambaDomainName in LDAP at all. Any ideas? Misty

In short this is the problem. The XP Home machine called "misty" cannot see any other machines. It cannot see the Linux machines and it cannot see the XP Home machines or the XP Pro machine. In spite of this blindness it can map to all the XP machines and define so-called network places. But "misty" cannot map through the SAMBA protocal used by the Linux machines to make

Hi all, I have been having the weirdest network browsing problems on my network the past week. Come to find out the wins.dat file got corrupted. Removing that file fixed everything. Because our systems typically have uptimes measured in months rather than days, and it is difficult for me to restart Samba except as a scheduled task (which I'm afraid to do because there are users who

OK, I just took my first non-root user live on my Samba 3.0.7 system. Printing is via cups, with drivers stored in the print$ share. This user is a local power user. She can add printers, or root can add them. Root can also print from them. If this user tries to print anything (a test page even) she gets a non-verbose error that looks like a permissions error. She can view the queues

Hi all, I've got a share called [ACCOUNTING] with the following share definition: [ACCOUNTING] path = /data/samba/shares/Accounting valid users = @acct @"Domain Admins" browseable = yes public = no read only = no force group = acct Here is the permissions on the directory: oink:/data/samba/shares # ls -ld /data/samba/shares/Accounting drwxrwxr-x 9 root acct 4096 Nov 29 09:30

Hi all, i have ACLs working fine on my PDC, but they do not work on a member server. Here is a summary of my set-up: I am using LDAP backend, with nss_ldap on all of my member servers. Samba 3.0.12pre1 on the PDC and Samba 3.0.14a on the member server. I have winbindd running on my member server, and it is pointing at LDAP as its backend. ?wbinfo -u and wbinfo -g both work. I am using

I've got a WinXP machine that was configured for local profiles. I have now joined that machine to the domain, but when I try to log in as a user, it tries to use a roaming profile. Fine, that's what I want anyway. But it doesn't do the smart thing and copy the user's local profile to roaming -- it gives an error instead. OK, no problem, I will change the type. I log in as

Our Samba server was recently the recipient of a major upgrade. I thought all the kinks were worked out, but apparently not. I think this is the first time I've tried to join a machine account to the domain since the upgrade. I've tried using smbldap-tools and also just using smbpasswd (I have my users in LDAP). I'll also say that 'net join' works just fine from my Samba

Hi, I'm a tad confused about something. I've got a production instance of Samba running. I am trying to get a test version running on the same box, with the same SID. Without the test server running, I used "net setlocalSID <oldsid>" (the net binary is the one for the new server). Then when I issued 'net getlocalsid' it returned it. I thought I was fine.

I=92m using Samba 3.0.24 on Ubuntu Feisty. I=92m managing my printers = with CUPS. =20 =20 Just yesterday, one printer stopped being able to print through Samba. = This printer still prints fine directly from CUPS. When I try to send any = print job to the print via Samba, I get this: =20 [2008/04/08 11:15:58, 0] printing/printing.c:allocate_print_jobid(2262) allocate_print_jobid: failed

I have gotten 'point-and-print' working, but there are a couple small issues/questions I am trying to get my grasp around: - rpcclient print-1201 -U root%secret -c 'enumdrivers' this lists the drivers twice (I saw one other post about this, without any followup) - When adding drivers via the Windows APW, after uploading the drivers and the APW closing - are you supposed to