topic Re: Secure Web Console - cannot connect in Operating System - HP-UX

Secure Web Console - cannot connect

Simon R Wootton — Thu, 19 Apr 2001 07:35:25 GMT

Following message posted 18.4.01, I've managed to connect the SWC to the LAN and I can ping it from unix on 192.0.0.192 which is the default IP address. However, I cannot ping it from DOS on my PC or access the SWC via my browser - any suggestions please?
Thanks
Simon

Re: Secure Web Console - cannot connect

Marc Dijkstra — Thu, 19 Apr 2001 08:12:10 GMT

have you added a route on your PC to connect to the SWC via the 192.0.0.0 network? You need to do this on the PC before you can connect via a browser to change the default settings.

route add 192.0.0.192 mask 255.255.255.0

MND

Re: Secure Web Console - cannot connect

Simon R Wootton — Thu, 19 Apr 2001 09:02:02 GMT

Still no joy, can you help me with the command ?

Details :

SWC ip 192.0.0.192
Unix host 172.21.1.1
My PC 172.21.10.19
Subnet 255.255.0.0

Re: Secure Web Console - cannot connect

Vincenzo Restuccia — Thu, 19 Apr 2001 09:03:05 GMT

With cross cable of lan connect web console and your PC,change IP of it with 192.0.0.193 subnet 255.255.255.0. It is ok!

Re: Secure Web Console - cannot connect

Marc Dijkstra — Thu, 19 Apr 2001 09:09:10 GMT

Vincenzo is correct, one can use a crossed cable and change the ip address of the PC.

You say you can get to the SWC from the UX box? Do you have a X-emulator running that you can get Netscape up on the L?

Try:
route add 192.0.0.0 mask 255.255.0.0 172.10.21.19

This will add a route via your PC to the subnet, however I think that the class B will interfere as the SWC is class C, if that don't work, change the PC's subnet to 255.255.255.0 and try the route again using that mask.

MND

Re: Secure Web Console - cannot connect

Ravi_8 — Thu, 19 Apr 2001 10:37:55 GMT

Hi,
while adding the route to ur pc don't use the netmask. just issue the command from DOS prompt : route add 192.0.0.192 pc's Ip.
If u r using 2 or more web console u need to change the ip of the current web console to 192.0.0.x since the new web console u r connecting will be having default ip 192.0.0.192 which clashes with the current webconsole.In the browser don't use any proxy settings to access the webconsole.

good luk