Comments on: Disabling IPv6 on Server Core and Hyper-V Server http://tristanwatkins.com/index.php/disabling-ipv6/?utm_source=rss&utm_medium=rss&utm_campaign=disabling-ipv6 Technical guidance for SharePoint, Cloud Services, Windows and more Thu, 02 Feb 2012 22:11:06 +0000 hourly 1 http://wordpress.org/?v=3.1.4 By: Sharepoint 2010 Installation in Hyper V – “Cannot connect to database master” « Joe Rivera's Techno-Ramblings http://tristanwatkins.com/index.php/disabling-ipv6/comment-page-1/#comment-4249 Sharepoint 2010 Installation in Hyper V – “Cannot connect to database master” « Joe Rivera's Techno-Ramblings Tue, 19 Oct 2010 15:56:03 +0000 http://tristanwatkins.com/?p=286#comment-4249 [...] use both IPv4 and IPv6, but it seems that the Sharepoint wizard uses IPv4 to connect to SQL. This article that I found told of a registry change, but those type of changes I try to avoid, so with a little [...] [...] use both IPv4 and IPv6, but it seems that the Sharepoint wizard uses IPv4 to connect to SQL. This article that I found told of a registry change, but those type of changes I try to avoid, so with a little [...]

]]> By: Tristan Watkins http://tristanwatkins.com/index.php/disabling-ipv6/comment-page-1/#comment-951 Tristan Watkins Mon, 29 Mar 2010 20:35:46 +0000 http://tristanwatkins.com/?p=286#comment-951 And if you find anything else out, I'd love to know. Sorry if I've inadvertently caused you any headaches. And if you find anything else out, I’d love to know. Sorry if I’ve inadvertently caused you any headaches.

]]> By: Tristan Watkins http://tristanwatkins.com/index.php/disabling-ipv6/comment-page-1/#comment-950 Tristan Watkins Mon, 29 Mar 2010 20:31:37 +0000 http://tristanwatkins.com/?p=286#comment-950 How strange. Microsoft have deleted the original KB article. It might be worth dropping Tony Soper an e-mail (upper left-hand corner of his site), as he originally posted the guidance. I wonder if something will have changed since then. See his original post here: http://blogs.technet.com/tonyso/archive/2009/09/28/hyper-v-how-to-turn-off-ipv6.aspx To answer your question re: whether IPv6 is necessary, it totally depends on your tools/requirements. I've successfully disabled it in many instances but your infrastructure may implement it more widely than mine. How strange. Microsoft have deleted the original KB article. It might be worth dropping Tony Soper an e-mail (upper left-hand corner of his site), as he originally posted the guidance. I wonder if something will have changed since then. See his original post here: http://blogs.technet.com/tonyso/archive/2009/09/28/hyper-v-how-to-turn-off-ipv6.aspx

To answer your question re: whether IPv6 is necessary, it totally depends on your tools/requirements. I’ve successfully disabled it in many instances but your infrastructure may implement it more widely than mine.

]]> By: andrew http://tristanwatkins.com/index.php/disabling-ipv6/comment-page-1/#comment-945 andrew Mon, 29 Mar 2010 17:48:12 +0000 http://tristanwatkins.com/?p=286#comment-945 Both of the Hyper-V hosts (running 2008 R1 SP2) I've tried this on go haywire upon reboot. They lose connectivity and refuse to accept RDP connections. Connecting over my IP-KVM, I'm able to locally log on, but it takes 2 minutes to load the user profile, and then throws up error messages about everything. Rebooting into safe mode, deleting the reg key, and rebooting fixes it immediately. Is IPv6 necessary for Hyper-V? I've disabled it on other machines, real and virtual, with no side effects--it only seems to affect my Hyper-V hosts. Both of the Hyper-V hosts (running 2008 R1 SP2) I’ve tried this on go haywire upon reboot. They lose connectivity and refuse to accept RDP connections. Connecting over my IP-KVM, I’m able to locally log on, but it takes 2 minutes to load the user profile, and then throws up error messages about everything. Rebooting into safe mode, deleting the reg key, and rebooting fixes it immediately.
Is IPv6 necessary for Hyper-V? I’ve disabled it on other machines, real and virtual, with no side effects–it only seems to affect my Hyper-V hosts.

]]>