Windows Server?

We are a Windows' shop, writing software that runs on Windows. Naturally, the network location I.T. provided for the repository is on a Windows server. I'm concerned with using file:// access once everyone starts using it in earnest, especially over a cross-continent VPN.

I suppose that git-daemon isn't available as a Windows service. I posted a short time ago asking about it, and the news did not seem good. So, is ssh a good second? That is, the manipulations of the central repo is being done by the machine that owns that disk, and the protocol talks between the two copies of git?

Is there anything that needs to be done on the server machine, other than having a SSH server, and formulating the path the way the disk really is on that machine (as opposed to the network share structure)?

--John (watch out for the footer...)

TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.
  If you received this in error, please contact the sender and delete the material from any computer.