The Goal : Move all AD services to a Server 2012 R2 virtual machine inside Azure.
Why The majority of my employees and contractors work from home or in the field, all around the nation. Our office only supports two people working full time as resource management.
What we have done Setup a 2012 R2 server with the AD role and DNS. Setup a Azure Virtual Network, and tied in the mobile systems and office systems via VPN. The server is on 10.10.80.1 inside the virtual network.
What we expect to do To help protect information and assets, our resources should be able to login via the domain hosted by the AD/DNS server in the virtual network, this would control desktop settings, etc as needed for our always mobile resources.
What is actually happening All units are pinging back and talking. I can see the AD server when I ping 10.10.80.1 with an outstanding response time. However, when I change the systems from WORKGROUP to a DOMAIN, I get the standard issue error that the Active Directory Domain Controller couldn't be found.
Now by all that I understand about AD, the DNS is there, and the AD is in fact online. So why are we having issues here? Any advice or fixes would be so helpful. Thank you in advance!
Your on-premise gateway may be blocking the ports necessary for AD access from on-prem devices to AD in Azure (I'm assuming based on what you've written this is what you are aiming to achieve). Here is a list of ports: http://technet.microsoft.com/en-us/library/dd772723(v=ws.10).aspx.
If your gateway's not blocking ports it might be due to settings on your firewall device - take a look at the content here around MTU and RPC settings: http://blog.kloud.com.au/2012/07/25/windows-azure-virtual-network-vpn-with-tmg-2010/
The Goal : Move all AD services to a Server 2012 R2 virtual machine inside Azure.
Why The majority of my employees and contractors work from home or in the field, all around the nation. Our office only supports two people working full time as resource management.
What we have done Setup a 2012 R2 server with the AD role and DNS. Setup a Azure Virtual Network, and tied in the mobile systems and office systems via VPN. The server is on 10.10.80.1 inside the virtual network.
What we expect to do To help protect information and assets, our resources should be able to login via the domain hosted by the AD/DNS server in the virtual network, this would control desktop settings, etc as needed for our always mobile resources.
What is actually happening All units are pinging back and talking. I can see the AD server when I ping 10.10.80.1 with an outstanding response time. However, when I change the systems from WORKGROUP to a DOMAIN, I get the standard issue error that the Active Directory Domain Controller couldn't be found.
Now by all that I understand about AD, the DNS is there, and the AD is in fact online. So why are we having issues here? Any advice or fixes would be so helpful. Thank you in advance!
Your on-premise gateway may be blocking the ports necessary for AD access from on-prem devices to AD in Azure (I'm assuming based on what you've written this is what you are aiming to achieve). Here is a list of ports: http://technet.microsoft.com/en-us/library/dd772723(v=ws.10).aspx.
If your gateway's not blocking ports it might be due to settings on your firewall device - take a look at the content here around MTU and RPC settings: http://blog.kloud.com.au/2012/07/25/windows-azure-virtual-network-vpn-with-tmg-2010/
0 commentaires:
Enregistrer un commentaire