Why isn't Appliance Manager discovering any Appliances?

When Appliance Manager is launched, it uses a "broadcast" (on UDP port 2346) to discover iPrism (and ePrism) units. If you are not seeing any appliances, it may be that:

  1. You have not installed Appliance Manager in the same subnet as iPrism, and therefore the broadcast packets are not reaching iPrism.

  2. You have launched a 2nd Appliance Manager (you should run one Appliance Manager only). Use Alt-Tab to see application icons, looking for the Java coffee cup which may be a hidden Appliance Manager window.

  3. Windows XP/SP2 is blocking broadcasts because of its built-in firewall software, called Internet Connection Firewall (ICF). You have two options, you can:

or ...

  1. You have a 3rd party VPN client software installed on the workstation. Appliance Manager may fail to detect any appliances. These 3rd party applications sometimes either block or modify the original requests from the Appliance Manager program. You may want to try terminating the VPN connection or software, and use ipconfig/all to verify that only your machines normal LAN IP addresses are in use, then reboot your machine and re-launch Appliance Manager. It may be necessary to un-install the VPN software in order to see if the VPN software is interfering with Appliance Manager. Another approach would be to install Appliance Manager on another machine that doesn't have VPN connections or software (as suggested in #5 below) and note the result.

  2. Java execution is impeded for some reason. Try the following:

Turn Windows Firewall (ICF) "Off"

If you are using the "Classic Start Menu", go to Start > Settings > Control Panel > Windows Firewall, select "Off", Click Ok.

If you are using the default XP Start Menu, go to Start > Control Panel > Windows Firewall, select "Off", Click Ok.

Configure Windows Firewall (ICF) to allow Appliance Manager

Creating Windows Firewall (ICF) Exceptions via the "Windows Security Alert" Message

When you install Appliance Manager on an Windows XP/SP2 workstation, if ICF is "On" (the default), you may see the "No appliances were found" message in Appliance Manager, with a "Windows Security Alert" (below) displayed on top of the Appliance Manager window.

 

Appliance Manager is a Java application, as indicated by the program name "javaw" above. If you click Unblock, ICF will create an "exception" for the "javaw" program, allowing Appliance Manager to run un-impeded in the future. After you click Unblock the Alert will go away, and an exception will have been created for the Appliance Manager.

When you click the Refresh List icon (highlighted above) this will cause the Appliance Manager to re-broadcast for appliances and your appliance(s) should now appear in the Appliance Manager window.

If you do NOT get the "Windows Security Alert", but you DO get "No appliances were found", continue reading and set up an "exception" for the Appliance Manager javaw.exe program as explained in the "Checking/Creating ICF Exceptions" section below.

Manually Checking or Creating Windows Firewall (ICF) Exceptions

Below is more information on exactly what happened when you clicked Unblock (above), and how you can manually use ICF to block/unblock specific applications from the Exceptions tab.

If you go to:

Start > Settings > Control Panel > Windows Firewall (Classic Start Menu) or&ldots;

Start > Control Panel > Windows Firewall (default Start Menu) &ldots;

you can click on the Exceptions tab to look for "javaw" (see below). This is the exception that was setup when you clicked Unblock in the "Windows Security Alert" dialogue.

This exception can be manually setup in the event that you did not get a "Windows Security Alert".

Looking above, you can see that Add Program makes it easy to add exceptions for known installed programs. For unknown programs you might have to Browse to the program location to add it as an exception (browse is part of Add Program).

The Edit button allowed viewing the path below. "javaw.exe" is clearly part of the Appliance Manager installation. We show this path here so that it is clear where the javaw executable resides.

If you need to manually create an exception for javaw.exe, click Add Program, then Browse to the javaw.exe file and add it as an exception.