TortoiseSVN 1.71 and VisualSVN 2.51 will not connect after update
I updated VisualSVN to v2.51 and TortoiseSVN to 1.7.1 at the same time a few days ago. Before the update, using subversion worked fine for many months. Ever since the update, I have not been able to connect to the repository.
The OS is Win7 Home Premium 64bit, Visual Studio Web Developer Express 2010 is installed, all Windows Updates have been applied automatically, and I used the apache server connection with SSL, which is the same as was working before. Also browsing the repository from VisualSVN works fine.
To demonstrate the problem in a simple way, I used a Command Prompt session to try to list the files in the repository and get the error shown below:
C:>svn ls "https://robert-pc/svn/Scedule/" --username xxx --password yyy<br>
svn: E175002: Unable to connect to a repository at URL 'https://robert-pc/svn/Schedule'
svn: E175002: OPTIONS of 'https://robert-pc/svn': Could not resolve hostname
`https://robert-pc/svn/': No such host is known.
(https://robert-pc)
The same error occurs if I try using TortoiseSVN from Windows Explorer. Based on the answer from a similar question in Nov, 2009, I tried the following without success:
- Specified the port number in the computer name, e.g.,
svn ls https://robert-pc:8443/svn/Schedule/ - Allowed SVN.exe (the one installed with VisualSVN) through the Windows firewall.
I have uninstalled and reinstalled both VisualSVN and TortoiseSVN to no available. I don't see where anyone else has had a problem using VisualSVN v2.51 and TortoiseSVN v1.7.1. I wonder if the problem is how the Windows Network is configured. The Network is a simple local network configured as a Work Network under Windows 7 Home Premium. Any help is greatly appreciated.
I can successfully ping robert-pc from a Command Prompt session. I can browse the repository successfully from IE as follows: https://robert-pc:8443/svn/
(I get a certificate warning from IE, which I continue through, and then I enter a username and password.)
Answer
Your problem isn't VisualSVNServer or TSVN, and it was written in pure plain English
Could not resolve hostname `https://robert-pc/svn/': No such host is known.
Could not resolve hostname means you must get in your Windows at least ping robert-pc without errors before complaint to connect
I don't know, from which source robert-pc resolved before and who broke it now, but you have to restore old settings (hosts, local DNS-server)