I have a problem when I install WebSphere Application Server 6.0(WAS) and We
bSphere Portal Server 6.0(Portal):

I installed WAS and Portal on a linux server and run it. We can access the a
dmin console on that local server by running Browser:

http://servername:9060/ibm/console
http://servername:10038/wps/myportal


The problem is we try to access the admin consoles of WAS and Portal from a 
  another *remote* machine(Not local server) by open an browser by the same 
link:

http://servername:9060/ibm/console
http://servername:10038/wps/myportal

The admin console can not be accessed.

Anybody have any hints for that? We need configure WAS and Portal somewhere 
to let admin console can be remotely accessed?

Sincerely
Zhiyi Li
Email: zli04@vbi.vt.edu

[ Post a follow-up to this message ]

check out whether the ip address of  the machine(where u istalled WAS) is pi
nging on the machine(remote machine where u want to run the admin console)

ex: ping 11.48.533.33

if it is responding then u can access the admin console.

if it is not responding i think u should do the tunneling on the putty inord
er to access the admin console remotely.i m not sure about this.lets try fir
st to ping the ipaddress.

..mahendra

[ Post a follow-up to this message ]

lzy12001@gmail.com wrote:

>...
>       The problem is we try to access the admin consoles of WAS and Portal
 from a   another *remote* machine(Not local server) by open an browser by t
he same link:
>
>           http://servername:9060/ibm/console
>           http://servername:10038/wps/myportal
>
> The admin console can not be accessed.
>
> Anybody have any hints for that? We need configure WAS and Portal somewhere to let
 admin console can be remotely accessed?

It would be really good if you provide more information in addition to the s
tatement "The admin
console can not be accessed." For example - what do you see in your browser 
when you try to access
remote websphere?

[ Post a follow-up to this message ]

Try if you can telnet from your workstation to port 9060 on the server. If N
OT, there must be a firewall blocking that port; talk to your network guys. 
There is an alternative if it is an issue with firewall - you can tunnel in 
port 9060, you should be ab
le to login then.

[ Post a follow-up to this message ]