4

I used to have a working Git installation on Windows, but for some reason, it's not working anymore, and I don't know what to do to fix it.

If I were to follow GitHub's setup tutorial, it says that all I'd need to do to verify things are copasetic is to type

ssh -T [email protected]

and when I do that, things are dandy:

C:\
> ssh -T [email protected]
Hi klauern! You've successfully authenticated, but GitHub does not provide shell access.

So I feel confident that I can clone one of my projects locally (such as a fork of a project I have):

C:\
> git clone [email protected]:klauern/ruby.git
Cloning into 'ruby'...
FATAL ERROR: Network error: Connection timed out
fatal: The remote end hung up unexpectedly

I can get through to this using an https:// protocol behind an HTTP proxy, but I should be able to go through the ssh protocol, too, right?

Edit

I'll add that I am using the windows install of Git from http://git-scm.com/, I have PuTTy and PAgeant installed and working, as well as a ~/.ssh folder with all the keys in it. As I'd mentioned above, this used to work, but now it doesn't, and the only test I know is ssh -T.

3

1 Answer 1

1

The question "How to make git to work with pagent(putty) on Windows?" mentions an issue with plink, related to issue 251.

This seams to be a bug in putty/plink: plink will just you the IP specified in Default Settings (putty) and ignore your command line hostname if you specify one.

The question "Can't Push Commits to Central Repository" also reminds us to check your origin declaration (git remote show origin)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .