RE: Can't reach HMC console remotely

We were on firmware level SF240_338 and upgraded to SF240_258.
We were on v5r1 of the HMC Console and upgraded to v6r1.3 and there were
several corrective services fixes as well.

There was a notification that the Web-based System Manager Remote Client on
my PC needed to be uninstalled before downloading and installing the new one
from the server. I did that and then connected to the server from the
network (i.e. NOT from the VPN). The new client was downloaded and
installed and worked perfectly from my PC, as long as I was directly on the
network. I then went back to me remote office and tried the WBSM after
connecting to the network via VPN. The result of that was described below.


Best Regards,

Thomas Garvey
Unbeaten Path International
Office: 630-462-3991
web: www.unpath.com



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Essinger
Sent: Monday, March 09, 2009 6:09 PM
To: Midrange Systems Technical Discussion
Subject: Re: Can't reach HMC console remotely

Thomas.

What version of the HMC operating system are you at or did you upgrade to?
Version 7 uses a web browser interface to control the HMC. I use it over a
local network, and over our VPN all the time.

Jim

On Mon, Mar 9, 2009 at 4:49 PM, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:

Anyone else encounter this, or have a suggestion?

We recently upgraded our server firmware and HMC Console software.
Before this upgrade we were able to use the Web-based System Manager
Remote Client over our VPN to manage the HMC remotely. Now we can't.
I get a dialog box saying...

Cannot complete connection to hostname xxx.xxxxxx.com

Possible problems are:
1. Host xxx.xxxxxx.com is not a valid hostname
2. Host xxx.xxxxxx.com is not currently operating or is not connected
to
the network
3. Host xxx.xxxxxx.com is not running an operating system with a
version
of Web-based System Manager that is compatible with your client
version of Web-based System Manager
4. The time to connect could have exceeded the time limit set in the
websm.cfg file (remote_timeout)
5. The inetd subsystem on host xxx.xxxxxx.com may not have been
initialized on the 9090 port to start the WServer

Additional information might be in the file
/var/websm/data/wserver.log on host xxx.xxxxxx.com

I was able to download and install the new version of Web-based System
Manager when my PC was actually physically on the network, rather than
connecting through the VPN. So, I believe that eliminates possible
problems
1 through 3. I wouldn't know how to set a time limit as noted in #4
and have no idea what #5 is referring to. Furthermore, I know nothing
of the
(AIX?) operating system on the HMC Console and so don't know how to
look at the log file mentioned.

Nothing about our network has changed, nor our VPN connections. Any

ideas?

Thanks in advance,

Thomas Garvey

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.