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

    Can't Get SpiceWorks on Azure to Authenticate to AD

    Scheduled Pinned Locked Moved IT Discussion
    spiceworksactive directoryazure
    15 Posts 4 Posters 3.7k 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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Both systems are hosted on Microsoft's Azure service. He has tried authenticating with SSL both on and off, same problem.

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

        Oh, I also clarified with him that he has no sub-domain for his AD, it really does use his base domain name.

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

          I'm stepping away for a bit to hang out with @Dominica before it is too late here, hopefully someone has some ideas or insight for him.

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

            Can you sign into that account via any other method?

            Verify the UserName and Password. Using Notepad, is what you think you are typing actually what is being typed?

            1 Reply Last reply Reply Quote 1
            • DustinB3403D
              DustinB3403
              last edited by

              Has he tried using the FQND in the user account to sync to Azure?

              A 1 Reply Last reply Reply Quote 1
              • A
                aanenih @DustinB3403
                last edited by

                @DustinB3403 hi. i am the person that has this problem that needs fixing.
                Yes i have used FQDN in the user account. still get same error.

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

                  @aanenih Welcome to the community!

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

                    I feel as though a firewall or networking issue is the most likely. What VPN type are you using to connect the nodes?

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      aanenih @scottalanmiller
                      last edited by

                      @scottalanmiller I am using site to site VPN to connect

                      1 Reply Last reply Reply Quote 0
                      • A
                        aanenih
                        last edited by

                        Hello Guys, I seem to have found the solution to this issue. By default, Azure has no ports open and that was why i was getting the errors. To solve this problem, i had to create an endpoint for the Virtual machine that had Spiceworks installed in it and open ports 389 and 636 TCP.
                        Now spiceworks syncs and authenticates with the AD on Azure and on premise.

                        DustinB3403D scottalanmillerS 2 Replies Last reply Reply Quote 3
                        • DustinB3403D
                          DustinB3403 @aanenih
                          last edited by

                          @aanenih Very nice, I'm glad you were able to find and fix the issue.

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

                            @aanenih said in Can't Get SpiceWorks on Azure to Authenticate to AD:

                            Hello Guys, I seem to have found the solution to this issue. By default, Azure has no ports open and that was why i was getting the errors. To solve this problem, i had to create an endpoint for the Virtual machine that had Spiceworks installed in it and open ports 389 and 636 TCP.
                            Now spiceworks syncs and authenticates with the AD on Azure and on premise.

                            that's why I was asking for specific VPN details. A VPN on the servers bypasses the Azure ports. A site to site VPN hits the "outside" of the servers and has ports blocked.

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