> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: Tuesday, January 21, 2014 10:08 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Changing the server's ip has the system foobared
>
> On 21.01.2014 15:56, Sam Carleton wrote:
> > I am running a local instance of Subversion under Apache using SSL.
> I
> > have had to switch the IP address of my Apache server from 172.16.0.X
> > to 192.168.200.X. When I tried to connect with TortoiseSVN, it asked
> > for me to approve the new SSL but never the username/password, but
> > then gave a 501 error. Since I was running 1.8.2, I uninstalled,
> > deleted %APPDATA%\TortoiseSVN, and , upgraded to the latest tonight.
> > I still had the problems, so I went exploring and found the
> REPOSITORY
> > table in the .svn\wc.db, so I when off and did a relocate using the
> ip
> > address, successfully! The problem is this is a laptop and there are
> > times when I am not in the local network. Thus I need to use the
> full
> > domain address of the apache machine.
> >
> > So I then went in and deleted the row in the REPOSITORY table that
> > pointed to the full domain address and tried to relocate again and am
> > getting an error:
> >
> > OPTIONS request on '<respository>' failed: 501 Not Implemented
> >
> > But it still works fine using the IP address. So... how do I get it
> > working with the full domain name again.
>
> you actually messed with the database directly? And now you wonder why
> your setup is corrupted?
>
> First of all: Subversion and TSVN do have a command for this:
> "Relocate".
>
> Now, since you messed with the database manually, you have to check out
> a new fresh working copy and start over from there.
>
> Stefan
It sounds like he might have used the Relocate command.
I think the problem here is his router. The problem is that the routing is
broken because the name resolution provides an IP address that is not on
the local network. This gets sent to the router for the next hop but does
not get handled correctly.
Here is how to test my theory edit the file
C:\WINDOWS\system32\drivers\etc\hosts
Add a line to it
192.168.200.X <name of server>
Where name of server is the name of your server and 192.168.200.X is the
internal IP address of your server. This will cause windows to bypass the
DNS lookup and use the IP address you provided. This WILL break DNS for
the server outside your local network.
If this fixes you problem then you will either need to update the routing
table in your router (I don't know if this is even possible) or come up
with a solution to change the name resolution when you are on the local
network.
Wayne
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3071867
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-01-21 19:29:40 CET