NxFilter not working for some hosts

Imran Haider

unread,

Sep 22, 2015, 11:53:03 AM9/22/15

to NxFilter

I'm using v2.8.7 and been using this since the day it was released but this problem started only today, the DNS resolution isn't working on some particular hosts but for others it's working fine. The login and logout URLs don't work, I can ping the NxF server from these hosts on which it's not working. I'm really lost here, can someone please help out?

I upgraded from v2.8.5 to v2.8.7.

PS: Resolution works on these hosts as soon as I replace the Nxf IP with our internal DNS IP.

dns_err_nxf.png

Imran Haider

unread,

Sep 22, 2015, 1:40:20 PM9/22/15

to NxFilter

After some further diagnosis, I can see the logs for the PCs but the problem seems to be that they aren't being redirected to the login URL as I could see a block page when I disabled authentication.

Jinhee

unread,

Sep 22, 2015, 8:37:27 PM9/22/15

to NxFilter

So your host think it's not existing. Did you try nxlookup on your host?

nslookup login.example.com

Imran Haider

unread,

Sep 22, 2015, 11:39:49 PM9/22/15

to NxFilter

Hi Jinhee,

So far I've tried, rebooting, flushdns, ip release/renew, nslookup and manually accessing the login URL using the IP of the Nx server and nothing seems to work. Now I'm going to try and change the IP of one of the affected hosts and see if it works. According to you, the host doesn't exist for the Nx server but it happened with so many nodes.

Nx Possible Fix.JPG

Imran Haider

unread,

Sep 22, 2015, 11:41:35 PM9/22/15

to NxFilter

One more thing, the Nx server seems to be entertaining new requests just fine.

Jinhee

unread,

Sep 23, 2015, 1:02:20 AM9/23/15

to NxFilter

What's your login domain then? Your hosts might be resolving it from somewhere other than NxFilter.

Imran Haider

unread,

Sep 23, 2015, 2:52:58 AM9/23/15

to NxFilter

It started working now, just like it stopped working without any reason last night. I do have a solution now, in case I face this issue in future, change the host's primary DNS to internal DNS server and then call the login URL by IP and authenticate and then revert back to Nxf as primary DNS. I can't test it right now but will do next time I face the same issue. Oh and nslookup confirmed last night that it was being resolved by Nxf not some other DNS server.

Imran Haider

unread,

Sep 23, 2015, 8:53:15 AM9/23/15

to NxFilter

Completely unrelated but I'm trying to configure a cluster and the slave server is throwing this error:

NodeTalkie.open: java.net.NoRouteToHostException: No route to host

Both slave and master are on v2.8.7. I can telnet the master server ports(19002 & 19003) from the slave server, am I missing something?

Imran Haider

unread,

Sep 23, 2015, 11:33:26 AM9/23/15

to NxFilter

Again faced the same issue with few nodes on the network, changed primary DNS IP to internal DNS, authenticated from there by calling http://serverip/block,login.jsp and then switched back the primary DNS to Nxf and it worked! Not a proper fix but atleast it works.

Jinhee

unread,

Sep 23, 2015, 8:24:42 PM9/23/15

to NxFilter

Actually it's 19003 and 19004. NodeTalkie is for talking on clutering channel and it uses 19004.

Jinhee

unread,

Sep 23, 2015, 8:27:14 PM9/23/15

to NxFilter

I don't know what happened exactly on your system and your solution looks weird but as long as it works. Next time try to change your login-domain to something can't be existing. Like 'myloginxx30.test4789.local'. If you can.

Imran Haider

unread,

Sep 24, 2015, 11:21:56 AM9/24/15

to NxFilter

Thanks for the tip Jinhee, I'll keep that in mind next time the issue occurs. Meanwhile I'll see if I made a mistake configuring firewall rules on the master server.

Imran Haider

unread,

Sep 24, 2015, 11:35:09 AM9/24/15

to NxFilter

It worked Jinhee, thanks a lot! I didn't allow 19004 tcp on the firewall of the master server, guess I was being stupid at the time of configuration :|

Reply all

Reply to author

Forward