similar to: hardware change

Hi all. Last thursday I've had to restore my customer's pdc from an hdd failure, and by the evening I restored a full working state of server and clients, rejoining all of them to the domain. Next morning the customer called me saying that nothing was working, I looked the server from remote without finding failures and then I went there: I found that clients couldn't find the pdc

Hi Folks, as promised, here's what I did to get net rpc vampire working. There's a question at the bottom that someone might be able to answer for me. If the detail below is sane, I'll tidy it up some and submit it as a proper HOWTO. If not, please tell me where I'm being insane :) ====================================================================== Using 'net rpc

Hi everybody, I'm an italian system administration (newbie about Samba). I have installed on Mandrake 9.1 the rpm samba3-*-3.0.2a downloaded from a Samba.org's mirror. I have configured a PDC based on ldapsam (OpenLDAP 2.1.29) that works fine, i use smbldap tools to manage sincronization account. Now the problem, when I try from my W2000 Workstation to change my domain password I reach

I'm running Centos 4.2, with 3.0.23b-SerNet-RedHat as a NT 4 Domain. My Window XP machine logs in perfectly well to the domain. I have another machine running Opensuse 10.2 which I joined to the domain with no problems. using opensuse, I'm unable to loging to the domain. I get the message xserver: login (domain\user) is disabled. On the server samba.conf the shell is set to template shell

So, I followed these directions and got errors in log.nmbd regarding "domain_master_node_status_fail". There were still entries for the old server's ip address in connections.tdb, gencache.tdb, locking.tdb and sessionid.tdb, so I stopped samba, deleted them and restarted. All was well. I then changed the SID using "net setlocalsid

hi, i just configure a samba box to be a PDC for my entire win98se netrowk, but im having this errors on log.user1: [2005/10/01 00:17:24, 2] lib/access.c:check_access(324) Allowed connection from (192.168.1.21) [2005/10/01 00:17:24, 1] smbd/service.c:make_connection_snum(705) sergio (192.168.1.21) connect to service netlogon initially as user sergio (uid=503, gid=503) (pid 6542) [2005/10/01

Hi John, > I understand that Samba doesn't support domain renaming, which is why > I'm looking for a way to export the data from one domain and import it > into a new one. Passwords and machine accounts are not a problem and can > be ignored for this exercise. The key things I need to copy across are > user accounts and groups, as they would be an absolute pain in the rear

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Assuming they exist, could someone point me to any resources that could assist me in renaming a Samba PDC's hostname and the domain it serves remotely *without* forcing the client workstations to have to manually-rejoin? If such things do not exist, 1) what effects should I expect in undertaking such an action, and 2) is there a standard

Hey guys, I'm trying to migrate my NT4 Domain and am having some problems. Ignoring my other post related to this, I can't get any of my machines to be able to login. Alls I ever get is "Your computer account was not found or the password is incorrect" I even tried rejoining the domain which works. I leave the domain and then rejoin it, it takes a LONG time (might just be

Im getting an erro while joing my domain in AD windows 2003 [root@TESTSERVER etc]# net ads join -Uadministrator%password Using short domain name -- FAMILYENRICHMEN Failed to set servicePrincipalNames. Please ensure that the DNS domain of this server matches the AD domain, Or rejoin with using Domain Admin credentials. Deleted account for 'TESTSERVER' in realm

One topic I can't find in either Samba 3 by Example or the Offical Samba 3 Howto & Reference Guide is that of migrating from a Samba3 server to a newer Samba 3 server (meaning newer hardware in this case). We are currently using the smbpasswd backend. I plan to move to tdbsam but that hasn't been done yet. All of the servers in question are running either whitebox 3 or redhat 9

Hello, I just upgraded from Samba 2.2.7 to Samba 3.0.0 on RedHat 9. I did this by uninstalling the 2.2.7 samba RPM's and then applying the Samba 3.0.0 RPM from samba.org, then putting my local changes back into smb.conf. I have also migrated my smb users from smbpasswd to tdbsam with the pdbedit utility as discussed in the HOWTO. It seems I have to rejoin my client boxes (windows 2000 pro)

when an nt 4.0 workstation or backup domain controller is joined to a domain, the trust account password is set to a well-known initial value. if you are concerned about internal network security, this is not really an acceptable risk: any captured network traffic can be decoded simply from knowing the name of the workstation, which is contained in the network traffic itself. the initial value

This isn't looking like a samba problem, but thought I'd ask just in case. I'm running samba 3.0.10 on Debian stable as a PDC. I have a Windows 2000 Server which was happily part of the domain until this morning. This morning users couldn't use an application whose database files are on the w2k machine, the symptoms looking like the users weren't authenticating to the

On Sun, Aug 13, 2017 at 9:03 AM, Ian <yoitsmeremember at gmail.com> wrote: > > Finally, it could be down to windows updates, try adding this to your >> smb.conf: >> >> server max protocol = NT1 >> > > Thanks, I'll give this a try shortly. > So when I went to test this I rebuilt samba46 (enough dependencies had changed since I last built it) and

hi everybody I'm thinking I'll grab whole lot of my ldap backend and change SID - what will this cause to workstation/machine members? I'm guessing users account should be fine and people would be able to log in but machine would probably have to rejoin (if I can call it that, because domain name is different). You probably already see what I'm hoping I can do - I hope I can

Hi all, I am migrating a Samba 3 domain from an ageing server to a new server. I've exported all users from the old server and imported them on the new server using the following command (LDAP to TdbSam): pdbedit -i ldapsam:ldap://127.0.0.1 -e tdbsam:/tmp/tdbsam.agix scp /tmp/tdbsam.agix new.server.local:/etc/samba/passdb.tdb I've set the same SID on the new server. Windows7

Can anyone point me to a guide on migrating Linux and Samba accounts to LDAP? I can only find part guides, and I can't figure out how to get the account data combined (without a lot of manual effort). I can get the Linux accounts over no problems. I then tried to do "pdbedit -i tdbsam -e ldapsame -s /path/to/modified/smb.conf", but it only manages to stuff things up by skipping

When I migrated our Samba PDC from version 2.2.7 to 3.0, I was forced to have the 4 machines we are using rejoin our domain, because the SID had changed. Since then, users have been able to log on, but any attempt to start IE, or Outlook fails, apparently because something in the user's profile cannot be accessed due to the SID modification, and the icons in the WinXP start menu have

I'm about to give up. It's been months now that I've been playing around with Samba 3.0. I've downloaded their documentation. Tried to follow it as much as possible, but I'm getting no where with adding machine accounts to a Domain, real fast. I've asked this question a couple of times at the Samba Mailing list, but have gotten no reply(probably my fault, not enough info).