You can run a scan of your computer at Symantec. If you are running a firewall, be forwarned you will get alerts generated by this.

Use the --accept-all switch. This sets the default policy to "accept"; flushes all firewall rules and removes chains. This allows any incoming and outgoing traffic.

Since this script cannot possibly include every service out there, you can easily create your own script with the example provided in the file: /etc/firewall/modules/public/services/tcp-clients-template Copy the file to the relevant directory in the firewall-modules hierarchy and edit it to suit your needs. Run RCF with the --update-config parameter and edit your newly created options in /etc/firewall.conf. Upon restart of the firewall, your script should be executed.

Use the --[accept|deny|forward]-[int]-[serv]-[hosts|servers|clients|ports|rhostlports] {host|ip|subnet} {...} switch. Adds a temporary entry to a configuration option; Useful when you want to open-up a service "on the fly". These settings will be lost the next time the firewall is executed.

All Clients first contact the Server on port 2774, or 21, or whatever you have defined as your main port number. The Server then tells the Client to call back on a different port number to send its data. Each client that calls in simultaneously will get a different port number called the "Data Port," and may attempt to use as many as five ports, depending on bandwidth availability. That way the Server can handle many simultaneous users.

From a security standpoint, TCP and UDP ports on your system are divided into several groups according to their probability of being used by an attacker. Attempts to access ports that are assigned to vulnerable services like DCOM or RPC should be seen as serious indications that you are being maliciously probed. Vulnerable ports are divided in two groups: System and Trojan. System ports are vulnerable because they are often open for everyday system services.

On the SRB server server-side, you must open the port that the srbMaster is listening on, plus a set of 100 or so configurable data ports (described below). The srbMaster listens on the port defined in srb.h or specified in srbPort environment variable (often set in the runsrb script). By default, srb.h has DefaultPort "5544" but this can be changed via the configure --enable-srbport=value option.

Port 80 (http) is used for most communications with the project servers. Port 443 (https) is used if the password is being exchanged . Ports 1043 and 31416 are used for local control as well as for remote control of a BOINC client. 1043 is preferred and 31416 is a fall back. Unless you are RPC'ing over the Internet don't open 1043 and 31416 in your non-local firewall specifically for BOINC.

You need to be able to establish outgoing connections on ports 4038 and 4039. For optimal performance, you need both incoming and outgoing connectivity on port 4137. You may not change the ports that BitWise uses. Allowing different ports would substantially detract from the ease of communication among BitWise users.

If you have questions regarding the compatibility of your router with your new VoIP service you should contact the router manufacturer directly. Some of the most common manufacturers' tech support numbers and web sites are listed below. If you do not see your router manufacturer's information listed above, please refer to their website for further information. Most likely the VoIP device you received is not registered with PhoneOverNet.

You will need to open a bi-directional port in the firewall, this is set to 10622 by default but can be configured to a different port, however higher is prefered. This is the port that the OpenHand server will listen on, it will only respond to requests from a device using an OpenHand client. All other requests will be denied. You will also need to set a NAT rule to reflect the internal address of your OpenHand server

To "close" a port, you need to shut down any programs that are listening on that port. Instructions on how to shut down various programs are included in the Port Scan Recommendation email (see bottom of Port Scan) and in all the results in the Test Results area.

You need to open port 4242, in addition to any steam ports, on your firewall, to play Ragdoll Kung Fu online. (for both TCP & UDP). How you open these ports depends on what firewall and router you use; please see the documentation for your firewall for more information. Try the FAQ run by our amazing fansite, www.rdkf.net. They've got even more info there.If that doesn't help, you could try reading and posting on the Rag Doll Kung Fu forums here.

There are no ports blocked to and from WH-Netz. If your computer uses a IP address that begins with 10., your computer will not be reachable from the internet. How do I run my favourite filesharing tool? Our network is for science and education ONLY!! We will not support your filesharing client and we try to avert any filesharing usage.

No. PocketVPNs proprietary protocol tunnels over HTTP or HTTPS, and can even be installed on the same server as other network asset such as Microsoft Exchange Front-end. If you are using BES then PocketVPN doesn't even need to be accessible from the Internet.

The main port used by P2P-Radio is the port 2000 (UDP & TCP). This port must be accessible from the Internet. The port 2001 (TCP) is used for communicating with your media player. P2P-Radio only accepts connections from the local machine on this port. Connection requests from the Internet will be rejected. A web page with detailed information is available on port 2002 (TCP). You may also make this port accessible from the Internet.

No, but port 2641 is the ICANN registered handle port. You may choose which ports you would like your handle server to run on during the installation (Simple Setup) but remember that no other processes, i.e., a web server, can be running on the same ports as your handle server. Yes, the handle server uses its own ports. You will need to re-run the Simple Setup again to make the change. This not only creates the sitebndl.zip file that the handle administrator uses, but also the config.

By default the VNC server will accept connections on TCP port 5901. Under the Linux environment, you can start multiple sessions at once, so the number will increase with each VNC session, i.e. 5901, 5902, 5903, etc...