Hi everyone, OK, this is driving me nuts, and I'd really appreciate some help from those who are intimately familiar with the way the Locks, etc work with Win2K clients... We have an ACT database that is shared among about 25 Users, all Win2K clients. I have tried and tried and tried again to move this database over to my Linux (Redhat 7.0 with almost all 7.1 patches) server running SAMBA, both in 'Share' mode and 'User' mode. I haven't tried 'Server' or 'Domain' modes yet. I've tried with 2.07, and I've tried with 2.2a3, all to no avail. Everything works just fine, until everyone has been logged in and been using the system for 20 to 30 minutes. Then we start getting weird errors, saying 'something can't be saved', and 'ACT has experienced an error'. Nothing that crashes the database (although we had major corruption problems with 2.07), just major problems working. Would someone mind giving me some precise recommendations for settings for the locking options and any other options that will make this work? If I can't make it work soon, my boss is gonna lose confidence in this (Linux/SAMBA) as a viable alternative to Win2K Server, and that would be bad, bad, bad. Tia for any suggestions anyone can provide... Charles Marcus
I am using Samba 2.0.7 with an Act database and Windows NT clients. I had
one Windows 2K client on the network at one point without any problems, but
that was a laptop and it now has it's own replica of the Act Database. We
haven't had any corruption of our large Database (18K+ records) AFAICT.
[ACTDatabase]
path = /home/LPc/ACTDatabase/current
browseable = yes
guest ok = no
writable = yes
valid users = @LPc
preserve case = yes
short preserve case = yes
force create mode = 0775
force directory mode = 0775
force group = LPc
I have no special locking settings in the global section of my smb.conf
file. I use the force* settings to make sure the user/group
permissions/settings don't get f'd up by the various users. And only
those
users who are in the LPC group can access the share.
Hope that helps.
-----Original Message-----
From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On
Behalf Of Charles Marcus
Sent: Thursday, April 12, 2001 12:20 PM
To: Samba Maillist (E-mail)
Subject: OK, need some help with Win2K clients real bad
Hi everyone,
OK, this is driving me nuts, and I'd really appreciate some help from those
who are intimately familiar with the way the Locks, etc work with Win2K
clients...
We have an ACT database that is shared among about 25 Users, all Win2K
clients.
I have tried and tried and tried again to move this database over to my
Linux (Redhat 7.0 with almost all 7.1 patches) server running SAMBA, both in
'Share' mode and 'User' mode. I haven't tried
'Server' or 'Domain' modes
yet. I've tried with 2.07, and I've tried with 2.2a3, all to no avail.
Everything works just fine, until everyone has been logged in and been using
the system for 20 to 30 minutes. Then we start getting weird errors, saying
'something can't be saved', and 'ACT has experienced an
error'. Nothing
that crashes the database (although we had major corruption problems with
2.07), just major problems working.
Would someone mind giving me some precise recommendations for settings for
the locking options and any other options that will make this work? If I
can't make it work soon, my boss is gonna lose confidence in this
(Linux/SAMBA) as a viable alternative to Win2K Server, and that would be
bad, bad, bad.
Tia for any suggestions anyone can provide...
Charles Marcus
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Just for grins.. I too have seen problems with various databases. I set up a test with 5 Win2K machines all using the same databases. (DBase3) and found that after time (3 hours or so), those machines started reporting problems reading and writing to those files (codebase errors). All machines were built the same. When the machines were setup to hit the database for an hour then stop.. and access again for another hour, the problems would happen in a time frame that you are seeing. To verify further, the same server (RH 6.2 w/2.07) was tested with 5 NT4.0 machines using the same databases. The NT4.0 machines had no problems and were reliable as always. I know that Win2K has added ODBC support for databases. I do not have any other info on this as of yet but hope to soon. I am not entirly convinced that this is a Samba problem. The same system works like a charm w/NT4.0 just not with Win2K. Basic troubleshooting would point to the 2K's but it's hard to pin it down to one or the other. -----Original Message----- From: Charles Marcus <CharlesM@media-Brokers.com> To: Samba Maillist (E-mail) <samba@lists.samba.org> Date: Thursday, April 12, 2001 11:15 AM Subject: OK, need some help with Win2K clients real bad>Hi everyone, > >OK, this is driving me nuts, and I'd really appreciate some help from those >who are intimately familiar with the way the Locks, etc work with Win2K >clients... > >We have an ACT database that is shared among about 25 Users, all Win2K >clients. > >I have tried and tried and tried again to move this database over to my >Linux (Redhat 7.0 with almost all 7.1 patches) server running SAMBA, bothin>'Share' mode and 'User' mode. I haven't tried 'Server' or 'Domain' modes >yet. I've tried with 2.07, and I've tried with 2.2a3, all to no avail. > >Everything works just fine, until everyone has been logged in and beenusing>the system for 20 to 30 minutes. Then we start getting weird errors,saying>'something can't be saved', and 'ACT has experienced an error'. Nothing >that crashes the database (although we had major corruption problems with >2.07), just major problems working. > >Would someone mind giving me some precise recommendations for settings for >the locking options and any other options that will make this work? If I >can't make it work soon, my boss is gonna lose confidence in this >(Linux/SAMBA) as a viable alternative to Win2K Server, and that would be >bad, bad, bad. > >Tia for any suggestions anyone can provide... > >Charles Marcus > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba >
digi> I'd be intrestead to see what you get when you add a few more 2K's to the network. If you get the chance, try it. I can imagine a machine that is running a local copy of the database will work wonderfully. That, however kinda defeats the purpose. I would not give up on Linux or Samba just yet. Some things just take time. I'm just hopeing that someone has been able to figure out why. If the group knows of something to try or look for, I'd be happy to test or look for what I can. -----Original Message----- From: Edward Muller <emuller@learningpatterns.com> To: Charles Marcus <CharlesM@media-Brokers.com>; Samba Maillist (E-mail) <samba@lists.samba.org> Date: Friday, April 13, 2001 9:18 AM Subject: RE: OK, need some help with Win2K clients real bad>I am using Samba 2.0.7 with an Act database and Windows NT clients. I had >one Windows 2K client on the network at one point without any problems, but >that was a laptop and it now has it's own replica of the Act Database. We >haven't had any corruption of our large Database (18K+ records) AFAICT. > >[ACTDatabase] > path = /home/LPc/ACTDatabase/current > browseable = yes > guest ok = no > writable = yes > valid users = @LPc > preserve case = yes > short preserve case = yes > force create mode = 0775 > force directory mode = 0775 > force group = LPc > >I have no special locking settings in the global section of my smb.conf >file. I use the force* settings to make sure the user/group >permissions/settings don't get f'd up by the various users. And only those >users who are in the LPC group can access the share. > >Hope that helps. > >-----Original Message----- >From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org]On >Behalf Of Charles Marcus >Sent: Thursday, April 12, 2001 12:20 PM >To: Samba Maillist (E-mail) >Subject: OK, need some help with Win2K clients real bad > > >Hi everyone, > >OK, this is driving me nuts, and I'd really appreciate some help from those >who are intimately familiar with the way the Locks, etc work with Win2K >clients... > >We have an ACT database that is shared among about 25 Users, all Win2K >clients. > >I have tried and tried and tried again to move this database over to my >Linux (Redhat 7.0 with almost all 7.1 patches) server running SAMBA, bothin>'Share' mode and 'User' mode. I haven't tried 'Server' or 'Domain' modes >yet. I've tried with 2.07, and I've tried with 2.2a3, all to no avail. > >Everything works just fine, until everyone has been logged in and beenusing>the system for 20 to 30 minutes. Then we start getting weird errors,saying>'something can't be saved', and 'ACT has experienced an error'. Nothing >that crashes the database (although we had major corruption problems with >2.07), just major problems working. > >Would someone mind giving me some precise recommendations for settings for >the locking options and any other options that will make this work? If I >can't make it work soon, my boss is gonna lose confidence in this >(Linux/SAMBA) as a viable alternative to Win2K Server, and that would be >bad, bad, bad. > >Tia for any suggestions anyone can provide... > >Charles Marcus > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba >