[Samba] 3.0.24 on Solaris 10 (sparc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am running samba 3.0.24 (PDC, LDAP) since one week on solaris 10. Everything worked fine, but after one week samba did not respond anymore. When I tried with smbclient, a smbd process forked, and then hangs here (log level 10): [2007/03/28 22:18:23, 3] smbd/oplock.c:init_oplocks(862) open_oplock_ipc: initializing messages. more specifically (with truss): 13500: lwp_sigmask(SIG_SETMASK, 0x00010080, 0x) = 0xFFBFFEFF [0x] 13500: fcntl(27, F_GETFL) = 2 13500: getmsg(27, 0xFFBFF2E4, 0xFFBFF260, 0xFFBFF26C) (sleeping...) where fd 27 is /dev/tcp: 27: S_IFCHR mode: dev:322,0 ino:37295 uid:0 gid:0 rdev:42,347 O_RDWR /devices/pseudo/[EMAIL PROTECTED]:tcp Even deleting all tdbs and reinstalling from source did not solve the problem. However when I tried it with 3.0.14a again, it worked. Then, I rebooted the machine and 3.0.24 worked again, too. Maybe a Solaris Bug... any comments are welcome... br Harald Strack -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFGC2eZczpSApoeLSQRApWxAKC4kw2UoJ/IALWf84EHg6rx/8by+gCg4V8O vgO67EdJYE+KLYOsghE3VDU= =W64f -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] windows clients can't see workgroup at all
Here are a few things you might try if the samba server is the only server on the network. In the smb.conf file make sure wins support = yes And on the windows computer in the tcp/ip settings add the ip address of the server to the wins tab. Then when the servers and other windows computers are running check the logs on the server to see if one of the windows computers is fighting with the Samba server for browse master on the network. If this is happening change the OS level in the smb.conf file to make samba win the master browser slot on the network. If this samba server is not going to be the wins server add these settings to the smb.conf wins support = no wins server = (192.168.0.2 ip address of your wins server) Make sure the wins server ip address is set in the tcp/ip settings > I'm trying to troubleshoot a new samba setup on a tiny network, and I'm > clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. > > When I first set it up, it seemed to go so smoothly. I changed all the > workstations to the same workgroup (RABNETWORK) and they could see each > other and the server, but they couldn't open anything on the server. I > don't > really understand what the problem is, but I didn't change anything, I > gave > up and went home. Now, none of the workstations can browse the network at > all. When I click "View workgroup computers" the error I get says that the > network is not accessible. Even with the server off, the network is not > accessible (hence my suspicion that samba is not the problem). > > What I can't sort out is what the problem is likely to be. I tried > stopping > the firewall (AVG) altogether, which didn't make a difference. I tried to > walk through this diagnosis worksheet: > http://samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html > > and got the following results: > 1) testparm works > 2) ping by name fails; I can ping the server's IP address from the Windows > clients, but can't ping the Windows machines from the server. > 3) works: smbclient -L BIGSERVER > > Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] > > Sharename Type Comment > - --- > homes Disk Home Directories > print$ Disk Printer Drivers > Share Drive Disk This is the server. > tmp Disk temporary files > IPC$IPC IPC Service (beastie server (Samba, > Ubuntu)) > ADMIN$ IPC IPC Service (beastie server (Samba, > Ubuntu)) > amanda Disk Home Directories > Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] > > Server Comment > ---- > > WorkgroupMaster > ---- > RABNETWORK BEASTIE > > 4) works: *nmblookup -B BIGSERVER __SAMBA__ > [EMAIL PROTECTED]:~$ nmblookup -B BEASTIE __SAMBA__ > querying __SAMBA__ on 127.0.0.1 > 192.168.1.102 __SAMBA__<00> > > *5) fails:* nmblookup -B ACLIENT '*'** >[EMAIL PROTECTED]:~$ nmblookup -B presta '*' >querying * on 0.0.0.0 >192.168.1.102 *<00> > > I'm stopping here because it seems pretty clear that the Windows XP client > machines are hating me.Where do I go from here? > > Thanks, > Amanda > > * > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] windows clients can't see workgroup at all
Here are a few things you might try if the samba server is the only server on the network. In the smb.conf file make sure wins support = yes And on the windows computer in the tcp/ip settings add the ip address of the server to the wins tab. Then when the servers and other windows computers are running check the logs on the server to see if one of the windows computers is fighting with the Samba server for browse master on the network. If this is happening change the OS level in the smb.conf file to make samba win the master browser slot on the network. If this samba server is not going to be the wins server add these settings to the smb.conf wins support = no wins server = (192.168.0.2 ip address of your wins server) Make sure the wins server ip address is set in the tcp/ip settings > I'm trying to troubleshoot a new samba setup on a tiny network, and I'm > clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. > > When I first set it up, it seemed to go so smoothly. I changed all the > workstations to the same workgroup (RABNETWORK) and they could see each > other and the server, but they couldn't open anything on the server. I > don't > really understand what the problem is, but I didn't change anything, I > gave > up and went home. Now, none of the workstations can browse the network at > all. When I click "View workgroup computers" the error I get says that the > network is not accessible. Even with the server off, the network is not > accessible (hence my suspicion that samba is not the problem). > > What I can't sort out is what the problem is likely to be. I tried > stopping > the firewall (AVG) altogether, which didn't make a difference. I tried to > walk through this diagnosis worksheet: > http://samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html > > and got the following results: > 1) testparm works > 2) ping by name fails; I can ping the server's IP address from the Windows > clients, but can't ping the Windows machines from the server. > 3) works: smbclient -L BIGSERVER > > Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] > > Sharename Type Comment > - --- > homes Disk Home Directories > print$ Disk Printer Drivers > Share Drive Disk This is the server. > tmp Disk temporary files > IPC$IPC IPC Service (beastie server (Samba, > Ubuntu)) > ADMIN$ IPC IPC Service (beastie server (Samba, > Ubuntu)) > amanda Disk Home Directories > Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] > > Server Comment > ---- > > WorkgroupMaster > ---- > RABNETWORK BEASTIE > > 4) works: *nmblookup -B BIGSERVER __SAMBA__ > [EMAIL PROTECTED]:~$ nmblookup -B BEASTIE __SAMBA__ > querying __SAMBA__ on 127.0.0.1 > 192.168.1.102 __SAMBA__<00> > > *5) fails:* nmblookup -B ACLIENT '*'** >[EMAIL PROTECTED]:~$ nmblookup -B presta '*' >querying * on 0.0.0.0 >192.168.1.102 *<00> > > I'm stopping here because it seems pretty clear that the Windows XP client > machines are hating me.Where do I go from here? > > Thanks, > Amanda > > * > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA and ACLs on FreeBSD 6.1
I have winbind working and it is providing security for my shares. Now, I would like to implement ACLs so I can help my backup users manage everything through MMC. Following is a copy of my smb.conf file. [global] workgroup = XX winbind separator = + idmap uid = 1-2 idmap gid = 1-2 winbind enum users = yes winbind enum groups = yes security = domain password server = 10.129.10.YY client schannel = no wins server = 10.129.10.YY log level = 5 # log file = /var/log/samba.%m name resolve order = wins hosts winbind use default domain = Yes realm = XX [Jay.Hall] comment = Jay Hall's Home Directory browseable = yes writeable = yes valid users = XX+jay.hall force user = hallja directory mode = 0770 path = /home/hallja admin users = Jay.Hall Using wbinfo -u and wbinfo -g I am able to pull user and group information from the Domain Controller. When I use MMC to connect to the share defined above, the only search location listed is the IP address of the server. I believe that should be the name/IP address of the domain controller. This leads me to believe I have something wrong in my smb.conf file. Any suggestions would be greatly appreciated. Thanks, Jay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] windows clients can't see workgroup at all
I'm trying to troubleshoot a new samba setup on a tiny network, and I'm clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. When I first set it up, it seemed to go so smoothly. I changed all the workstations to the same workgroup (RABNETWORK) and they could see each other and the server, but they couldn't open anything on the server. I don't really understand what the problem is, but I didn't change anything, I gave up and went home. Now, none of the workstations can browse the network at all. When I click "View workgroup computers" the error I get says that the network is not accessible. Even with the server off, the network is not accessible (hence my suspicion that samba is not the problem). What I can't sort out is what the problem is likely to be. I tried stopping the firewall (AVG) altogether, which didn't make a difference. I tried to walk through this diagnosis worksheet: http://samba.org/samba/docs/man/Samba-HOWTO-Collection/diagnosis.html and got the following results: 1) testparm works 2) ping by name fails; I can ping the server's IP address from the Windows clients, but can't ping the Windows machines from the server. 3) works: smbclient -L BIGSERVER Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] Sharename Type Comment - --- homes Disk Home Directories print$ Disk Printer Drivers Share Drive Disk This is the server. tmp Disk temporary files IPC$IPC IPC Service (beastie server (Samba, Ubuntu)) ADMIN$ IPC IPC Service (beastie server (Samba, Ubuntu)) amanda Disk Home Directories Domain=[BEASTIE] OS=[Unix] Server=[Samba 3.0.22] Server Comment ---- WorkgroupMaster ---- RABNETWORK BEASTIE 4) works: *nmblookup -B BIGSERVER __SAMBA__ [EMAIL PROTECTED]:~$ nmblookup -B BEASTIE __SAMBA__ querying __SAMBA__ on 127.0.0.1 192.168.1.102 __SAMBA__<00> *5) fails:* nmblookup -B ACLIENT '*'** [EMAIL PROTECTED]:~$ nmblookup -B presta '*' querying * on 0.0.0.0 192.168.1.102 *<00> I'm stopping here because it seems pretty clear that the Windows XP client machines are hating me.Where do I go from here? Thanks, Amanda * -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] LDAP Account Manager 1.3.0 released
LDAP Account Manager (LAM) 1.3.0 - March 28th, 2007 === LAM is a web frontend for managing accounts stored in an LDAP directory. Announcement: - LAM now supports multiple lamdaemon servers and displaying user photos in the account list. This release fixes also a security bug where HTML characters in LDAP data were not escaped. Features: - * management of Unix user and group accounts (posixAccount/posixGroup) * management of Samba 2.x/3 user and host accounts (sambaAccount/sambaSamAccount) * management of Kolab 2 accounts (kolabInetorgPerson) * profiles for account creation * account creation via file upload * automatic creation/deletion of home directories * setting quotas * PDF output for all accounts * editor for organizational units (OU) * schema browser * tree view * multiple configuration files * multi-language support (Catalan, Chinese, Dutch, English, French, German, Hungarian, Italian, Japanese, Russian, Spanish) * support for LDAP+SSL Availability: - This software is available under the GNU General Public License V2.0. You can get the newest version at http://lam.sf.net. It may take some time until you can download the files from all mirrors. File formats: DEB, RPM, tar.gz There is also a FreeBSD port. Debian users may use the packages in unstable. Demo installation: -- You can try our demo installation online. http://lam.sf.net/live-demo/index.htm Support: If you find a bug please file a bug report. For questions or implementing new features please use the forum and feature request tracker at our Sourceforge homepage http://www.sf.net/projects/lam. Authors & Copyright: Copyright (C) 2003 - 2007: Michael Duergner <[EMAIL PROTECTED]> Roland Gruber <[EMAIL PROTECTED]> Tilo Lutz <[EMAIL PROTECTED]> LAM is published under the GNU General Public License. The comlete list of licenses can be found in the copyright file. signature.asc Description: OpenPGP digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Problem with Desktop
sato x schrieb: > I guess it means that your roaming profiles are not working. So each time > users logon to their workstation, windows makes a temporary profile, then > delete them when they log out. :) Same guess from me. Jason, you might start with looking at the contents of the user's profile folder. If it's empty after logout something prevents the storage. If you need further assistance, just send a mail. timbo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File transfers to Windows XP x64 stalling and dying after a few minutes. [SOLVED]
just wanted to post to the list that i just had a very very similar issue to Geoff's but in this case the client OS (using samba as a file server) was Windows Server 2003 x64 R2 SP1 and the samba version was 3.0.24. After much googling and config trial-and-error, i found that upgrading to the recently-released Windows Server 2003 SP2 alleviated my problem. I also corresponded with Geoff (creator of this thread) off-list and he wrote that the same service pack (which is also available for 64-bit XP) also took care of his issue. In my own experiences, samba appeared to be functioning optimally as I only had this problem on this particular architecture/edition/version of Windows Server 2003. Basically any app that had a lock or connection to any open file would lose that connection after a few minutes of idleness (don't have a more exact time). I tried multiple network cards and multiple versions of network cards in the Windows box to no avail. Only applying SP2 solved the issue. On Monday, February 12, 2007 21:16:51 GMT , "Geoff Ellingwood" <[EMAIL PROTECTED]> wrote: I just did a fresh install of Windows XP Professional x64 on my primary machine, and am reconnecting all of my LAN services. One thing I have on my home network is a dedicated file server, running Ubuntu and Samba, used as a general file server, as well as a backup for when I reformatted my main system. While attempting to restore some of my files, I started noticing some odd errors. After a few minutes of transfers on a Samba session, the transfers would simply die, with various errors. Watching movies or listening to music stored on the server would meet with similar problems (the audio/video would start to skip). I attempted to narrow down the problem a bit. I have not experienced any errors with Internet transfers at all - I receive sustained high transfer rates off of high-traffic websites, and get excellent ping rates when playing on-line games. Transfers on the LAN using other protocols (SCP, AIM, etc.) all work just fine, both to and from the server, as well as with other machines on the LAN. My only conclusion was that something in Samba was causing this issue. To confirm, I watched the samba log and the top monitor while a transfer was occurring (and failed). Sure enough, something strange happened. I opened up the shared folder in Windows and began a copy of a large (2 Gb) ISO file. At first, the transfer went just fine. But then, the smbd process went from a steady 40% CPU utilization down to next to nothing. The file transfer also stalled at this point. After about 30 seconds, the process went back to normal utilization and the file transfer resumed, but the stall happened again after another few minutes. At this point, Windows apparently gave up, saying that "The specified network name can no longer be found" and aborted the file transfer. Then, the log spit out a few errors, which I have reproduced here: [2007/02/12 14:55:08, 1] smbd/service.c:make_connection_snum(693) bast (192.168.0.102) connect to service dump initially as user neppyman (uid=1000, gid=1000) (pid 11290) [2007/02/12 15:01:29, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.102. Error = Connection reset by peer [2007/02/12 15:01:29, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.102. Error Broken pipe [2007/02/12 15:01:29, 0] lib/util_sock.c:send_smb(765) Error writing 75 bytes to client. -1. (Broken pipe) [2007/02/12 15:01:31, 1] smbd/service.c:make_connection_snum(693) bast (192.168.0.102) connect to service dump initially as user neppyman (uid=1000, gid=1000) (pid 11311) I'm certainly no Linux guru, but I was at least able to get Samba set up and running prior to the reformat, and had no issues with it up until this point. Here are various portions of my smb.conf file: [global] workgroup = DOPE FIENDS server string = Loki dns proxy = no log file = /var/log/samba/log.%m max log size = 1000 syslog = 0 panic action = /usr/share/samba/panic-action %d security = user encrypt passwords = true valid users = ... neppyman passdb backend = tdbsam guest obey pam restrictions = yes invalid users = root passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . wins support = no [homes] comment = Home Directories browseable = no writable = no create mask = 0700 directory mask = 0700 [printers] comment = All Printers browseable = no path = /tmp printable = yes public = no writable = no create mode = 0700 [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no [dump] path = /share comment = Network Dump read only = No force create mode = 0777 guest ok = Yes (end smb.conf) Version information: Serve
Re: [Samba] Dueling master browsers...
Eric Knudstrup schrieb: > Server NITIN at IP 192.168.1.126 is announcing itself as a local master > browser for workgroup DVC and we think we are master. Forcing election. > Mar 27 09:10:05 macallan nmbd[3481]: [2007/03/27 09:10:05, 0] > nmbd/nmbd_become_lmb.c:unbecome_local_master_success(149) > Mar 27 09:10:05 macallan nmbd[3481]: * > Mar 27 09:10:05 macallan nmbd[3481]: Mar 27 09:10:05 macallan > nmbd[3481]: Samba name server MACALLAN has stopped being a local > master browser for workgroup DVC on subnet 192.168.1.2 > os level = 255 Tell the dork with the XP machine to stop that. YOU are the network's master, aren't you? (Pity if not...) AFAIK he must have tweaked his registry for that, but i'm not completely sure. timbo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] shares breaking
Hello, Samba 3.0.22 running on SuSE 10.1 in a small (eight machine) mostly Windows workgroup. We have a Buffalo 1.0TB Terrastation serving as a central file store with all workstations mapping a couple of Terrastation shares as drives. Samba intalled and works as expected, but when Samba comes up some of the workstation-Terrastation shares start to break intermittently (red x, diconnected network drive). I gather that the Terrastation may be running Samba. Any leads appreciated. Thanks in advance, jab -- John Bollinger, CFA, CMT www.BollingerBands.com If you advance far enough, you arrive at the beginning. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Logon script change failure
Thanks, I've got basically the same type of thing configured now but the PCs
were initially joined to the domain and have been signing on and receiving
login scripts in the form of %U.bat for years.
Now though I modify smb.conf to point them to logon.bat and for some reason
they continue to look for %U.bat and fail to process the logon.bat file. I've
patched around this via symlinking all
possible usernames as {username}.bat to logon.bat in the netlogon directory.
Frustrating to have to do this. I've tried stopping samba and removing .tdb
files with no luck as well.
The other thing I had asked about, upgrading RedHat9 machines from Samba2 to
Samba3 we've approached again. We've been successful in doing so, but not
without some pain.
The section titled "Linux clients printing to Windows XP machine" at the end of
this article is relevant: http://www.wlug.org.nz/SambaPrinting
The symlink of smb -> smbspool had to be made. Afterwards we could not add a
printer pointing to a WinXP share via the graphical system-config-printer GUI
tool but could using the text version,
system-config-printer-tui. Strange...
Also, we discovered that even if Samba was set to pass on print data raw,
configuring the printer in CUPS with a printer driver appeared to cause the
data received from the PC to have print driver
rules applied to it twice. We setup the printer as RAW in CUPS and it's working
now. Also strange...
>Hi Wendel,
>
>I've this in my smb.conf, and it works for any M$ windows in my domain
>
>[global]
>logon path =
>logon home =
>logon script = logon.bat
># logon path = \\%L\profiles\%U
># logon home = \\%L\%U\.9xprofile
># logon drive = H:
>
>[netlogon]
>comment = NLService
>path = /var/lib/samba/netlogon/%U
>valid users = %U
>browseable = no
>writeable = no
>
>In this configuration, each user will have their own logon.bat, but of
>course you can change it to suit your needs.
>
>Regards,
>
>sato
>
>
>
>
>On 3/20/07, Wendell Dingus wrote:
>>
>> I've got a bunch of servers which for a long time now have provided
>> domain logon scripts of the form %u.bat or %m.bat I've recently
>> created a more capable logon script in Kixtart and have changed smb.conf
>> to launch it for all users as just logon.bat So no more per-machine or
>> per-user scripts, everybody runs the same one, and inside it it does
>> per-machine and/or per-user things. At maybe 2/3rds of the sites this
>> works fine. For the others I'm getting errors in logs where the PC is
>> trying to find {machinename}.bat or {username}.bat and failing and
>> thusly *not* processing the logon script at all. As if the change in
>> smb.conf is being totally ignored. I've restarted samba, rebooted, etc..
>> In a few cases I've even tried renaming the entire /var/cache/samba/
>> directory and restarting samba so that it creates new copies of all the
>> .tdb's. I'm not certain that *all* instances of this are Samba2 but am
>> kind of suspecting they are. We've still got a bunch of customers with
>> RH9 and Samba 2.2.12 Hey it's doing what we ask and besides this latest
>> problem is working fine.
>>
>> So, any suggestions how to get a bunch of WinXP PCs to start looking for
>> "logon.bat" instead of "%u.bat"? In testing I've simply symlinked
>> logon.bat to all the usernames in netlogon and that works, as a band-aid.
>>
>> If Samba2 turns out to be the issue and an upgrade to Samba3 is to be
>> suggested, something else that's been a problem for me I could ask
>> about. I've tried the Samba3 RPMs provided at samba.org and they worked
>> great, except... The ability to define a printer in cups pointing to a
>> shared printer on a PC as \\{PCNAME}\{SHARENAME} ceased to work and I
>> ended up having to revert back to Samba2. I'd love to resolve this one
>> as well and breathe a bit more life into the RH9 boxes we may not get
>> upgraded for a long time still. They're all stock RH9 with the Fedora
>> Legacy updates all applied.
>>
>> # rpm -qa | grep -i 'samba\|cups' | sort
>> cups-1.1.17-13.3.0.14.legacy
>> cups-devel-1.1.17-13.3.0.14.legacy
>> cups-libs-1.1.17-13.3.0.14.legacy
>> gimp-print-cups-4.2.4-5
>> qtcups-2.0-15
>> qtcups-devel-2.0-15
>> redhat-config-samba-1.0.4-1
>> samba-2.2.12-0.90.6.legacy
>> samba-client-2.2.12-0.90.6.legacy
>> samba-common-2.2.12-0.90.6.legacy
>> samba-swat-2.2.12-0.90.6.legacy
>>
>> Thanks!
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/listinfo/samba
>>
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Active Directory Groups within /etc/group
I apologize if I'm going down the wrong avenue here... I have Samba/Winbind working to authenticate AD accounts to my Linux server. I can perform getent passwd ADUser and view the user credentials as well as using getent group ADGroup to view AD groups. When I modify /etc/group I can add ADUser to the file and the ADUser will have the security desired. However when I add an ADGroup to /etc/group it does not appear to work. My end goal is that instead of listing out several users on /etc/group on the wheel line, I would like to put an AD group on the line which I can keep up to date in the windows world for individuals that need wheel access. If there is another way that I am missing, please let me know. Thanks, Mark CONFIDENTIALITY NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email reply. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Application slowness after samba upgrade
Hi We have upgraded a very old Samba server to a new server running 3.0.22 on Ubuntu. The the workstations were Windows 98 on very old hardware and are now Windows XP on new hardware. Everything is now very fast compared to the old server, except for two applications - a payroll (Ace Payroll) and and finance system (Profax). Somewhat contrarily, these two apps are MUCH slower on the new server than they were on the old server. They have both been around for a while, although we are still getting updates for them. They both use some kind of file based "database" (data files and index files), although the actual "database" technology is different between the two. For the Payroll, if it is run locally on the workstation it is fast. I have turned off oplocks on the file types for the database files. The vendors are no help, and these two [EMAIL PROTECTED] applications have slightly soured an otherwise impressive upgrade. Can anyone suggest where I should be looking to catch performance problems? Many thanks Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] authentication w/o using /etc/passwd
You could alway's try another backend, nss-mysql, nss-ldap ect ect. sato x wrote: I've never done this before, but I guess if you're using redhat or fedoracore, you could try to use authconfig via the console and choose samba authentication. Let me know if you succeed. Good luck. Regards, sato On 3/3/07, Young <[EMAIL PROTECTED]> wrote: Is there a way to configure Samba such that /etc/passwd is not used but Samba's password file only? I'm looking for a simple way to configure it to avoid using /etc/passwd, if there's a way. Thanks in advance! - Young -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
