Monitoring remote machines

  • Thread starter Thread starter laurent.herve23
  • Start date Start date
L

laurent.herve23

How do you monitor your remote servers, in order to
prevent them from crashing or being away from
the net because of bad IP, etc.
I wanted to connect to my vnc server and i see (from dyndns.org)
that the machine is reported to have 192.168.1.2, since 3 days.
I can't figure out what happens there :)

laurent
 
192.168.1.2 is a local ip address. How are you updating your dyndns.org A
record? Is the vnc server doing it via some software or do you have a router
which is taking care of this (many routers have this function built in to
their firmware).
It should be updated for its external ip address if you want it to be
accessable from the internet.

Ben
 
Thanks for the replys ! in fact the router "nows" everything
in order to make the update (account +password), but usually
the update should happen each 4 hours throught the dns
client from dyndns. For some reason the router's machine name
was taken to update the account, and that was a bad idea.
Many things can happen : the machine can hang during start
process or stop process, the machine can encounter a strom
breakdown, etc (need a converter) , the ISP's name servers can
be down...the town can burn....

lh
 
Can you explain exactly how to configure and to use the combination VNC and
no-ip service? I've both, but I don't know how I can use them.
Thank you.
Giovanni
 
1) you register for a no ip account and you get an address
2) you download and install the no-ip application on windows
that will allow for your ip adress to be automatically translated into your
new
address like giorel.no-ip.net
3) you open your firewall to see if its working
4) in vnc now all you have to do is type the new address instead of your ip
in order to connect
 
Back
Top