ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Group Policy and VPNs

    Scheduled Pinned Locked Moved IT Discussion
    windowsgroup policyvpn
    11 Posts 4 Posters 1.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gjacobseG
      gjacobse
      last edited by

      We have the problem with Pertino that while nearly everything works, it is 'borking' DNS is a manner that things like MS Outlook can't find Office365.

      And the native MS Windows VPN gets borked and won't connect to an ERL from time to time, forcing the user back to Pertino

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @gjacobse
        last edited by

        @gjacobse said in Group Policy and VPNs:

        We have the problem with Pertino that while nearly everything works, it is 'borking' DNS is a manner that things like MS Outlook can't find Office365.

        Is that because of the AD Connector?

        1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender
          last edited by

          SDN and internal DNS seems to be the problem. If one could go completely to an external DNS, that might help, but you're still having two IPs on everything, both a physical NIC/VM and the SDN NIC.

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • gjacobseG
            gjacobse
            last edited by

            What is AD Connector? This is not something I am familiar with. Where would it be located?

            DashrenderD scottalanmillerS 2 Replies Last reply Reply Quote 0
            • DashrenderD
              Dashrender @gjacobse
              last edited by

              @gjacobse said in Group Policy and VPNs:

              What is AD Connector? This is not something I am familiar with. Where would it be located?

              It was an thing you could buy from Pertino that fixed DNS issues with AD.

              1 Reply Last reply Reply Quote 1
              • scottalanmillerS
                scottalanmiller @gjacobse
                last edited by

                @gjacobse said in Group Policy and VPNs:

                What is AD Connector? This is not something I am familiar with. Where would it be located?

                It's the piece of Pertino that you have to pay extra for in order to get AD to work correctly with Pertino. You can tell if you have it because it should be listed as one of the add ons in the console. Also, if AD servers are set up in Pertino, that's the functionality that allows that to happen. It allows you to select up to three AD servers that will be defined by and controlled by Pertino.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @Dashrender
                  last edited by

                  @Dashrender said in Group Policy and VPNs:

                  SDN and internal DNS seems to be the problem. If one could go completely to an external DNS, that might help, but you're still having two IPs on everything, both a physical NIC/VM and the SDN NIC.

                  The theory of an overlay SDN is that every device has the SDN IP and should use only that.

                  1 Reply Last reply Reply Quote 0
                  • gjacobseG
                    gjacobse
                    last edited by

                    Well from this - it would appear that it should be available.

                    0_1482368370888_2016-12-21 19_59_11-2016 SSI Keyfile.csv - Excel.png

                    1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller
                      last edited by

                      Available, but is it being used properly?

                      1 Reply Last reply Reply Quote 0
                      • NerdyDadN
                        NerdyDad
                        last edited by

                        We use Cisco Any Connect that authenticates against AD, but is not tied to any kind of GPS and it works for us just fine. Except for deployment, I see no need in using GPS.

                        If we use GPS for anything, it's with RADIUS for our wireless network. That works in one location but not the other. And this is only because both locations have different wireless systems and in how each system implements RADIUS and authenticates a laptop against an OU.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post