PDA

View Full Version here: : How to access IP power Switches over the net??


Paul Haese
23-12-2013, 04:07 PM
I have several ip power switches which can be accessed over the net. I can access them via my computers on site which I use Radmin or Team viewer to access.

However, I would prefer to access the IP power switch via the IP address. So I know I need to access the static ip I have and I need to allow port forwarding on the router. What is the correct syntax to connect to the IP power. For instance is it http:/Static IP:192.168.1.(actual assigned port) or is it something else.

My reasoning is that I want to shut down the computer and then wake that up via power up of the IP power switch which has its own webserver.

Not being a tech head, I understand some basic language, and how to setup most things but this has been bugging me for a while and I have not been successful so far.

malclocke
23-12-2013, 04:48 PM
http://192.168.1.234/ will probably do it, assuming where you say port you actual mean the last part of the ip address.

If the web server is listening on a different port to the default (80 for web) then the format is http://192.168.1.234:456/ where 456 is the custom TCP port number.

Hope that helps.

Paul Haese
23-12-2013, 05:25 PM
Thanks Malc, but that does not work either. It times out and gives the "this page cannot be displayed" message. Does the static IP with a password mean that I cannot open IP power remotely?

Also your assumptions were right. I did not want to display the last part of the ip address or my static ip either.

I have noted that the port forwarding will not allow the standard port of 80 to be used as it says this is in use already. Yet both IP units are using this standard port because I cannot get those to work with any other port setting in IP edit.

gary
23-12-2013, 05:34 PM
Hi Paul,

Season's Greetings

Your internal IP addresses definitely won't be of the form 192.168.1 as it is not a full
32 bits. Most likely you made a typo.

Your internal addresses will be most likely of the form 192.168.0.X
where X might be, for example 99.

1) Do you know the internal IP address of your power switch?

2) Has your service provider provided you with a fixed IP address for your
connection or does it change every time you connected your router to the ISP?

Typically in the Port Mapping dialog for the router you are going to add a rule to
provide HTTP on External Port 80 to your power switch IP address, for example
192.168.0.99, on its Internal Port 80. That will then expose the web server on
the switch to the outside world.

Best Regards

Gary Kopff
02 9457 9049

gary
23-12-2013, 05:40 PM
Hi Paul,

Keep in mind that the address 192.168.0.0 through to 192.168.255.255 are reserved
special addresses on the Internet so that you, me, anyone can create their
own private intranets.

So you won't be giving anything away if you tell me what your intenal IP
addresses are. :)

You will also not be able to access your site externally from a http://192.168.0.1:80
request either.

You need to know the IP address your service provider provides you and use that
address.

Best Regards

Gary

mithrandir
23-12-2013, 07:08 PM
Paul,
1. you have to know the IP address your home network is known as on the internet. If it isn't static you need to set up one of the dynamic DNS providers to automatically map the IP to a name you know or you'll never know what the IP is.
2. you have to configure your router to forward traffic sent to a specified port on the internet side to whichever port the IP switch is listening.

eg Suppose your external IP was 241.202.202.202, (that looks valid but isn't) your internal network was 192.168.0.0/24 and the IP switch was 192.168.0.66 listening to port 80.

Pick an unused port number on the router - say 17000. Numbers between 16384 and 32767 are good choices. You configure the router to forward internet traffic sent to that port to 192.168.0.66 port 80.

Exactly how you do that depends on what brand and model of router you have.

From the internet you then http://241.202.202.202:17000 (http://202.202.202.202:17000)

Paul Haese
23-12-2013, 09:09 PM
Ok thanks guys,

So just to be clear. I have a static ip and yes i know what that address is.

Andrew a little lost with the port forwarding. I have a tp link router and it is called port triggering. I can set that port in the triggering. Though not sure how the ip switch allows another port. I would like some more explanation on that thanks.

Paul Haese
23-12-2013, 09:20 PM
I think I have got it going. Thanks guys.

gary
23-12-2013, 09:31 PM
Very good Paul.

I was just writing a post to suggest to you to look at the "Virtual Server" feature of
your brand of router.

In it you can specify the IP address of the power switch, the Service Port (typically
port 80), the Internal Port (typically port 80 as well) and the Protocol (set TCP).

This may well be what you have ended up doing yourself.

Best regards

Gary

Paul Haese
23-12-2013, 09:46 PM
Thanks Gary, yes worked out from the posts that I had to make one external of say 21100 and use the internal port as the same default and then the relevant IP address of the unit itself. All so clear now. See it just takes the help of others to see it clearly. Thanks all.

Now to get the computer to remain on via bios. I know there is a setting somewhere in the bios. Once that is sorted I can remotely boot the computers. Like I said I have them running continuously at present and use the internal IP addresses for the IP switches to open the browser to start the various items. Now I can do that without having the computer up and running at the other end.

gary
23-12-2013, 09:54 PM
Hi Paul,

Perhaps you are looking for the "Wake On LAN" setting that is in some BIOS's?

Otherwise later versions of Windows such as Vista and Windows 7 have the
Control Panel -> Power Options dialog where you can specify that the computer is
never to sleep.

Best regards

Gary

mithrandir
23-12-2013, 10:16 PM
"Wake on LAN" requires some device to send a WOL packet to the PC. Maybe the switch or router can do that.

The BIOS probably has a "Resume on power restoration" setting which would turn it back on, but Windows (and most other operating systems) do not play well with powering off without shutting down.

The best solution I can think of would be plug a UPS into the IP switch, the PC into a battery backed port, and connect the UPS alarm cable to the PC. When the switch turns off the power the UPS tells the PC the mains power is gone. You program the PC to shut down and the UPS gives it time to do that. It only takes a small UPS.

Then after the IP switch turns the power back on you send a WOL packet to the PC to turn it back on.

Paul Haese
23-12-2013, 10:36 PM
What about if I shut down the computer and then have the bios set to always on. Once the operating system shuts down the bios will try to reboot at which I can shut off the power. When I restore the power it should reboot?? Maybe?

AstroJunk
23-12-2013, 11:37 PM
Reading this thread is causing me angst just remembering my own pain and suffering trying to get the router/pc/switch combo to work reliably.

I had no end of pain with WoL and gave up eventually, but in the process discovered that bios setting that caused the pc to re-boot after power failure rather than just sit there. With this setting, you can shut down the machine and switch it off using the ip-power and it will automatically start when you switch the power back on. Works a treat, and without ever visiting the observatory.

Fingers crossed your bios supports it!

Paul Haese
24-12-2013, 12:24 AM
Fortunately I already have UPS on both dome and roll off roof observatories. I am just trying to relieve the need to have computers powering up full time. The power and wear on the power supplies of the computers being the primary considerations. I checked one systems manual tonight and that supports power on for power loss. So I can test this over the Christmas break to see if it will work. This will be the final redundancy measure in place. I can then choose to have the computers off or on at my will. Redundancy becomes really important for remote systems. This one had me stumped but now it seems I will have this sorted, thanks to you guys.