Can't Get SpiceWorks on Azure to Authenticate to AD
-
Oh, I also clarified with him that he has no sub-domain for his AD, it really does use his base domain name.
-
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.
-
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?
-
Has he tried using the FQND in the user account to sync to Azure?
-
@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. -
@aanenih Welcome to the community!
-
I feel as though a firewall or networking issue is the most likely. What VPN type are you using to connect the nodes?
-
@scottalanmiller I am using site to site VPN to connect
-
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. -
@aanenih Very nice, I'm glad you were able to find and fix the issue.
-
@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.
