>From what I know, VisualSVN Server only uses the port specified in the management tool.
The only way that VisualSVN Server could be responding is if the router is configured to forward requests for a port to the server and that happens to be the port VisualSVN Server is using. What port is VisualSVN Server using and what ports is your router forwarding? Once this is all straightened out, yes, you should be able to connect via VPN and then use the local address (or name) of the server to get to your repositories. On Tue, May 4, 2010 at 9:59 PM, Steverino <sjgar...@gmail.com> wrote: > Hi, > > I'm not a complete network neophyte, but I'm unsure where to start on > this one. > > Have single public ip address, with a locally addressed Win Server > 2008 behind it running VisualSVN. Seems to be running fine from > within the local net. > > I don't necessarily need it directly accessible from the Internet. I > would like to have access from outside the local net, but had planned > to connect with VPN to do so. > > The current problem: if from the Internet I attempt to secure https > connect to my router (the bearer of the public address), instead of > the router answering, VisualSVN answers. > > The router seems to be passing more than it should, and that is a > problem to be fixed at the router. Question: what are the ports > VisualSVN uses that should not be passed through? > > Next question: when I do connect remotely via VPN, I expect to be able > to use SVN (tortoise on my client) to use the VisualSVN server. This > should work, right? > > Thanks, > Steve >
