similar to: Migrating from Windows 2000 Server to Samba

Hi all, Due to a security breach at my office recently, we need to log successful / failed log-ins.? I've put in "log level = 3" in smb.conf on our active directory domain controller which seems to log what we need, however this is generating massive log files, due to it logging every file opening/closing by all users.? How do I log successful/failed log-ins without having to

Hi all, We're a small charity and we've got a working and stable Debian 9 AD system using one Samba server (version 4.9.5-Debian) and 4 x Windows 10 Pro clients.? The server has two shared folders - "Profiles" for roaming profiles and "users" for user's home directories. We've just got delivery of two donated computers, and we got 2 new staff members.? I

Hello all, I've got a simple active directory server set-up with 5 computers and about 5 users which works reasonably well, but recently, when an user changes to a different computer, it takes about a hour for the user to log in.  However, future log-ins on the same computer is pretty much instant, but the exact same problems occurs when the user changes computers - even to one

Hello all, Migrated a Windows 2000 server to Debian Sarge with Samba (3.0.10). Works nicely. But apparently there's a Microsoft Access database on this specific server that people have been using - apparently one of them add in information in the database, while the rest access the same database to read it only - apparently people can do that on the old server - i.e. one person opens it,

Rowland, Thank you so much for replying!  I'm not exactly sure of the issues, but it includes very slow log-in times (>30 minutes if I move to another computer I've not used previously) and the KDC doesn't work.  I've tried joining the two servers, but it stopped the new one from working entirely, and I had to wipe the server and start again.  I've now spent some time

Hi all, So I've set up a new Samba server for our small office.  As it's completely separate to the old one, I had to use rsync to transfer files over to the new server.  Unsurprisingly, the permissions on the freshly transferred files are incorrect - what's the best way to reset permissions? Many thanks! Cheers - Piers

Sigh, hopefully 3rd time lucky! Thank you Rowland and Louis, > > > > I do not use roaming profiles, but I seem to remember that > > they are are > > liberally plastered with SID-RID's. It is the SID that identifies the > > domain, so it is this that is probably causing your computers looking > > for the old DC. > > > > Rowland > >

Hello all, We're running a Samba AD DC and we want to move to a new server. The old server is slightly misconfigured and have some issues, and the new server has already been set up freshly set up with no issues and everything working fine.  I need to move users, groups & passwords from the old server to the new one without moving configuration and retaining the old issues, am hoping

Hi all, I've decided to completely replace an old AD with a fresh, brand new one - the only thing linking the two is that I've transferred the user profiles & home folders over to the new one and I'm testing this configuration by disconnecting one of the Windows 10 computers from the old AD and then connecting it to the new AD. Old AD: Name - ad.domain.intranet IP -

Hi all, An user queried whether the error "Your profile was not synchronised with the server" was a big problem, so I had a look into it.? This only happens on one computer, all non-admin users has this problem, the Samba admin account don't have this problem.? Looking into the windows error log, we get plenty of messages of the below:

On 18/07/2018 14:43, Rowland Penny wrote: > Go on, spoil us by actually giving us some information, such as what > distro is the DC running on ?, what is in smb.conf, what are your > clients running etc etc. > > Rowland > Hello Rowland, Gaiseric, LPH & Miguel, Thanks for all of your replies! Not having much time at the moment, but to answer some questions... The server is

There's a note at the top of that document: "Samba only supports logging of succeeded authorization events." Does that mean that it won't log authentication events at all? Because that's implied. I think it would be better, assuming it will log auth events, to say; "Samba only supports logging of *successful* authorization events, not unsuccessful. Samba also supports

Rowland, Thanks for your response.  That's the issue, I'm not sure what other details I can give that would be helpful in this situation!  How do I identify who owns what and how do I propogate this over?  I'm aware how to do chmod/chown and find out the uid for Linux users, but I'm not sure how it works for Samba - does Samba use the same uid as Linux users, or does Samba

Hello all, Am trying to set up a guest account for employees from other offices to come in the office to login and do stuff. I want to block access to all public drives so this is what I've done: Consider the SAMBA server in Office A and I want to create a guest account so that people from Office B and C can access. There is a public drive that everyone in Office A can edit, and a drive

Hi all, So we have a single AD-DC master, and I'm trying to join a fresh new DC (DOMAIN-ad.DOMAIN.intranet, 192.168.0.11) to the master (ad.DOMAIN.intranet, 192.168.0.17), and I'm using the HOWTO here: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory and I've hit a problem in the section "Built-in User & Group ID Mappings" - when

Hi this is really a last resort as I'm literally pulling my hair out over AIX and Samba and cannot find any threads on this particular issue. Basically we have 3 systems running AIX 5.1 and Samba 2.2.7 We upgraded one system to Aix 5.2 and everything works no problem. Upgraded the next two and both will not join the domain using the smbpasswd -j domain-name -r ny0000000 -U

Hello all, Have joined a new DC to an existing active directory consisting of a sole DC.  So, we now have two domain controllers, the original being ad.DOMAIN.intranet (192.168.0.17), and the new one being DOMAIN-ad.DOMAIN.intranet (192.168.0.11).  I want the new DC to become the FSMO role owner, so I followed the instructions here -

Thanks Rowland, OK, sorry about this... Note that the "Old AD" has some errors in their config files, but everything sort of work so I'm not going to fix those errors - my concern is obviously just the "New AD".  I've not set up printing in the new AD yet as it doesn't work in the old one anyway, and that's a discussion in a future thread.  Note

Hi all, A bug popped up recently when I upgraded to fedora core 2 (from core 1). Whenever I used the bitmap() function, ghostscript complained that it couldn't handle png or tiff devices. This was NOT a bug with R. It was with the version of ghostscript shipped with core 2. Going to rawhide and getting ghostscript 7.07-29 (core 2 comes with 7.07-25) solved this problem. Unfortunately, I

> That explains it a bit further, Samba (and Windows) uses the SID to > identify the domain, so user 'kit' with the SID-RID of > S-1-5-21-3690213834-1721161859-1610588051-1116 isn't the same user as > 'kit' with the SID-RID of > S-1-5-21-456595659-2484967225-2845901235-1104 That is from a Windows > perspective, how Unix treats them depends on how you are