Windows Azure Connect Diagnostic Errors (no connectivity policy, no IPsec cert)
-
19 ianuarie 2012 16:53
Hi there,
I'm trying to set up Azure Connect from my local machine to my Azure account to allow me to do some worker-role based load testing.
However, there seems to be some issues with the Azure Connect connection. When I run the diagnostic check I get two errors:
Policy Check: There is no connectivity policy on this machine.
IPsec certificate check: No IPsec certificate was found. Please ensure that this machine is configured for connectivity.
I looked at the MSDN documentation on this, and it didn't seem so helpful. ( http://msdn.microsoft.com/en-us/library/windowsazure/gg433016.aspx )
The solution offered was "Verify that your computer has an active internet connection."
Well, my computer definitely has an active internet connection, can anyone suggest how I might go about fixing this?
Toate mesajele
-
20 ianuarie 2012 03:35ModeratorIs this local machine in a machine ground and is "linked" to an Azure role?
Jason Chen, Windows Azure PM -
20 ianuarie 2012 06:13Moderator
Check this Link and see if helps:
http://blogs.msdn.com/b/james_morey/archive/2005/06/20/430894.aspx
Thanks
Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework- Editat de Arwind - MSFTModerator 20 ianuarie 2012 06:13
- Propus ca răspuns de Arwind - MSFTModerator 25 ianuarie 2012 13:35
- Marcat ca răspuns de Arwind - MSFTModerator 2 martie 2012 14:16
-
2 martie 2012 12:43
Hi SamArkadium,
As per my knowledge The policy will get available when you add the local machine in Connect endpoint group on Azure management portal. So go to portal, select "virtual Network" and create group. Add your desired Azure role and your local endpoint in the group the refresh policy by right clicking on connect agent logo on your local machine.
Hope it helps.
Mark As Answer if it helps you | My Blog
- Propus ca răspuns de kunal chandratre 2 martie 2012 12:43
- Anulare propunere ca răspuns de kunal chandratre 2 martie 2012 12:43
- Propus ca răspuns de kunal chandratre 2 martie 2012 12:43
- Marcat ca răspuns de Arwind - MSFTModerator 2 martie 2012 14:16
-
13 iunie 2012 06:40
Hi all,
I had the same symptoms and solved by inserting the mentioned endpoint into a proper group within the Azure Management Portal ("Move into group"), which I simply not did forget before! :-)
- Propus ca răspuns de JustIndeed 13 iunie 2012 06:40