Multiple uploads

Hello,
It would be nice if Nexus Control identifies if you're trying to
connect to a PC which is within LAN and connect locally instead
passing through internet.

Eg,

Server -> Nexus Controls
MyPCDomain -> Nexus Host

The Server nexus controls should use the LAN IP of the Nexus Host
(eg, 192.168.1.123) instead of the External Internet IP to
control the remote session.

Charalampos Michael wrote:

> Hello,
> It would be nice if Nexus Control identifies if you're trying to
> connect to a PC which is within LAN and connect locally instead
> passing through internet.

Any such "recognition" is in reality nothing else than a guess. How does the
system know whether a "local network" really is faster or the better solution?

The correct solution to that problem is to setup your network with the rigth
metrics. Once that is done the TCP layer will take care of any such
"intelligent routing".

http://support.microsoft.com/kb/299540

Charalampos Michael wrote:

> Hello,
> It would be nice if Nexus Control identifies if you're trying to
> connect to a PC which is within LAN and connect locally instead
> passing through internet.
>
> Eg,
>
> Server -> Nexus Controls
> MyPCDomain -> Nexus Host
>
> The Server nexus controls should use the LAN IP of the Nexus Host
> (eg, 192.168.1.123) instead of the External Internet IP to
> control the remote session.

Just realized that your question could be interpreted in a different way. If
you mean that there are two gateways (one on the local network and one on the
internet). I would say that the above suggested multi gateway solution with
automatic fallback would be a feasible solution. This way your local gateway
would be the first in the list and the internet one would only be chosen if
the local one is unreachable/down.

Hi,

Is there a possibility to upload file from several hosts at the same
time? When I strat to upload in a second FileTransfer window, than in
the first one, the upload process waits until the second is finished. I
don't have this problem with downloads.


--
ornotp

Is it working by you in the same way? I'm developing a software which is
able to upgrade other software by ours customers and it would be very
usefull to upload files to several hosts at the same time.

Thank you in advance


--
ornotp

ornotp wrote:

>
> Is it working by you in the same way? I'm developing a software which is
> able to upgrade other software by ours customers and it would be very
> usefull to upload files to several hosts at the same time.
>
> Thank you in advance

Hi. Sorry, we've overlooked your question. Will investigate ...

Dear Hannes,

>> The Server nexus controls should use the LAN IP of the Nexus Host
>> (eg, 192.168.1.123) instead of the External Internet IP to
>> control the remote session.
>
> Just realized that your question could be interpreted in a different way. If
> you mean that there are two gateways (one on the local network and one on the
> internet). I would say that the above suggested multi gateway solution with
> automatic fallback would be a feasible solution. This way your local gateway
> would be the first in the list and the internet one would only be chosen if
> the local one is unreachable/down.

I like that idea, please add it to mantis

Dear Hannes,

>> The Server nexus controls should use the LAN IP of the Nexus Host
>> (eg, 192.168.1.123) instead of the External Internet IP to
>> control the remote session.
>
> Just realized that your question could be interpreted in a different way. If
> you mean that there are two gateways (one on the local network and one on the
> internet). I would say that the above suggested multi gateway solution with
> automatic fallback would be a feasible solution. This way your local gateway
> would be the first in the list and the internet one would only be chosen if
> the local one is unreachable/down.

I like that idea, please add it to mantis

Dear Hannes,

>> Hello,
>> It would be nice if Nexus Control identifies if you're trying to
>> connect to a PC which is within LAN and connect locally instead
>> passing through internet.
>
> Any such "recognition" is in reality nothing else than a guess. How does the
> system know whether a "local network" really is faster or the better solution?
>
> The correct solution to that problem is to setup your network with the rigth
> metrics. Once that is done the TCP layer will take care of any such
> "intelligent routing".
>
> http://support.microsoft.com/kb/299540

Well another Example ...

(Server outside the LAN)
Gateway: 88.88.88.88 (Internet IP)

(Below both on the same LAN)
Host: 192.168.1.10 (Internet IP: 99.99.99.99)
Remote: 192.168.1.2 (Internet IP: 99.99.99.99)

Currently the route is:
99.99.99.99(Remote) -> 88.88.88.88 (Gateway) -> 99.99.99.99 (Host)

My idea is to make the route:
99.99.99.99(Remote) -> 88.88.88.88 (Gateway) -> 192.168.1.10 (Host)

Thank you

Dear Hannes,

>> Hello,
>> It would be nice if Nexus Control identifies if you're trying to
>> connect to a PC which is within LAN and connect locally instead
>> passing through internet.
>
> Any such "recognition" is in reality nothing else than a guess. How does the
> system know whether a "local network" really is faster or the better solution?
>
> The correct solution to that problem is to setup your network with the rigth
> metrics. Once that is done the TCP layer will take care of any such
> "intelligent routing".
>
> http://support.microsoft.com/kb/299540

Well another Example ...

(Server outside the LAN)
Gateway: 88.88.88.88 (Internet IP)

(Below both on the same LAN)
Host: 192.168.1.10 (Internet IP: 99.99.99.99)
Remote: 192.168.1.2 (Internet IP: 99.99.99.99)

Currently the route is:
99.99.99.99(Remote) -> 88.88.88.88 (Gateway) -> 99.99.99.99 (Host)

My idea is to make the route:
99.99.99.99(Remote) -> 88.88.88.88 (Gateway) -> 192.168.1.10 (Host)

Thank you