RE: .NET 3.5 SP1 loopback issue

2010-05-09 Thread Paul Noone
Yep. Not denying that. It's just annoying under the scenarios you listed when you're not aware of it. :) From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Brian Farnhill Sent: Monday, 10 May 2010 8:37 AM To: ozMOSS Subject: RE: .NET 3.5 SP1 loopback is

RE: .NET 3.5 SP1 loopback issue

2010-05-09 Thread Brian Farnhill
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Monday, 10 May 2010 8:15 AM To: ozMOSS Subject: RE: .NET 3.5 SP1 loopback issue Indeed. But a security feature that tends to break SharePoint farm functionality...? From: ozmoss-boun...@ozmoss.com [

RE: .NET 3.5 SP1 loopback issue

2010-05-09 Thread Paul Noone
Indeed. But a security feature that tends to break SharePoint farm functionality...? From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Daniel Brown Sent: Monday, 10 May 2010 8:10 AM To: ozMOSS Subject: Re: .NET 3.5 SP1 loopback issue This is by design and not a

Re: .NET 3.5 SP1 loopback issue

2010-05-09 Thread Daniel Brown
s very dirty to me. J > > > > *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On > Behalf Of *Daniel Brown > *Sent:* Saturday, 8 May 2010 10:49 AM > *To:* ozMOSS > *Subject:* Re: .NET 3.5 SP1 loopback issue > > > > Can confirm this morning that win2k8

RE: .NET 3.5 SP1 loopback issue

2010-05-09 Thread Paul Noone
Seems crazy there's not a patch (or switch) for this yet. Playing with the registry always feels very dirty to me. :) From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Daniel Brown Sent: Saturday, 8 May 2010 10:49 AM To: ozMOSS Subject: Re: .NET 3.5 SP1 loo

Re: .NET 3.5 SP1 loopback issue

2010-05-07 Thread Daniel Brown
Can confirm this morning that win2k8 r2 is effected by this also On Fri, May 7, 2010 at 12:16 PM, Paul Noone < paul.no...@ceosyd.catholic.edu.au> wrote: > Can I ask if everyone has routinely applied the fix for this issue or if > it’s since been resolved with a patch somewhere? > > > > http://su

RE: .NET 3.5 SP1 loopback issue

2010-05-06 Thread Prashanth Thiyagalingam
I did applied for Search Indexer problem, and it was fixed. But not sure about the usage report problem. regards, Prashanth From: paul.no...@ceosyd.catholic.edu.au To: ozmoss@ozmoss.com Date: Fri, 7 May 2010 13:22:15 +1000 Subject: RE: .NET 3.5 SP1 loopback issue Search indexer

RE: .NET 3.5 SP1 loopback issue

2010-05-06 Thread Paul Noone
[mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Turner Sent: Friday, 7 May 2010 12:52 PM To: ozMOSS Subject: RE: .NET 3.5 SP1 loopback issue It depends on lots of things. Mainly if your search indexer is also a WFE then you will need it. If the Indexer is separate you don't. Generally I

RE: .NET 3.5 SP1 loopback issue

2010-05-06 Thread Paul Turner
ed to delete it immediately. Any opinion expressed in this e-mail may not necessarily be that of DWS Pty Ltd. Please consider the environment before printing this email. From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of Paul Noone Sent: Friday, 7 May 2010 12:16 PM To: oz

.NET 3.5 SP1 loopback issue

2010-05-06 Thread Paul Noone
Can I ask if everyone has routinely applied the fix for this issue or if it's since been resolved with a patch somewhere? http://support.microsoft.com/kb/896861 I'm thinking it's the cause for my 401 errors when trying to call a web service via a workflow. Kind regards, Paul Noone --