For Git Bash

If you are running msysgit (I am assuming you are) and are looking to run Git Bash (I recommend it over TortoiseGit, but I lean to the CLI more than GUI now), you need to figure out what your home directory is for Git Bash by starting it then type pwd (On Windows 7, it will be something like C:\Users\phsr I think). While you're in Git Bash, you should mkdir .ssh.

After you have the home directory, and a .ssh folder under that, you want to open PuTTYgen and open the key (.ppk file) you have previously created. Once your key is open, you want to select Conversions -> Export OpenSSH key and save it to HOME\.ssh\id_rsa. After you have the key at that location, Git Bash will recognize the key and use it.

Note: Comments indicate that this doesn't work in all cases. You may need to copy the OpenSSH key to Program Files\Git\.ssh\id_rsa (or Program Files (x86)\Git\.ssh\id_rsa).

For TortoiseGit

When using TortoiseGit, you need to set the SSH key via pacey's directions. You need to do that for every repository you are using TortoiseGit with.

It rather sounds like a strange replication or authentication problem. It certainly does not come from domain and schema master roles not have been moved to the new DCs. I would advise against moving roles as this truly might break something - although probably not permanently.

You should try the following steps:

• remove DC2 from the domain, delete its machine account and re-join it
• use the Windows Server 2003 netdiag and dcdiag tools on DC01 and DC02 to check for possible problems with network services configuration or directory services contents
• use the Windows Server 2008 dcdiag tool to check for possible networking or directory problems on DC1
• try temporatily disabling the firewall on DC1 and re-try replication (just in case your firewall rules screwed up for some reason)