IP Change Issue (Device)

70 views
Skip to first unread message

f.ha...@blue-shield.at

unread,
Apr 6, 2017, 7:59:25 AM4/6/17
to NxFilter
Dear support,

is there an solution, when the device changes the IP, for example, switch from LAN to WLAN?
The user has to logoff, logon, if not the nxfilter loginpage appears.
It doesn´t matte if it uses nxmapper/nxlogon.

Best regards,
Florian

Jinhee

unread,
Apr 6, 2017, 8:18:53 AM4/6/17
to NxFilter
You mean that you want to differentiate users behind a router? Or dynamic IP updater for an external IP address for your cloud service? We have NxRelay for differentiating users behind IP or mapping private IPs on NxCloud. If you are just talking about we have NxUpdate. Everything is on tutorial.

f.ha...@blue-shield.at

unread,
Apr 7, 2017, 1:57:18 AM4/7/17
to NxFilter
Good morning,

no, for example i have an laptop which is connected to LAN (nxfilter works via nxmapper or nxclient, doesn´t matter) an the laptop get connected to WLAN (no lan any more) i have the problem if i try to open an webpage,
the nxfilter loginscrren appears, until the user log off and on again, then it start working again!

The same problem is also when i have an public nxfilter an the laptop (with nxclient) get disconnected from one wlan and connected to an other (For exapmle from the WLAN to an mobile hotspot), the loginscreen appears (until the user log off/on)

So that means if an device is running an the ip changes, he has to log off/on that it works again

Are there any solutions?

Jinhee

unread,
Apr 7, 2017, 5:18:35 AM4/7/17
to nxfil...@googlegroups.com
The changed IP should be discovered by NxMapper but I don't think it would as your user already logged-in to your AD network so it doesn't make any event log or session on your DC. And I guess your NxLogon or NxClient sends NxFilter your LAN IP not WAN IP. So NxFilter doesn't know that your user is on a WAN IP. If the system always have 2 IPs then you could set 2 server-ip on NxClient's setup. One for NxFilter's LAN IP and the other one for NxFilter's WAN IP.

f.ha...@blue-shield.at

unread,
Apr 10, 2017, 10:03:57 AM4/10/17
to NxFilter
NO, the user disconet the LAN Interface and then connect the WLAN this don´t work, without, log off and on again

Jinhee

unread,
Apr 10, 2017, 9:26:58 PM4/10/17
to NxFilter
So is it like this?

NxFilter IP:192.168.0.100
Your client LAN IP: 192.168.0.200

And your NxLogon sends username to 192.168.0.100. And NxFilter detects its IP as 192.168.0.200.

But your client lost the LAN IP and gets a WAN IP something like '203.248.252.22'. Then how can your NxLogon contact 192.168.0.100 which is your NxFilter?

f.ha...@blue-shield.at

unread,
Apr 11, 2017, 3:31:09 AM4/11/17
to NxFilter
No,


NxFilter IP:192.168.0.100
Your client LAN IP: 192.168.0.200

And your NxLogon sends username to 192.168.0.100 (per NxMapper). And NxFilter detects its IP as 192.168.0.200.

Then my client lose the LAN IP and gets a WLAN IP for example '192.168.0.201'.

Jinhee

unread,
Apr 11, 2017, 4:50:33 AM4/11/17
to NxFilter
NxLogon contacts its server once in a minute. Means it updates its IP once in a minute. So it's natural. If you don't want to see that popup absolutely you may create default user to cover whole IP range. Create a user associating 192.168.0.1 ~ 192.168.0.255. Before NxLogon updates its IP your users will be appeared as the default user. Just assign some restricted policy to the default user.
Reply all
Reply to author
Forward
0 new messages