Adam,
You can use Dynamic DNS. Essentially, you would install a small
utility on the machine which acquires its IP dynamically. You would
register this machine with for example, dyndns.org. This utility
would then update the DNS servers of dyndns.og everytime the IP
address changes. You could then simply access the machine using its
DNS name.
Using dyndns.org has a cost, however, you could just as easily write a
script to say email you or update a webpage when the IP changes.
-V
On Tue, 15 Mar 2005 09:46:17 +0800, hartmann <hartmann_at_thestar.com.my> wrote:
> Hi,
>
> Is there any software or any way that we could have a remote control over
> client(s)
> Which does not have fixed IP?
> I'm one of my company system administrators, and currently we need to
> support remote site clients.
> But, the difficult part is that the client have a dynamic IP.
> Thus, is there any tools to help?
> Even it needs to be launched from the client side.
>
> Thanks.
>
> Adam
>
> /******************************************************************\
> This message and any attachment(s) are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or e-mail the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the content to any other person.
>
> Any opinion, view and/or other information in this message and/or any attachment(s) hereto which do not relate to the official business of Star Publications (Malaysia) Bhd shall not be deemed given nor endorsed by Star Publications (Malaysia) Bhd. Our company is not responsible for any activity that might be considered to be an illegal and/or improper use of email.
>
> E-mail transmissions cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, delayed, incomplete or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message or for any virus damage which may arise as a result of this e-mail transmission.
> /******************************************************************\
>
Received on Mar 17 2005
Intro
