Solution 1:

YES,

Usually corporate networks are behind proxy. Try to find your git repo server public IP (google it), ping it. If it isn't working you are probably behind a proxy server. If you are behind proxy use:

git config --global http.proxy http://proxy_address:proxy_port

git clone http://.../..

You can find proxy address in internet explorer properties\Connections\LAN Settings

enter image description here

If git has still problem resolving address you could try putting git repo public IP DNS to C:\Windows\System32\drivers\etc\hosts file. Git will resolve DNS locally and use proxy for connection.

Here are some additional methods how you can discover proxy:

  1. Open IE, browse to some page next run from cmd:

netstat -ban

(it requires elevated command prompt - probably you can't do it on the corporate computer)

on the left sight under [IEXPLORER.EXE] is your IP on the right sight should be proxy IP and port.

enter image description here

  1. run:

ipconfig /all - find your DNS suffix

ping wpad.suffix or ping wpad

Now use the IP address returned by the ping command and us it in your browser:

http://ipaddress/wpad.dat

It will download wpad.dat file in which you can find line "PROXY ..." containing IP and port of your proxy.

Solution 2:

I often use an external, browser based, dns/ip lookup tool, like GetIP, to get the ip address of a server I'm trying to connect to. Then you can use the address for git, svn, etc as long as it's not explicitly blocked by your corporate firewall or proxy.