[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

remote svnserve access using tortoise

From: John Meloro <john.meloro_at_gmail.com>
Date: Thu, 17 Jul 2008 20:17:15 -0400

Hi Si,

Just a final email to say THANK YOU!

NMAP did the trick!

Using it I saw that port 3690 was 'filtered' even after I turned off
the Firewall I was using.

What happened is that I forgot about the Windows Firewall!

Which seemed to be turned on even after I turned it off

I have access now to my repository through svnserve and remotely!

Thank You again,
John M.

Hi John,

> I can successfully run the following two commands on the server side svn
> info svn:\\192.168.1.100\code and svn list svn:\\192.168.1.100 locally,
>
> I can successfully run the tortoise repo browser from the server locally
> with the following url: svn:\\192.168.1.100/code.

Assuming you're entering // instead of \\, it does smell like a
firewall or port forwarding issue.

Grab a copy of nmap or similar and on the client try:

nmap 192.168.1.100 -p3690

assuming you're running off the default svnserve port of 3690, you should see:

PORT STATE
3690/tcp open

If state is not open (filtered or closed) then it's more than likely a
network issue.

Actually, a quicker way is to fire up your web browser and enter url:
http://192.168.1.100:3690/
You should see something like:
( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries
commit-revprops depth log-revprops partial-replay ) ) )

My gut feeling is you have a router that needs port 3690 forwarded to
192.168.1.100.

cheers
si

p.s. this type of question is more suited to the svn users mailing
list rather than TortoiseSVN, but no dramas.
Received on 2008-07-18 07:01:45 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.