We have finally fixed it, although we sadly do not really know what the problem was. The magic medicine has been: run /netsh int ip reset c:\filename.log/, reset, reconfigure the network, and done! So it seems it was a client problem, but I don't really know even what kind of problem it was. Did it help anyone else?
-- View this message in context: http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193059.html Sent from the Subversion Users mailing list archive at Nabble.com.
