Proxy Servers & Firewalls: Reaching the Internet

ShipRush uses the internet during these operations:

a) Initial installation, when you configure your shipper account

b) Each time you press Ship, estimate a rate, or get time in transit

ShipRush communicates with the shipping carrier using SSL on port 443 (the standard SSL port).

ShipRush does not require you to open ports for inbound access. ShipRush connects outbound, just like a web browser. Most sites can simply install and use ShipRush without any PC or network reconfiguration. However, certain firewalls, proxy servers, and security software may block ShipRush, so awareness is in order.

Network Firewalls:

"Transparent"  A Transparent Firewall requires no configuration on the workstation. For example, you can set up a new PC on the network, and no configuration is required in order to browse the internet. Examples of Transparent Firewalls include NAT type devices, Netscreen, Linux IP Masquerade, and many other systems. ShipRush Basic Edition is compatible with Transparent firewalls. ShipRush Pro Edition is compatible with Transparent Firewalls.

"Personal"  A Personal Firewall is a software utility installed on your PC to protect it from internet attacks and rogue software (such as spyware). Examples of Personal Firewalls include: Norton, ZoneAlarm, BlackIce Defender, and similar products. ShipRush is typically compatible with such systems, but in some cases configuration is necessary.

"Configured"  A Configured Firewall requires one of the below:

• Configuration on the client PC

• The PC uses a central script for 'automatic' configuration

• Special firewall client software must be installed on the client PC.

The rule of thumb is: If the browser requires proxy configuration in order to access the internet, the firewall is a Configured Firewall. You can check for proxy configuration in Internet Explorer with these steps:

1. Select Tools | Internet Options

2. Select Connections

3. Select LAN Settings

If any of the checkboxes are checked, a Configured Proxy is in use.

A Configured Firewall may require extra steps to set up ShipRush.  

First try to install and use ShipRush. Only use these steps if ShipRush fails to function.

Steps:

• Get the firewall name, address, user name, password, and other required information from the network administrator.

• After installing ShipRush, do not start the ShipRush setup wizard (cancel it when it starts).

• Open the Start menu and navigate to the ShipRush program group.

• Select "Internet Connection Utility"

• Try the Windows and Compatible modes. Save the settings and retry ShipRush

• Note: ShipRush must be exited and restarted to engage the new settings.

• If the problem persists, open the Internet Connection Utility and select Native

• Set the settings appropriately

• Restart ShipRush and try it

Software Client Based Firewalls

Many personal firewalls, and some network firewalls, require that you name the specific pieces of software permitted to communicate on the internet.  In such situations, configure the firewall to allow the following access:

• ShipRushServer.exe  Outbound access: port 443 (SSL) and ports 20 & 21 (FTP)

• ShipRushServer.exe  Inbound access: port 3841 and 1124

• ShipRush5.exe  Outbound access: port 443 (SSL) and ports 20 & 21 (FTP)

A potential issue is that the ShipRush Server does the communication, and this software runs as an NT Service.  The firewall in use must allow NT Services to communicate with the internet.  A possible problem area is firewall clients that require a username every time the internet is accessed.  Since communication is done by an NT Service, the firewall login screen may not be displayed.

If this applies to your site, please contact your firewall vendor to discuss how to allow NT Services to communicate through the firewall.

Personal Firewall Troubleshooting

If you use a Personal Firewall and are having internet communication issues, start out by disabling the firewall temporarily to allow initial configuration of ShipRush.  If this is successful, contact the firewall maker technical support to figure out how to allow coexistence of the firewall with ShipRush.