similar to: Possible PDC security hole r

Hey all! I was fiddling with some LDAP stuff for fun's sake, and I ran into this strange situation. The situation occurred with both my stock Samba and my modifications applied. I had a Win2000 Advanced Server machine already joined into the domain and working perfectly with PDC logons through the Samba server (v2.2.7, LDAP-SAM backend, OpenLDAP 2.0.25). While testing if the searches were

I thought that it was quite impossible to do that due to the Domain SID as well as the SAM list that currently Samba is unable to retrieve. (Not that it would have helped me any, since our old NT 4.0 PDC took a major Hardware failure.) How would one duplicate the SID, is that possible with 'smbpasswd -S' from the new Samba DC? Regards, Robert Adkins II IT Manager/Buyer Impel

I ran into a similar problem with one of my machines. I simply couldn't quite understand why it happened. I did destroy and recreate the machine account and it still persisted. I ended up changing the machine name and creating a new machine name for the system. That is the only fix that I am aware of at this time. Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph.

When you mean register the client, are you meaning "Join the Domain"? Unless I am mistaken, I believe the machine account that you had to create using smbpasswd creates the SID in the smbpasswd file, if you copy that file over to the new server, and also copy over all the netlogon information, profiles and such. Then you should have no issues and it will be

Simon, What version of Windows XP are you using? If your client has purchased computers from Best Buy or a similar electronics "mega-store" they likely received WinXP Home Edition. (Which is what it sounds like based upon the use of Win9x machines you mentioned.) If that is the case, then you will be unable to get the WinXP machines to see the Samba Server (or a Windows

Additional Info... I am beginning to think that a file called 'secrets.tdb' might be what I am looking for. Inside that file is something mentioning SID. Of course, it also mentions the name of the PDC. If that is the file I am supposed to copy over. Then it is done. However, I still need a little more input for setting up a Samba BDC. With a Samba BDC, should I leave the

PDC RH9 running v2.2.7-a-8.9.0 from RH Member RH73 running v2.2.7-3.7.3 from RH both are up to date with regards to RH Would like the Member server to authenticate against the PDC rather than locally to itself causing me to keep auth all synced up between the two. Yes LDAP is an option as we already use it, but was waiting for ver 3 to go down this road as we don't like to compile because of

Hi all, I read a few posts a while back from people who were trying to get this done. Has anyone succeeded in doing a transparent (or an as-close-to-as-possible) migration of an NT4 PDC to a Samba PDC? I know it entails stuff like snatching the passwords with pwdump or the like, and importing them into smbpasswd/LDAP, and toying around with RID's/SID's for the new PDC to make it look

Racer X, The simple answer I have; No Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx. 586-254-5804 -----Original Message----- From: Racer X [mailto:racer_x_0x0@yahoo.com] Sent: Tuesday, January 14, 2003 1:27 PM To: samba@lists.samba.org; Robert Adkins Subject: [Samba] Password protect shares without creating user accounts Hi, Could you tell

Ralf, I am using Samba 2.2.5-10 and haven't had any issues with getting Win2K clients to connect to the domain after getting Samba properly configured as a PDC. It could be a minor configuration issue. Although, in my reading I could only get confirmation that Samba 2.2.5-x would work with Windows 2000 Clients regardless of the Service Pack level. You might need to take a

Hello all. First, a little background... I recently downloaded samba-*-ldap-2.2.5-2mdk , installed on Mandrake 8.2 and got everything working fine. I have LDAP installed for "single sign-on" support. I can use LDAP to authenticate other Linux boxes, and have Samba as a PDC for some Win2000 boxes - all working fine. Linux users are the same as PDC users, except for their passwords

DrTebi, I would setup a VPN (Which is outside the scope of this list) tunnel into your machine running Samba. Then you could use Samba as though you were locally connected to the network the Samba server is living on. Other then that, I wouldn't recommend using Samba connected directly to the internet. Of course, that is based upon my limited knowledge of Samba and network

I am unsure if that is quite possible... However, I think that it would be best to address this to a Windows Mailing list of some sort. There may well be an answer that you can alter to work with whatever Samba installation that you have. Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx. 586-254-5804 -----Original Message----- From:

Randy, I believe that it is a simple matter of calling out the local path that you wish to have profiles placed on each machine, in the smb.conf. Example: logon path = C:\Documents and Settings\%u The above should work, for you. I haven't done so myself, since each user on my network has their own unique mailbox, which is saved onto the server when they log off. Which is very

Jim, Perhaps you should forward your concerns to the OpenLDAP developers list and hopefully they can work out something to streamline the process. Perhaps they are already working on streamlining the system and require some help in tightening up some of their ideas. I am sure that they would welcome any suggestions that you may have. Of course, some of the issues that you have

Everyone could setup an auto-responder to send replies to his E-mail address that contains instructions on how to properly setup his mail filters to skip the auto reply to this and any other mailing lists he is associated with. Perhaps when his company sees the incredible slow-down on their mail server and investigates the issue. They could unplug his machine from their network,

Brendan, Unless I am seriously mistaken, I believe that by adding this 'wide links = no' to each share section will end the ability to create and use symlinks on your shares. I am unsure why anyone would want to really include symlinks into a Samba share. Does anyone care to enlighten me? Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx.

Yes, there is a line in the smb.conf called 'domain admin group =' Just put the UNIX group name that you wish to have admin rights on Windows to there. Then open up your group file and add whomever needs those rights on the system. I have found that needs to be done the first time that a user account is setup on a Windows workstation when Office needs to install a few files

I believe that your issue is related to UNIX permissions. The location of your profiles directory must be set to allow all users R/W to it. Create a new group in your group file and add every user to it. Then change the ownership of the profiles directory. Also make sure that all of your users have R/W permissions on that directory. Regards, Robert Adkins II IT Manager/Buyer Impel

Colin, I know that on Windows, when you copy and Immensely large single file, there are times when it will show something like 100 years in minutes to complete the copy. Your issue could be related to that issue with Windows. You say that you copy files over from several other systems without a problem. Are those files on the other systems single small files or are they also in