This depends upon how your firewall / NAT server is configured. Please ask your network administrator if your firewall (or NAT server) is configured to allow PING and TRACERT to work (which use ICMP ECHO, ECHO REPLY, and TTL EXPIRED packets). You can test this yourself by running these programs on your computer (For example, try "tracert www.visualware.com"). If these programs work, VisualRoute should work just fine on your computer.

VisualRoute uses ICMP which is not a protocol that can be proxied so VisualRoute will coexist and not interfere with a proxy. In order for VisualRoute to work through a firewall VisualRoute will require that ICMP the following outbound and corresponding inbound message types to be enabled. Another option is to configure a VisualRoute Server which is specifically designed to operate in a DMZ environment outside of your company firewall.

Yes. You must ensure however, that port 3306 is available in order to permit connection to your remote mySQL server. Network Address Translation boxes are not a problem. Non-translating proxies might be however - contact your systems administrator if you are operating under a proxy to ensure that packets will be properly routed.

Yes, the InfoGate 3020 can work behind a firewall or NAT, by opening the following ports: TCP/IP: 8481 UDP: 6024, 6026, 6028 & 6030 UDP: 1588 for InnoSphere

The File Transfer Protocol and firewalls do not co-exist well. Luckily, firewalls, NAT devices, load-balancers, and proxies are handling FTP and its quirks better each year. Please see our article titled "The FTP and Your Firewall / NAT / Load-Balancing Router" for details on the problems and what you can do about them.

Absolutely. Our specialists will provide you with the required proprietary firewall port information. In most situations, firewall changes are NOT required.

For most routers, yes. The service is designed to work behind a NAT router and you should be able to just plug in and go, assuming your router is handling DHCP services. In addition, there is an excellent network connection troubleshooter built into the XBL front-end. You can configure your Xbox with a static IP if required, you can manually set various network settings, and you can even have the Xbox spoof a certain MAC address if required by your ISP.

It should work with any type of firewall including Symmetric NAT. Symmetric NAT is performed only by advanced enterprise routers, in that case NATPass™ will recognize this scenario and will make the call succeed by signaling and doing RTP bridging. It is all transparent for the user and there is no need to reconfigure anything.

You can find classification of NAT in RFC 3489 – STUN http://www.faqs.org/rfcs/rfc3489.html. It should not mater what type of firewall you have.

Yes. WuWu is completely Firewall/NAT compatible! For additional information on this topic, please read the WuWu Firewall / NAT how-to.

The quick summary: You need to forward your ports if you have NAT in order to get the fastest speeds. This is probably the most common thing that people fail to do when using BitTorrent. Read on for more details of what all this entails, and if it's something that you need to do. Prior to version 3.2, BitTorrent by default uses ports in the range of 6881-6889. As of 3.2 and later, the range has been extended to 6881-6999. (These are all TCP ports, BitTorrent does not use UDP.

eCare uses the HTTP port (port 80) for initial communications and services between the Support Agent and the Client. The SSL port (port 443) is used for the View Remote User and Control Remote User features. Because of this, firewalls and/or proxies do not have to be reconfigured to enable online support, thus maintaining the safety of the corporate network.

If you are running through separate proxies for each service, you shouldn't need to do anything. If you are working through sockd, you will need to "socksify" your application. Details for doing this can be found in the package itself, which is available at:

I'm doing firewall/network configuration and need to know how the GIDB™ Client communicates with the data servers. All of the traffic from GIDB™ Client occurs over port 80 (with the exception of key requests that occur over port 443) and should look the same as regular web browser traffic to your firewall.

You can't have the DHCP server listening for requests directly from the users. This is because the relay agent is used to distribute the request to the right server, and in this case the server would answer to the user anyway. The Right Way to do it is to have the DHCP server in another machine located in the upstream network. Blocking requests from the users by filtering out any IP except for the relay agent in the firewall doesn't work either.

Generally the answer to this is no. However, if your NAT Server allows you to perform IP Forwarding, and your network router can receive forward requests over specific ports, then you should be able to use the iSeries PC-Engine suite of tools. Check with your network technician to find out if this capability is available on your network.

Yes, but you will get better performance if other peers can connect to you. By default, BitTorrent listens on port 6881, trying incrementially higher ports if it's unable to bind. It gives up after 6889 (the port range is configurable.) It's up to you to figure out how to poke a hole in your firewall/NAT.

Incoming traffic is usually accomplished by simple port-forwarding, with certain types (fragmented, for example) of traffic filtered out. Although ports can be forwarded to other internal IP addresses, this isn't generally referred to as NAT, which includes port-remapping as well as forwarding.