Only one workstation, the rules defined in NXFILTER through NXPROXY work perfectly.
NXFILTER 127.0.0.1 TUTORIAL HOW TO
You can see in the photos I sent by wetransfer because, I don't know how to send attachments on this forum. In this branch, we have 3 workstations, all with DHCP enabled. In the past topic I was having trouble getting NXPROXY right in the head office, now, I'm having trouble at the branch company. On which step, it doesn't work? On which step, you see the difference between your users? You can see those domains on NxFilter's 'Logging > Request'. You can see those domains requested in NxProxy log files. You can test it with nslookup as it's a DNS server.
NXFILTER 127.0.0.1 TUTORIAL WINDOWS
Your Windows DNS settings changed to point 127.0.0.1 as its DNS server.
You don't need any special settings for NxProxy. And your nslookup should be working if you see '127.0.0.1' as your server address.Īnd in previous post, you were talking about some firewall rules. If it's NxProxy, there's no partial working. So it works for Administrator accounts but doesn't work entirely for other accounts without admin privileges? So it works partially still or do you have other agent like CxBlock for those other accounts? Last time, you mentioned on CxBlock. Now, when I access the same computer, with the administrator, the filter works perfectly for browsed URLs and for all network services. The service is started, the process is in memory, the DNS (IP ADDRESS) is correct, but this user without an administrator profile does not work. NXPROXY in this user's profile only filters URLs opened by browsers and not other Windows services that use the data network. I just noticed that when I connect a computer with NXPROXY in the user profile, it does not contain the other URLs that WINDOWS and other applications use to connect (WINDOWS UPDATE, ADOBE, JAVA). So, it works for your new user accounts and not for old accounts? Did you see the network settings of your old users? NxProxy listens on 127.0.0.1/53 and it updates your Windows DNS settings to have 127.0.0.1/53 as the only DNS server.Īll Windows settings are correct pointed to DNS 127.0.0.1. If it works, it works against DNS requests not for browsers. I ask, is there any way or tip to fix this problem in the profile of these 3 Windows users, without having to create a new user profile on the computer?Ĭreating a new user on each computer would be a lot of work because I would have to reconfigure all the icons, applications, links to services again and that I would not like, so if someone knows or has any more tips (clue) of what it can be and how to solve, I appreciate it.įirstly, 'the filter only works by taking the URLs accessed by browsers'. Otherwise, the filter only works by taking the URLs accessed by browsers. Creating a new user the 3 computers where my users use, the filter works completely taking everything according to policy. After a lot of work, cleaning the user's cache, cleaning the Windows disk, repairing the windows, (sfc / scannow) and others, I found that the filter only works completely on these 3 computers of users with problems, after I create a new user on the same computer where they work. Only browser accesses are filtered, but not WINDOWS ( filter BACKGROUND). I noticed that on only 3 users' computers, the filter is not working completely. I am using NXFILTER 4.3.8.7 with NXPROXY 1.0.7 on each of my users' workstations.
0 kommentar(er)
