On Aug 18, 2006, at 17:07, Britt, Eli T wrote:
>>>>> I have set up Subversion on a small business network between two
>>>>> laptops running XP Pro. When I try to access the repository from
>>>>> using TortoiseSVN from a remote machine on this network, I get the
>>>>> error message" Error * Can't connect to host '': No connection
>>>>> could be made because the target machine actively refused it.".
>>>>
>>>> [snip]
>>>>
>>>>> I can access the repository without any problem on the machine it
>>>>> resides on.
>>>>
>>>> How is the repository being served? You mentioned svnserve.conf, so
>>>> presumably you're using svnserve?
>>>>
>>>> What is the URL of the repository?
>>>>
>>>> svnserve is presumably actually running on the server?
>>>>
>>>> Is there a firewall on the server that's blocking access to the
>>>> other
>>>> client? You would have to configure it to let traffic through on
>>>> the
>>>> svnserve port.
>>>
>>> No firewall on any of the boxes in my 3 box network. This network
>>> is for evaluation purposes only.
>>>
>>> Svnserve.exe is running on the server box in daemon mode.
>>>
>>> The repository url is svn:///148.34.137.2:3690/Work.
>>
>> Ah, we may have something: You need two slashes, not three: svn://
>> 148.34.137.2:3690/Work. With three slashes I get the error message
>> "svn: Unknown hostname ''" from the command-line client, which sounds
>> similar to what you're getting in TortoiseSVN.
>
> I was able to access the repository yesterday from the remote machine
> using the command line using "svn checkout file://148.34.137.2/Work
> c:\work in progress". Once I did that, I was also able to access it
> using TortoiseSVN. But today when I try it get the following:
>
> svn: Unable to open an ra_local session
> svn: Unable to open repository' file://148.34.137.2/Work'
> svn: Can't open file '\\148.34.137.2\Work\format': Access denied
>
> Any thoughts?
I wasn't aware the file protocol could be used in that way. I've only
ever used it for accessing files on the local machine, with file:///
path/to/repo. The file protocol in Subversion is good for testing and
if you're the only developer working on a local repository, but if
you're trying to get this to work in a client/server arrangement
across several machines, you should be using one of the other
protocols with a server process (like you're trying to do with
svnserve).
Please let's also keep the discussion on the mailing list so others
can make suggestions too. Use the Reply To All feature of your email
program when you reply.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 18 17:23:27 2006