This seems more like a permissions issue than port.  Are you sure your credentials have proper permissions on the remote system?

Rob

Yes, the credentials entered have admin access on the server.  Does this copy to admin shares over SMB?  Or how do the packages get moved to the remote server?

Hi,

Assuming you are using windows targets, you can try the following:

To enable the successful functioning of remote Server Administrator CLI and

 software updates/deploy features, ensure the following (applicable to Microsoft®

 Windows® only)

 The managed system and the management station must be on the same domain or there

 should be a trust relationship between the two domains.

 If you have a Windows Firewall configured on the management station or the managed

 system, make the following configuration changes to enable remote Server

 Administrator CLI and software updates to work successfully.

 Management Station:

 1. Open TCP port 135.

 2. Add the application "omremote.exe" (located in Essentials\bin)

    to the Firewall exception list.

 Managed System:

 If you have the Windows firewall configured, enable remote administration by

 running the following command in the command prompt:

 "netsh firewall set service RemoteAdmin"

Regards

Abhijit

There is a ports and protocols table in OME user guide and online help under "Managing Security Settings" section which lists all the ports used by OME to communicate. You can take a look at that and see if any of those ports are blocked.

We are using a Cisco firewall not the windows firewall.  What ports is omremote.exe trying to use in addition to 135?