How do I use SVN without disabling my firewall?

3 Answers

$0.25 tip awarded

santus_lupinus | 3 years, 3 months ago

I am not entirely sure of this firewall problem having never used Symantec myself, however, generally speaking, this sounds like a port problem. Generally speaking, programs use ports on the computer to shoot information at eachother. In this way, they can send multiple packets of information at a time. 200 sounds like a port number. Firewalls block packets of information when it notes traffic on channels that the program has not registered or is not registered for in its database, or on high-traffic or high-priority ports. Enable traffic in Symantec on port 200 with both options (TCP/UDP) and you should probably be able to make this error disappear. Failing that, you should be able to change the port to a different number in Tortise under options, which should solve the problem. If you get a similar error with the same number, you'll know that it's the port that's the problem, and that you should open the new port number.

You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.

Report Abuse

alfy | 3 years, 3 months ago

I have not used a symanted product in a long while but i'm thinking your firewall has a rule that blocks SVN.

Try looking at the firewall rules for one (or more) that specifically refer to the svn client and remove them.
If you can't find any then you should look for rules that block svn ports, if you have such rules and you do need them, i suggest you make a new rule that grants access to the SVN client specifically (by referring the exe file path) and set it with a higher priority than the existing rule

Report Abuse

athanaric | 3 years ago

I found out more about why this fails. I was having the same problem and did some network traces, it seems that Symantec changing is changing the headers the SVN client sends. In particular it is removing the
Accept-Encoding: svndiff1;q=0.9,svndiff;q=0.8
and replacing it with
---------------: ----------------------------
and adding
Accept-Encoding: gzip, deflate

This causes the client to get a response that is gziped and that it can't handle.

There is a firewall policy that can be changed for this, I don't know what it is as my machine is a managed client, but I contacted my IT department and they issued a new manged policy that allowed it to work now without the mangling of the headers.

Report Abuse

Spam (off topic & commercial)
Inappropriate (profanity, hate speech, or other violations per Terms of Service)
Plagiarism (copy and paste text without proper citations)
Illegal (fraud, phishing, violence, threats, privacy invasion, harm to minors)

Details

add an image by: URL,
Search,
Upload

Selected images:

save images cancel

add a video by URL:

Selected videos:

save videos cancel

add an audio by URL:

Selected audio:

save audio cancel

About This Question

This question has already been resolved. You may add an answer to it but you will not be eligible to win best answer or any associated tips.

This question has been viewed 405 times.