![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
First of all, let me state that I am not a Linux guy (nothing against it, I just know barely anything). Moving on to the problem ...
My work is primarily a Microsoft network -- AD domain on Server 2003, most of the servers are running some form of Server 2003, but we do have a few Linux boxes hosting legacy apps.
One of the boxes is our source control repository called Subversion. It uses Apache 2 to authenticate user identities (usually from the developer using TortoiseSVN from a Windows dev box) through LDAP to our domain controller. There are no account details stored on the box, it only checks the username/password against AD. The Subversion config file does not have any statements of denying users, and anyone has free reign to commit/update as needed.
The problem is that TortoiseSVN refuses to authenticate and commit changes. Doing an "update" through TortoiseSVN works without a problem. It's isolated to the "commits". This started as only affecting a few AD user accounts, but this number has been steadily growing.
Additionally, I can use another user account on our domain, and the commits/updates work just fine against the repository.
My best guess is that something inside the Subversion service on the Linux box got hung-up with doing *something* that a user requested, and is still hung up on finishing the process/task that the user account started. Restarting the Linux box doesn't solve the problem, and I'm not sure where/how in Linux to check the state of this (if this is even possible or likely).
Does this make sense at all to anyone? I'm really at a loss on where to continue digging, and have been scouring random Google searches. I'm still digging online for a possible solution, but if anyone has any suggestions or further questions then please post them.
My work is primarily a Microsoft network -- AD domain on Server 2003, most of the servers are running some form of Server 2003, but we do have a few Linux boxes hosting legacy apps.
One of the boxes is our source control repository called Subversion. It uses Apache 2 to authenticate user identities (usually from the developer using TortoiseSVN from a Windows dev box) through LDAP to our domain controller. There are no account details stored on the box, it only checks the username/password against AD. The Subversion config file does not have any statements of denying users, and anyone has free reign to commit/update as needed.
The problem is that TortoiseSVN refuses to authenticate and commit changes. Doing an "update" through TortoiseSVN works without a problem. It's isolated to the "commits". This started as only affecting a few AD user accounts, but this number has been steadily growing.
Additionally, I can use another user account on our domain, and the commits/updates work just fine against the repository.
My best guess is that something inside the Subversion service on the Linux box got hung-up with doing *something* that a user requested, and is still hung up on finishing the process/task that the user account started. Restarting the Linux box doesn't solve the problem, and I'm not sure where/how in Linux to check the state of this (if this is even possible or likely).
Does this make sense at all to anyone? I'm really at a loss on where to continue digging, and have been scouring random Google searches. I'm still digging online for a possible solution, but if anyone has any suggestions or further questions then please post them.