Announcement

Collapse
No announcement yet.

NxProxy and VPN network question

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I may be able to send it tomorrow.
    I may have found a workaround - That is to restart the NxProxy service whenever a network change event takes place.

    I am still testing it though.

    Comment


    • #17
      With the next version of NxProxy, you will be able to find a local DNS server by DHCP query not doing an actual DHCP processing. Then what you need is to change its DNS server to 127.0.0.1. Doesn't matter if it has enough permission to change network settings.

      However, in your case, it if's able to change system DNS settings, it should have enough permission. Send me the log file when you are ready I will see if I can find something from it.

      Comment


      • #18
        NxProxy v1.1.5 has been released. It uses DHCP query to find a local DNS server without updating network settings. However, it still does whole DHCP process when it stops since your system needs to have a DNS server other than 127.0.0.1. But we can do DHCP query while it's running so we can detect the change of local DNS server hopefully.

        And we bypass local domains from caching. It might solve your 'same domain but different result according to user location' problem.

        Comment


        • #19
          Awesome. I just updated the server and will update the nxproxy agent as well. I will update you with the results of my testing.

          Comment


          • #20
            Hello.

            I am still experiencing the error:

            HandyMan.hijackDns, Couldn't update it.
            This is the same with either the PCs being AD members or just stand-alone and no GPO running.
            I am already using the latest NxProxy version 1.1.5-win.exe

            Comment


            • #21
              Stop it and try to run it on CMD. Stop it by 'net stop NxProxy' and then go to 'C:\Program Files (x86)\nxproxy\bin\' and run startup.bat script. And see what happens. Run it in your admin CMD.

              Comment


              • #22
                I think the output is the same as the logs. I tried with local admin of the PC and even the domain administrator account and I still get the could not update error.

                Comment


                • #23
                  Then in the directory. Try this,

                  Code:
                  cscript chgdns.vbs
                  And run nslookup and then see if it's changed to 127.0.0.1.

                  Comment

                  Working...
                  X