search for: kallsen

Hi folks. I asked this question a couple of weeks ago, but nobody posted any answers. I have mandrake 9.1 with Samba 2.2.8 running a domain with 500 users. It has worked flawlessly for a long time. However, it is time to set up a new server. I have a new server with Mandrake 10 OE and Samba 3.0.3 running. Please explain to this newbie and very satisfied samba user how to migrate all my

I had a test machine up and running Samba, joining an AD domain, and set up with winbind... when I ran "getent passwd" it would list all the local users, and all the domain users. I could also log in as a domain user without any problem. So, I made an image of the hard drive, and copied it to 7 other machines. Now, those 7 are having a strange problem. I changed the names and IP's of

Dear Fellow Samba Users: I have mandrake 9.1 with Samba 2.2.8 running a domain with 500 users. It has worked flawlessly for a long time. However, it is time to set up a new server. I have a new server with Mandrake 10 OE and Samba 3.0.2 running. Please explain to this newbie and very satisfied samba user how to migrate all my users, groups, sid, domain, etc to the new machine. My goal is

Hi together, we have a Windows 2003 Active Directory Server, working together with Samba Version 3.0.2a-Debian. It seems everything (Kerberos authentication and so on) works fine. All the authentication is done by the windows 2003 server. My problem is, that I can't connect to a share via a windows xp client, when the share has an option "valid user" which defines a group of the

Samba folks: The title maybe indulgent, but I wanted to get everyone's attention. I currently run mandrake 9.0 (FILESERVER) with samba 2.2.8 running as a PDC and file server for 20 WinXP workstations. We bought a new server to replace (FILESERVER). However, I want to install mandrake 9.2 and samba 3.0 on the new server -then I want the new server also to replace the PDC of the old

...create mask = 0775 guest ok = Yes browseable = No [acct_rec] path = /home/cabinets/acct_rec admin users = @officeGROUP read only = No create mask = 0775 directory mask = 0777 guest ok = Yes browseable = No Kevin Kallsen Owner E101 Technology Solutions www.e101.com 203-525-2558 PO Box 535 Thomaston, CT 06787

I have the latest rsync running on mandrake official 10. At 2:30 I run rsync --daemon from cron to run an offsite backup for all my customers. At 8:00 I run killall rsync. However my log files show the following: 2004/04/20 02:00:00 [2702] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20 02:00:59 [2707] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20

I have the latest rsync running on mandrake official 10. At 2:30 I run rsync --daemon from cron to run an offsite backup for all my customers. At 8:00 I run killall rsync. However my log files show the following: 2004/04/20 02:00:00 [2702] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20 02:00:59 [2707] rsyncd version 2.6.0 starting, listening on port 873 2004/04/20

Hi, I have just installed 2.0.1 on two boxes. One box did not have shorewall on at all and the other had 1.4.10 on. Both these boxes are Debian. On the 1.4 box it upgraded fine, and everything works OK. The /etc/init.d/shorewall script runs on startup and loads shorewall fine. On the clean box the /etc/init.d/shorewall script does not seem to work. When run it produces no output, so on bootup

Here is my samba 3.0.4a smb.conf. I am scratching my head here because I know I missed something obvious.. My WINXP SP1 Clients cannot find the domain when I try to join the domain. # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2004/05/26 10:04:18 # Global parameters [global] workgroup = CARBYDOMAIN netbios name = CARBYSERVER