[FreeNX-kNX] Workstation without Fixed IP as FreeNX server

[Jesse Byler]

The dynamic DNS setup works best for a globally-accessible IP address  
- for example, a home cable or DSL connection which gets its IP from  
the provider via DHCP.

In the scenario you describe, with an NX server behind a corporate  
firewall, dynamic DNS could still help you if you only want to access  
the machine from other machines within the corporate network.  But if  
you want it to be externally accessible, like you said, you'll need  
the firewall to open a port and forward its traffic to the internal  
server machine, and to do that it has to have some way of knowing  
what the changing IP address of that internal machine is.  Hopefully  
if you have access to change the firewall settings and set up the  
port forward you also have access to the DHCP server settings and you  
can set up a static IP for your server - then you don't have to worry  
about updating the firewall settings each time the server's IP changes.

If you can VPN into your company network, then your client machine  
can use the VPN to get inside the firewall and then use dynamic DNS  
to find the NX server's changing private IP.

SOCKS is really meant for outgoing connections, not incoming.  I  
don't think it will help you.

-Jesse

On Jul 14, 2006, at 11:32 AM, LROUFAIL at nc.rr.com wrote:

> This would require that the firewall route traffice to that server
> through that port, right?  I am thinking about a corporate scenario
> where the workstation may not be directly accessible through a  
> firewall.
>
> Thanks,
>
> Lawrence
>
> ----- Original Message -----
> From: Jesse Byler <lists.freenx at web19.eml.cc>
> Date: Friday, July 14, 2006 6:35 am
> Subject: Re: [FreeNX-kNX] Workstation without Fixed IP as FreeNX  
> server
> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
>
>> Depending on how your network is set up, the easiest thing to do
>> might be to use one of the dynamic DNS providers such as
>> dyndns.com.
>> NX client machines connect to the NX server using a host name, and
>> the dynamic DNS provider maps that host name to whatever the
>> current
>> dynamically-assigned IP address of the NX server is each time the
>> host name is looked up.
>>
>> For this to work, the server needs to be running an update daemon
>> that keeps the dynamic DNS provider's record current.  The web site
>>
>> of your provider will give instructions for that, but there are
>> many
>> free tools available for this purpose.
>>
>> Disadvantage: it's probably not a good solution for a commercial or
>>
>> high-volume server, since there's always a time window after the
>> server's IP address changes but before the DNS record gets updated
>> during which clients will try to connect to the old address.  In
>> practice for a personal server used by a few people this isn't a
>> big
>> deal.
>>
>> On Jul 13, 2006, at 7:01 AM, LROUFAIL at nc.rr.com wrote:
>>
>>> This may have been discussed before.  I would like to have the
>>> capability of having a workstation without a static IP be
>> accessed
>>> as a
>>> freenx server.
>>>
>>> I don't know a lot about networking, but I was thinking I could
>> use
>>> some
>>> kind of proxy (maybe SOCKS or a VPN) to give the workstation a
>> static> external address.
>>>
>>> Is this possible with the nx software, or with an external
>> program
>>> on Linux?
>>>
>>> Thanks,
>>>
>>> Lawrence
>>> ________________________________________________________________
>>>      Were you helped on this list with your FreeNX problem?
>>>     Then please write up the solution in the FreeNX Wiki/FAQ:
>>>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>>>          Don't forget to check the NX Knowledge Base:
>>>                  http://www.nomachine.com/kb/
>>>
>>> ________________________________________________________________
>>>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>>       https://mail.kde.org/mailman/listinfo/freenx-knx
>>> ________________________________________________________________
>>
>> ________________________________________________________________
>>     Were you helped on this list with your FreeNX problem?
>>    Then please write up the solution in the FreeNX Wiki/FAQ:
>>  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>>         Don't forget to check the NX Knowledge Base:
>>                 http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>>       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>      https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________