Hello there.
We are testing NeoRouter in different contexts.
1) local computer, local user.
This case is trivial. No NeoRouter is needed to connect a <Windows user logged on locally to a Windows computer> to other computers on the same LAN.
2) remote computer, local user.
This is the typical case.
As soon as a Windows user logs on locally to a remote Windows computer, NeoRouter client starts automatically and build a VPN with all computers of the same NeoRouter domain with an active instance of NeoRouter.
A) local computer, Windows domain user
This case is trivial. No NeoRouter is needed to connect a <Windows user logged on to a Windows domain> to other computers on the same LAN.
B) remote computer, Windows domain user
We see here the risk of a vicious circle.
A remote Windows user willing to log on to a Windows domain must start NeoRouter to build the VPN, but the user can start NeoRouter if he/she has logged on remotely to a Windows domain.
The only solution I see (before the NeoRouter Connector is released) is to start NeoRouter on the remote computer *before* the log-on windows pops up.
This topic
Using NeoRouter with Active Directory did not help me.
Any help and suggestions would be appreciated.