Can you explain why OpenSSH would corrupt my Active Directory domain?
Here's the scenario. I co-admin a company which we set up on Active Directory with Roaming Profiles. The person in charge wanted a way to VPN into her desktop from her laptop. I decided on UltraVPN. I used no-ip for the dynapic IP and I was setting up tunneling through OpenSSH. Not being on the server I set up OpenSSH and UltraVPN on a computer in the domain as a domain admin (I wasn't thinking). I wasn't planning on pushing it yet but I needed to do some work with it and I wanted to set it up so SSH would auto authenticate without having to log in through Putty. The person in charge is AOL in level and anything more than pushing a connect button is above her. I had to run out to Wal Mart and when I came back all hell had broke loose. The computers were logging in dog slow, some couldn't log in or get on the web at all, resources were missing, etc. It took 3 hours to get everything back up and most of the computers had to be rolled back. I deleted everything for OpenSSH and Cygwin and UltraVNC it still didn't help. I honestly couldn't think why something installed on a local machine like that could cause the problems they did. Then I remembered the script for OpenSSH pulls out the users on the local computer or domain for login. It creates the keys you need, etc. I saw a warning about running it on a domain. Why would this cause these problems?
|