| How To Make P2P Programs to Work on Networks Using a Broadband Router | |
| By Gabriel Torres on February 15, 2007 | Page 2 of 5 |
Configuring Windows XP Firewall Windows XP SP2 has an internal firewall that blocks P2P connections (if you don’t have SP2 installed you won’t have Windows Firewall installed). So we must configure Windows XP in order to “open” the ports used. If you have another firewall program installed such as ZoneAlarm or Norton Personal Firewall, you will need to make this procedure on your firewall program. After running your P2P program for the first time you probably unblocked it on Windows Firewall (by clicking on Unblock on the screen shown on Figure 5) but this isn’t enough.
Open Control Panel, Windows Firewall and click on Exceptions tab. Your P2P program will probably be already listed there, as you can see on Figure 6, where eMule was already being listed. If not, click on Add program and choose your P2P program.
Even if your P2P program is already listed on Windows Firewall Exceptions tab you need to click on Add port. Then give a name to this rule (e.g. “eMule TCP Port”), add the TCP port number that eMule uses (4660), select “TCP” and click Ok (see Figure 7).
Then click again on Add port, give a name to this rule (e.g. “eMule UDP Port”), add the UDP port number that eMule uses (4670), select “UDP” and click Ok (see Figure 8).
These new rules will now be listed on Windows Firewall Exceptions tab, see Figure 9.
But that isn’t all. We still need to add one more configuration to Windows Firewall. | |
| Originally at http://www.hardwaresecrets.com/article/423/2 | Pages (5): 1 2 3 4 5 » |
© 2004-8, Hardware Secrets, LLC. All Rights Reserved. Total or partial reproduction of the contents of this site, as well as that of the texts available for downloading, be this in the electronic media, in print, or any other form of distribution, is expressly forbidden. Those who do not comply with these copyright laws will be indicted and punished according to the International Copyrights Law. We do not take responsibility for material damage of any kind caused by the use of information contained in Hardware Secrets. | |