On Nov 19, 2005, at 22:56, John F. Schank III wrote:
> On Nov 19, 2005, at 1:44 PM, Ryan Schmidt wrote:
>> On Nov 19, 2005, at 04:02, John F. Schank III wrote:
>>> On the server I run svnserve --daemon --root=Path/To/Repos; Using
>>> my appropriate paths... svnserve is run as user=svn a restricted
>>> 1) If I try to access the repository ON the server using local
>>> host - it works
>>> 2) If I try to access the repository from a machine on my
>>> network, using my domain name, like so svn://www.schankopolis.com/
>>> Project, Then I get an error that says "svn: Can't connect to
>>> host 'www.schankopolis.com': Address already in use", but only
>>> after I hit ctrl-c to break out of the call. Otherwise it will
>>> just time out.
>>> 3) However!, if I use the bonjour name for the remote computer
>>> (we happen to be on the same subnet) as so: svn://cooper.local/
>>> Project it will work fine.
>> Can you confirm with nslookup or dig that www.schankopolis.com and
>> cooper.local do in fact resolve to the same IP address?
>> Does it work if you try accessing the repository with the IP
>> address, like svn ls svn://18.104.22.168/Project ?
> Actually www.schankopolis.com and cooper.local do not resolve to
> the same IP address...
> The schankopolis IP is the WAN IP of my router. While cooper.local
> is a DHCP assigned IP on my LAN. (Assigned from the router. Always
> the same IP, and the LAN IP is the DMZ IP for the router. So all
> ports get automatically forwarded to this PC on my LAN. Also, using
> the IP address instead of the name makes no difference.
> This sounds like it is the heart of the problem. However, Apache
> has no problems working this way. Nor does FTP, SSH or any other
> listener I have (that I know of), Is there some way I can make
> svnserve work in this network configuration?
I don't know... Sending it back to the list; maybe someone else knows.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Nov 19 23:18:31 2005