Windows_Azure Archive

Ever work with a protocol and delve into its inner-workings more than you ever wanted, more than you ever thought you needed to? That’s how I feel about NVGRE after the past two weeks. I guess that is reality when you’re dealing with a new feature, newish protocol, not well documented and that runs on top of an operating system also going under lots of innovation (Hyper-V). Overview Let me just say that most NVGRE implementation guides are based on Hyper-V 2012 syntax — and, to be blunt, they’re outdated and didn’t even work for me on 2012 let alone 2012 R2. For example, none of these examples will work on 2012 R2. http://luka.manojlovic.net/ http://gallery.technet.microsoft.com/scriptcenter/Simple-Hyper-V-Network-d3efb3b8/view/Discussions http://hikmatkanaan.wordpress.com/2013/03/28/windows-2012-hyper-v-3-0-network-virtualization/ They also are based on a single interface server, [&hellip

Read More...

I recently attempted to stand up a secondary domain controller for my home in Windows Azure. I used the cross-premise VPN connectivity option to establish an IPSec VPN between my home Juniper SRX210 gateway router (connected to Comcast cable modem service) and the Windows Azure’s network. On Azure, I used the vNet concept and have extended my home network into Azure using RFC1918 address space. Part of Azure’s recommended SRX configuration guide includes this setting: “set security flow tcp-mss ipsec-vpn mss 1350″. It, however, doesn’t mention anything else about MTU, fragmentation, local MTU settings, etc. When I went to perform directory replication, the new domain controller would hang for at least 5 minutes and then error out with a DC replication error message similar to [&hellip

Read More...


Warning: file_get_contents(/opt/httpd/sites/rickmayberry.com/gpslogger.txt): failed to open stream: No such file or directory in /var/sites/rickmayberry.com/wp-content/plugins/google-maps-widget/google-maps-widget.php on line 150