Hello,

Most of our apps are working great on direct access.  We are unable to get our SVN app working.  Luckily only around 30 people use it but would be nice to get it working.   Anyone already dealt with svn not working?  

Appreciate the assistance.

Thanks

Whats SVN?

I don't think that I have ever worked with an app called SVN before, but I have been able to get many IPv4-only applications working over DirectAccess (assuming that is the issue with this one) with this utility: http://www.ivonetworks.com/news/2013/05/ivo-networks-announces-app46-for-directaccess/

 that APP which uses  server and client are those server and client capable of IPV6 ?

Just so all know, someone finally added ipv6 capability on TortoiseSVN.  You can get it here:  http://sourceforge.net/projects/tortoisesvn/files/1.8.7/Application/ipv6/

This works with Direct Access.

• Marked as answer by CSMatMan Friday, February 13, 2015 10:02 PM

Just so all know, someone finally added ipv6 capability on TortoiseSVN.  You can get it here:  http://sourceforge.net/projects/tortoisesvn/files/1.8.7/Application/ipv6/

This works with Direct Access.

• Marked as answer by CSMatMan Friday, February 13, 2015 10:02 PM

Just so all know, someone finally added ipv6 capability on TortoiseSVN.  You can get it here:  http://sourceforge.net/projects/tortoisesvn/files/1.8.7/Application/ipv6/

This works with Direct Access.

• Marked as answer by CSMatMan Friday, February 13, 2015 10:02 PM

I've just came across this thread and would like to clear up the situation of using Subversion client over DirectAccess (roughly speaking, DirectAccess is a VPN made by Microsoft) to connect to Subversion servers over HTTP(S) (e.g. VisualSVN Server, SVN Edge or some self-built and self-maintained httpd+svn server).

First and foremost, any Subversion client that supports HTTP(S) work over DirectAccess installed on Windows Server 2012 or which is installed as Forefront UAG component on Windows Server 2008 R2. However, there might be problems connecting with basic DirectAccess version installed on Windows Server 2008 R2 ("basic" version means "not UAG version").

Basic version of DirectAccess installed on Windows Server 2008 R2 requires the client to support IPv6, but some Subversion client distributions are compiled without IPv6 support, therefore they can't connect when working over DirectAccess. UAG and Windows Server 2012 version of DirectAccess do not have such limitation and work properly with IPv4-only clients. Here is a note about this DirectAccess limitation in Wikipedia, I guess there should be more authoritative sources.

If you are looking for Subversion client for Windows that supports IPv6, grap IPv6-enabled build of TortoiseSVN at http://sourceforge.net/projects/tortoisesvn/files/. Latest TortoiseSVN 1.8.x builds support IPv6 and you can download IPv6 enabled version in ipv6 folder. For example, TortoiseSVN 1.8.10 http://sourceforge.net/projects/tortoisesvn/files/1.8.10/Application/ipv6/.

See this users@ TortoiseSVN mailing list thread. There are more of them since this topic has been already bumped multiple times.

• Edited by bahrep 20 hours 24 minutes ago update
• Proposed as answer by bahrep 20 hours 24 minutes ago

I've just came across this thread and would like to clear up the situation of using Subversion client over DirectAccess (roughly speaking, DirectAccess is a VPN made by Microsoft) to connect to Subversion servers over HTTP(S) (e.g. VisualSVN Server, SVN Edge or some self-built and self-maintained httpd+svn server).

First and foremost, any Subversion client that supports HTTP(S) work over DirectAccess installed on Windows Server 2012 or which is installed as Forefront UAG component on Windows Server 2008 R2. However, there might be problems connecting with basic DirectAccess version installed on Windows Server 2008 R2 ("basic" version means "not UAG version").

Basic version of DirectAccess installed on Windows Server 2008 R2 requires the client to support IPv6, but some Subversion client distributions are compiled without IPv6 support, therefore they can't connect when working over DirectAccess. UAG and Windows Server 2012 version of DirectAccess do not have such limitation and work properly with IPv4-only clients. Here is a note about this DirectAccess limitation in Wikipedia, I guess there should be more authoritative sources.

If you are looking for Subversion client for Windows that supports IPv6, grap IPv6-enabled build of TortoiseSVN at http://sourceforge.net/projects/tortoisesvn/files/. Latest TortoiseSVN 1.8.x builds support IPv6 and you can download IPv6 enabled version in ipv6 folder. For example, TortoiseSVN 1.8.10 http://sourceforge.net/projects/tortoisesvn/files/1.8.10/Application/ipv6/.

See this users@ TortoiseSVN mailing list thread. There are more of them since this topic has been already bumped multiple times.

• Edited by bahrep Friday, February 27, 2015 3:03 PM update
• Proposed as answer by bahrep Friday, February 27, 2015 3:03 PM

I've just came across this thread and would like to clear up the situation of using Subversion client over DirectAccess (roughly speaking, DirectAccess is a VPN made by Microsoft) to connect to Subversion servers over HTTP(S) (e.g. VisualSVN Server, SVN Edge or some self-built and self-maintained httpd+svn server).

First and foremost, any Subversion client that supports HTTP(S) work over DirectAccess installed on Windows Server 2012 or which is installed as Forefront UAG component on Windows Server 2008 R2. However, there might be problems connecting with basic DirectAccess version installed on Windows Server 2008 R2 ("basic" version means "not UAG version").

Basic version of DirectAccess installed on Windows Server 2008 R2 requires the client to support IPv6, but some Subversion client distributions are compiled without IPv6 support, therefore they can't connect when working over DirectAccess. UAG and Windows Server 2012 version of DirectAccess do not have such limitation and work properly with IPv4-only clients. Here is a note about this DirectAccess limitation in Wikipedia, I guess there should be more authoritative sources.

If you are looking for Subversion client for Windows that supports IPv6, grap IPv6-enabled build of TortoiseSVN at http://sourceforge.net/projects/tortoisesvn/files/. Latest TortoiseSVN 1.8.x builds support IPv6 and you can download IPv6 enabled version in ipv6 folder. For example, TortoiseSVN 1.8.10 http://sourceforge.net/projects/tortoisesvn/files/1.8.10/Application/ipv6/.

See this users@ TortoiseSVN mailing list thread. There are more of them since this topic has been already bumped multiple times.

• Edited by bahrep Friday, February 27, 2015 3:03 PM update
• Proposed as answer by bahrep Friday, February 27, 2015 3:03 PM
• Marked as answer by CSMatMan 7 hours 16 minutes ago