search for: dahopkins

...WINDOWS directory (e.g. /home/student01/WINDOWS/TTL3.ini) With the old server, this file directory is recognized and the ini settings are applied. With the new server they are not. Additionally, on the Linux system, su - student01 just hangs. Same with any account. Similarly, running passwd dahopkins returns Changing password for user dahopkins. passwd: Authentication token manipulation error I guess things just aren't quite right yet. :0 So, can someone point me direction or offer a reason why the new server does not look the same to the Windows Terminal Server as far as account profile...

I need to move our existing Samba/LDAP PDC to another server. Currently it is on server1 and I want server2 to be the Samba/LDAP PDC instead. However, I am uncertain of what files need to be copied over to ensure that I don't have to rejoin machines to the domain. Searching the web I found information on creating the initial PDC setup, but nothing on moving the PDC. I also have a system

I have upgraded my Samba3+LDAP system to Samba 4 following the instructions given here: https://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO I did this on a test server (so I also moved the ldap database, installed openldap, etc). The installation passes all the simple tests suggested here:

This is in a test environment: Also, it is wordy, but I'm hoping it explains my scenario. I am migrating from a custom LDAP+Samba3 authentication solution to Samba4. I have used the classicupgrade option to pull off the data from the existing ldap server to populate the samba4 database. I've installed AD DS and Server for NIS tools on a Windows 2008 server that is connected to the Samba4

I have 2 Ubuntu 12.04/samba 4 servers acting as DCs for my Domain. I provisioned the Domain by using the classicupgrade (prior authentication was LDAP+Samba). I have added some new test users. I also have two files servers. One is running RHEL 5.9/Samba 3, the other Ubuntu 12.04/Samba 4. Users that have their home directories and profiles stored on the RHEL5.9/Samba 3 fileserver work correctly.

I installed wine using the fc5 repositories. # wine --version Wine 0.9.24 I then try to use winecfg and get: # winecfg wine: creating configuration directory '/root/.wine'... Failed to open the service control manager. It hangs here forever. However, it does create a wine directory with random extension: e.g. .wine-SMvQR6 Everytime I run the winecfg command, I get another

I am creating a user with samba-tool. I am essentially using the s4user script (very slight mods to echo some data and assign some site-specific data). The syntax in the script for a test user is samba-tool add user test.user47 Passw0rd! The echo'ed output is (including echo of entities that are to be set via ldbmodify) Creating s4 posix user test.user48 User 'test.user48' created

I need to migrate my current LDAP/SMB PDC to a new server. I found the information on how to replace an existing server with a new system with the same name, but in my case, I still need the existing system to continue as a slave LDAP/SMB BDC. I used slapcat to get the ldap database, and then used this ldif to create the new ldap database on the new server. Linux logins work fine. I used

I have a server that is not replicating correctly, but passes all the tests listed here: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC In particular running # host -t CNAME 976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.ncs.k12.de.us 976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.ncs.k12.de.us is an alias for ncssamba2.ncs.k12.de.us. returns correct information on all DCs.

Hello, I have an XP (SP2) CPU that has just been reloaded with the OS (hard drive was reformatted). The NIC works and I can access the Internet with no problem. When I join the CPU to the domain (there are many other CPUs already on this domain), it joins. After the mandatory reboot, if I try to log in using a domain account, I get an error saying the username and password are incorrect. I

I have samba4 installed on two systems: ncssamba1 and ncssamba2. ncssamba1 is the PDC, ncssamba2 was joined to the domain using the instructions here: http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC I had to manually add the DNS information as mentioned on that page. I can add a user and the user is replicated. However, I have some issues with DNS resolving hostnames.

I have been using Samba 2.2 with LDAP as a PDC for a domain for over a year in a gradeschool setting. Recently, users have been having problems with roaming profiles not working. And not all users, just some. I have applied the policy fix for CompatibleRUPSecurity, along with other suggestions, but I still get 'the profile cannot be loaded', Access is denied message for somce users. I

I have Samba 3.014a running. If I use the standard profiles definition: [profiles] path = /opt/samba/profiles writeable = yes browseable = no create mode = 0600 directory mode = 0700 then everything works fine. But changing just the path to path = /home/%U/profiles breaks it completely. I can curious why this doesn't work. The user that is logging in owns their

I have a very bizarre issue with Default User. I am running the latest version of Samba. I have created the netlogon share, and have added a Default User profile to it. I have Windows Server 2003 member server that is part of the domain. The exact same Default User profile is also located in Documents and Settings on this 2003 server. However, when users log on for the first time, sometimes

I have upgraded from Samba 3 to Samba 4 for authentication (Windows and Linux authentication are working). Samba 4 is acting as the DC. However, there are some issues that I can't resolve involving both profiles and automatic home folder mapping. I have 3 samba servers that are at Samba 3.5 (1 server) and 3.0 (2 servers). Prior to the upgrade, both roaming profiles and automatic mapping of

I have two samba 4 AD DC running using the internal DNS. On one of them, DNS will fail after a short time (10-15 minutes). Restarting samba on this AD DC corrects the issue temporarily. This behavior started about 2 weeks ago. We had not made any changes to either system during this time so it is a complete mystery. I unfortunately used the latest version of samba from git (4.2) for creating

When I try to add users or groups in Win2K via the Security tab -- Select Users or Groups, not all users or groups are displayed. Any account created since 1 January isn't showing up. I patched the Win2K server just before this date. All accounts that were creaated prior to this date still appear. On the Linux system which is acting as the Samba PDC (and is using ldap), pdbedit -l