title: tortoisesvn unable to connect to repository
body: <p>I am embarrassed to ask this question because of my knowledge and past experience and because of the popularity of the question. But I'm so frustrated I'm hoping someone can help me. I've spent hours on this already. I've searched the net, searched these forums, and read some documentation.</p>
  
  <p>I am trying to get my TortoiseSVN client to work with my Collabnet Subversion Edge again after a few years of not doing any programming development. Everything runs on one Windows machine. </p>
  
  <p>The Apache server and subversion server are both running (apparently fine), and I can easily access all my repositories with the two http: links on the Edge administration page. (<a href="https://host/svn" rel="nofollow noreferrer">https://host/svn</a> and <a href="https://host/viewvc" rel="nofollow noreferrer">https://host/viewvc</a>). </p>
  
  <p>I have checked the httpd.conf files, and all the pathnames to the repositories seem to be correct. (Edge writes them out from the browser admin page.)</p>
  
  <p>If I use a file:///xxx URL in Tortoise, I can see my repositories just fine, so they are well formed and not corrupted.</p>
  
  <p>But the Tortoise client won't connect to the subversion server, no matter what syntax I try. I get a series of variations of the usual messages about not being able to connect to the URL, to the host, or to a repository, or whatever. The messages vary a bit depending on what I enter in the search bar.</p>
  
  <p>The most popular messages are </p>
  
  <pre><code>(for svn://myhostname/myrep) "No connection could be made because the target machine actively refused it."
  
  (for http://myhostname/myrep) "Unable to connect to a repository at URL xxx"
  </code></pre>
  
  <p>I've also cleared the Saved Data caches in TSVN where they seemed appropriate.</p>
  
  <p>The frustrating thing was that all this software worked for a year or two in the past. I am hoping that someone can give me a few command lines to type, or a few files to check to get me going again. The only that has changed since everything worked was that I changed to a bigger disk drive, and changed the location of the repositories. Nothing else at all.</p>
  
  <p>Thank you. Here's hoping...</p>