users not authenticating

[rating2]

In Brazilian forum I can't post on the topic anymore, my messages are automatic excluded https://groups.google.com/g/nxfilter.../c/L545b-ZS5L4

bat files of nxlogon are exlcuded from the shared folder, by antivirus I think. Copied again and reboot a computer, but the problem persist, can you help me with nxfilter.log? I didn't find anything that can help in debug log.

Thanks.

[support200]

If it's from your Login Script, you can't find anything in the log file. Try VxLogon or NxMapper. You can run both of them.

[rating2]

If it's from your Login Script, you can't find anything in the log file. Try VxLogon or NxMapper. You can run both of them.

Nice, installed both, now testing!

[rating2]

If it's from your Login Script, you can't find anything in the log file. Try VxLogon or NxMapper. You can run both of them.

Now users are authenticating again!!
But I don't know if is from nxmapper or vxlogon, but I think it doesn't matter! XD
Thanks.

[rating2]

After this, clients computers showing erros on comunicate to active directory, I need to change the DNS to active directory (172.20.20.4) server now? or keep on nxfilter (172.20.20.2)?
My DNS until now is nxfilter (172.20.20.2)

:'(

[support200]

Use Local DNS and Local Domain on 'DNS > Setup'. Add both your AD domain and reverse lookup domain into Local Domain.

[rating2]

Use Local DNS and Local Domain on 'DNS > Setup'. Add both your AD domain and reverse lookup domain into Local Domain.

"Add both your AD domain and reverse lookup domain into Local Domain."


I didn't understand this, on AD I need to do something yet?

[support200]

It's done by your AD importation setup automatically. If it doesn't work then you do it manually. Read this, https://tutorial.nxfilter.org/c-acti...gration.php#ms

172.20.20.4 is your MS DNS IP? And is it your DC IP as well? If so, NxFilter tries to bypass your AD domain to 172.20.20.4 automatically.

If there's something different in your AD settings, NxFilter can't find your domain or your MS DNS server.

If I guess it based on the image you posted,

Local DNS : 172.20.20.4
Local Domain : saude.sms,20.20.172.in-addr.arpa,22.20.172.in-addr.arpa

[rating2]

It's done by your AD importation setup automatically. If it doesn't work then you do it manually. Read this, https://tutorial.nxfilter.org/c-acti...gration.php#ms

172.20.20.4 is your MS DNS IP? And is it your DC IP as well? If so, NxFilter tries to bypass your AD domain to 172.20.20.4 automatically.

If there's something different in your AD settings, NxFilter can't find your domain or your MS DNS server.

If I guess it based on the image you posted,

Local DNS : 172.20.20.4
Local Domain : saude.sms,20.20.172.in-addr.arpa,22.20.172.in-addr.arpa

Yes, 172.20.20.4 it's my DC and DNS, my nxfilter is 172.20.20.2 windows 10 machine. If I point a client DNS to 172.20.20.2 today, they can't resolve saude.sms (172.20.20.4)... and the settings in nxfilter are ok, I guess:

[support200]

What did you get when you nslookup for saude.sms then? Try both of these,

nslookup saude.sms 172.20.20.4
nslookup saude.sms 172.20.20.2

And try these as well,

nslookup srvfiles.saude.sms 172.20.20.4
nslookup srvfiles.saude.sms 172.20.20.2

[support200]

You can enable debugging, https://tutorial.nxfilter.org/i-faq.php#enable-debug

And see if it's forwarded to your MS DNS server correctly in /nxfilter/log/nxfilter.log file.

[rating2]

What did you get when you nslookup for saude.sms then? Try both of these,

nslookup saude.sms 172.20.20.4
nslookup saude.sms 172.20.20.2

And try these as well,

nslookup srvfiles.saude.sms 172.20.20.4
nslookup srvfiles.saude.sms 172.20.20.2

Client DNS set to 172.20.20.2

[rating2]

it seems that the client could resolve the FQDN, but doesn't map drives, fail to update the GPOs

[support200]

So, you get NxFilter IP as the answer. Right? Then you need to know why. Did you enable debugging? You could get it by block redirection or auth redirection. When you enable debugging, you can see what it is in your log file.

And when you do nslookup next time add '.' at the end of the queried domain to prevent your system adding its domain like 'saude.sms.saude.sms'.

Did you add that reverse lookup domains into your Local Domain? For dynamic update, you should bypass them as well. i don't know if it's related to your GPO problem though.

[rating2]

So, you get NxFilter IP as the answer. Right? Then you need to know why. Did you enable debugging? You could get it by block redirection or auth redirection. When you enable debugging, you can see what it is in your log file.

And when you do nslookup next time add '.' at the end of the queried domain to prevent your system adding its domain like 'saude.sms.saude.sms'.

Did you add that reverse lookup domains into your Local Domain? For dynamic update, you should bypass them as well. i don't know if it's related to your GPO problem though.

Yes, enabled debbug, but I can't found nothing special...
On reverse lookup it's ok, don't even remeber but I think this records were added automatically except the SRVFILES


On client nslookup seems to be ok! but when I execute a comand to test connection to DC, it fails...


And if I install nxfilter on DC? With DC DNS all ok but no passing through of nxfilter.