Re: [Samba] Novice question - How to completely disable printing and /etc/printcap errors ?
On 1/26/06, Josh Kelley [EMAIL PROTECTED] wrote: The following (or something like it) was suggested earlier on the list by Jerry Carter: load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes Thanks, this worked, no more errors! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED was Re: Any ESRI users? Upgrade 3.0.14 to 3.0.21a broke Arcmap layer loading?
On 1/30/06, Jeremy Allison [EMAIL PROTECTED] wrote: We discovered an oplock logic bug in 3.0.21a which we'll be fixing in 3.0.21b. You might want to try turning them on again if you upgrade. Thanks for the headsup! I've been reading about oplocks (including the HOWTO) and it sounds like we don't need 'em. If I understand the HOWTO correctly, they don't sound like the world's greatest idea. Our network is reasonably fast and our user applications aren't moving tons of data back and forth. It's still puzzling me why oplocks are even *in* this picture since the ESRI applications should be opening files read-only, but maybe they aren't. I *am* wondering why the default setting for oplocks is on, when they sound somewhat risky. Do some Microsoft applications take it ill if they aren't available? thanks again Betsy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SOLVED was Re: Any ESRI users? Upgrade 3.0.14 to 3.0.21a broke Arcmap layer loading?
Did not hear from anyone on this, so maybe we are the only ESRI users who got bit, but this turned out to be an issue with oplocks. Disabling oplocks on the server eliminated the problem. On 1/27/06, Elizabeth Schwartz [EMAIL PROTECTED] wrote: We just upgraded our samba server from 3.0.14 to 3.0.21a and have discovered a subtle but very painful problem. Users of ESRI ArcMap (on fully patched Windows XP clients) are unable to read complex layered file data. Arcmap works fine with 3.0.14, it works fine with the data on a windows share, and it works fine when I set up a server to run the version of samba shipping with Solaris 9 (3.0.2! ). But, I really don't want to downgrade the primary file server to one of these old versions. The data also works fine if it is copied back from the Samba server to a local disk. The problem as I understand it is that ArcMap loads .lyr and .mxd files which in turn contain metadata that references multiple other files. When these secondary files are loaded from the Samba 3.0.21a server, they are opened but not fully read - the database files show empty fields, the maps show partial images, etc. To quote our GIS guy: arcmap documents that have nested layer references to data on SAMBA, and also compressed shape (.sdc) files such as are included on the esri maps and data cds (if they happen to be on aSAMBA share, either cause arcmap to crash, or appear in the table of contents as layers that have no records. The windows XP event viewer shows an error when this happens: MRxSmb Description: The redirector failed to determine the connection type http://support.microsoft.com/kb/315244/ I'm not seeing any particular errors on the server side (although I am getting some of these: https://bugzilla.samba.org/show_bug.cgi?id=3346 https://bugzilla.samba.org/show_bug.cgi?id=3346i'll be glad to see 3.0.21b) ESRI claims to have no knowledge of the problem, and since their software works OK with other Samba versions they feel it isn't at their end. Are there other ArcMap users here? Any thoughts on what to pursue next? (other than installing 3.0.21b at the first opportunity) thanks Betsy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Any ESRI users? Upgrade 3.0.14 to 3.0.21a broke Arcmap layer loading?
We just upgraded our samba server from 3.0.14 to 3.0.21a and have discovered a subtle but very painful problem. Users of ESRI ArcMap (on fully patched Windows XP clients) are unable to read complex layered file data. Arcmap works fine with 3.0.14, it works fine with the data on a windows share, and it works fine when I set up a server to run the version of samba shipping with Solaris 9 (3.0.2! ). But, I really don't want to downgrade the primary file server to one of these old versions. The data also works fine if it is copied back from the Samba server to a local disk. The problem as I understand it is that ArcMap loads .lyr and .mxd files which in turn contain metadata that references multiple other files. When these secondary files are loaded from the Samba 3.0.21a server, they are opened but not fully read - the database files show empty fields, the maps show partial images, etc. To quote our GIS guy: arcmap documents that have nested layer references to data on SAMBA, and also compressed shape (.sdc) files such as are included on the esri maps and data cds (if they happen to be on aSAMBA share, either cause arcmap to crash, or appear in the table of contents as layers that have no records. The windows XP event viewer shows an error when this happens: MRxSmb Description: The redirector failed to determine the connection type http://support.microsoft.com/kb/315244/ I'm not seeing any particular errors on the server side (although I am getting some of these: https://bugzilla.samba.org/show_bug.cgi?id=3346 https://bugzilla.samba.org/show_bug.cgi?id=3346i'll be glad to see 3.0.21b) ESRI claims to have no knowledge of the problem, and since their software works OK with other Samba versions they feel it isn't at their end. Are there other ArcMap users here? Any thoughts on what to pursue next? (other than installing 3.0.21b at the first opportunity) thanks Betsy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Novice question - How to completely disable printing and /etc/printcap errors ?
I'm running Samba 3.0.21a (blastwave build) on Solaris 9. The Solaris servers have no printers attached or accessible, just file service. Samba users authenticate off a Win2003 AD controller and get printing from that. I got rid of the Unable to connect to CUPS Server errors by adding to smb.conf the line printing=bsd but I am still getting smbd[4809]: [ID 702911 daemon.error] Unable to open printcap file /etc/printcap for read! Is there a way to get rid of this error short of recompiling? (it is nice to be using the thanks Betsy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] More Random Behaviour
A few random possible causes for no reason failures: - a config file was changed some time ago but someone failed to test it by restarting the daemon or rebooting the server, until now -some server is having network connectivity or load issues, and the backup or secondary doesn't have the same information -some third party changed permissions somewhere that wasn't immediately apparent -your server is having connectivity or load or file system space issues (don't forget to check the space where the error log goes) -your config file has cruft in it from many versions ago that no longer applies to this particular version (that bit me yesterday on my AV scanner!) Seriously, turn your log level down to something sane and make sure that you understand any error that you see. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba and OS X 10.4.2 - vfs quota inheritance not correct
We're running Samba 3.0.20 on a Solaris 9 server, using the Blastwave build. smb.conf file is below. Our user homes are on a Veritas file system with vxquota enabled, usually 50M per user, and then users have links under their home dirs to file systems with larger quotas or no quotas. For example, /home/joeuser has a 50M vxquota, but /home/joeuser/aux is a softlink to /vol/aux on which joeuser has a vxquota of a gig, and /home/joeuser/nettmp is a softlink to /vol/nettmp which is a VERY LARGE file system with NO quotas (that gets wiped every 24 hours) With Windows and OS X 10.3.x clients, this works fine. However, OS X 10.4.2clients are incorrectly getting the home directory quota limit applied to any subdirectory, and these users can't write ANY large files ANYWHERE on the system. This is pretty bad. I know this is more likely to be an OS X problem than a Samba problem but I'm asking here to see if anyone else has encountered this and knows of a fix or workaround. Giving users unlimited quotas in their home directories is not a good option :-) I've got them using fugu to upload for the moment but that does not let them work on some applications. thanks Betsy # more /opt/csw/etc/samba/smb.conf # Global parameters [global] realm = DESIGN.HARVARD.EDU http://DESIGN.HARVARD.EDU security = ADS workgroup = DESIGN password server = snip encrypt passwords = yes interfaces = eri0 lo0 bind interfaces only = Yes password level = 8 log level = 2 syslog = 2 log file = /var/adm/cswsmblog deadtime = 5 local master = No load printers = no wins server = snip hosts allow = snip # printing = bsd # print command = echo nis homedir = yes posix locking = no max log size = 524288 [test] path = /vol/nettmp browsable = yes valid users = @everyone guest ok = Yes [homes] browsable = no writable = yes create mask = 0775 directory mask = 0775 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Followup: Samba and Tiger and Plaintext PW's fixed in 10.4.2
We downloaded the developer build and Apple has fixed this in 10.4.2, so Tiger users can use Samba plaintext passwords. (I know we still need to switch to encrypted, but at least now people can continue to work) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] FOLLOWUP: Samba, OS X Tiger 10.4 plain text password, username null-padded?
So, an Apple engineer came and hung out for about three hours last week and agreed that Tiger was doing something pretty funky with the plain text passwords. Today's word is: there is a fix in 10.4.2 that will go in combination with the /etc/nsmb.conf and hopefully solve your problem.That is as much detail as I have right now. Do you have access to the seed build of 10.4.2 via ADC ? We aren't going to play with beta releases of OS X ourselves right now but I'd be real interested if anyone here does. cheers Betsy [who received a bunch of off-list Me Too messages...] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] FOLLOWUP: Samba, OS X Tiger 10.4 plain text password, username null-padded?
On 6/20/05, Eric Hines [EMAIL PROTECTED] wrote: So, Apple is following the Microsoft school of Tech (non)Support I dunno, I think it's not too shabby to go from seeing proof of a problem to having a fix in a downloadable build in , um, two business days. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba, OS X Tiger 10.4 plain text password, username null-padded?
Our samba server is running Solaris 9 and Samba 3.0.2.a . For reasons *outside the scope of this question* we are using plaintext passwords and authenticating via our NFS server. (I know this isn't a great idea, but that's not the question) With Panther, plaintext passwords worked fine. Snooping, I see the plain text password and username go through. With Tiger, we first had to apply this small fix to the client to enable plain text passwords: http://docs.info.apple.com/article.html?artnum=301580 Once this was done, snooping an smbclient connection, I see the plain text password and the username but they are null-padded. Authentication works. But when Tiger attempts to mount an smb share via the GUI, I see the password NOT null-padded and the username PADDED, and this fails. Can anyone comment on this? I realize that the sane thing to do is switch to encrypted passwords, but if we don't want to do that right now for whatever reason, are there any other suggestions? Has anyone else seen this behavior? Am I correct in calling this a Tiger bug? thanks Betsy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Samba, OS X Tiger 10.4 plain text password, username null-padded?
On 6/15/05, Elizabeth Schwartz [EMAIL PROTECTED] wrote: Our samba server is running Solaris 9 and Samba 3.0.2.a . For reasons *outside the scope of this question* we are using plaintext passwords and authenticating via our NFS server (that should be NIS server, sorry!) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba, OS X Tiger 10.4 plain text password, username null-padded?
On 6/15/05, Geoff Scott [EMAIL PROTECTED] wrote: This list deals with the samba server side. The smbmount stuff for linux is kernel code and so is dealt with on another list. But whatever Apple have done to the code you need to ask Apple. Don't expect any response though. Er... ok. No linux in this picture though, Samba server on Solaris and OS X Tiger client. I'm wondering if this is a bug in OS X, or in Samba, and/or if anyone else has seen this and gotten Samba to work with OS X and plaintext passwords Maybe we're the last ones still using plaintext passwords thanks Betsy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Newbie question - Wrong Way to map a share?
After a recent upgrade (details below) as many as 30 percent of our returning users are having trouble mapping SAMBA shares of their home directories on the terra server. Many report that the problem just goes away. I've only been able to pin down a couple of them. Here's what I see. User tries to map the drive, fails, and get a box with the window: Username: terra\Guest Password: *** This doesn't work. If I replace terra\Guest with just the unix username, it works fine. Everyone says but it USED to work the other way. It SHOULD work the other way So: *should* it work the other way? What changed? Can I change it back? Or do I just need to re-educate all my users? (and take the hit for making undocumented changes to a production server) I don't want to make any changes that would creating an additional account for every user or every machine. I did start with a fresh config file with this installation. System is authenticating via NFS and unix passwords, NOT using Active Directory. Thanks for a clue bonk, Betsy. PS on the server I see check_ntlm_password: Authentication for user [Guest] - [Guest] FAILED with error NT_STATUS_NO_SUCH_USER Old box: Sun 220R running Solaris 7, samba 2.2.2 and Veritas VM/FS 3.4. New box: Sun 280R running Solaris 9, samba 3.0.2a and Veritas VM/FS 3.5 (same Clariion LUN, moved to new box, veritas deport/import-ed.) Config file: # Global parameters [global] workgroup = DESIGN interfaces = eri0 lo0 bind interfaces only = Yes password level = 8 log level = 2 syslog = 7 log file = /var/adm/smblog deadtime = 5 local master = No wins server = 128.103.170.97 hosts allow = 128.103.170. 128.103.171. 128.103.172. 128.103.173. 128.10 3.174. 128.103.175. 128.103.141. 10.1.1. 10.1.67. printing = bsd print command = echo nis homedir = yes encrypt passwords = no posix locking = no max log size = 524288 [test] path = /tmp browsable = yes valid users = @everyone guest ok = Yes [homes] browsable = no writable = yes create mask = 0775 directory mask = 0775 oplocks = no -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
