WCF Discovery feature in .Net framework cannot be used in Windows XP SP 3 by Ruxo

I wonder if you can provide an update on this bug mainly on its resolution (since it's marked as resolved) as I am experiencing the same behaviour (Win XP SP3) and cannot find any workaround. Disabling antivirus sw, firewall, network interfaces did not help, neither re-installing .NET Framework.

Thanks

This is the test code snippet:
________________________________________
     class MainClass
     {
        [ServiceContract]
        public interface ITestService{}
            public static void Main (string[] args)
            {
            Console.WriteLine("Begin Test");
            var discoveryClient = new DiscoveryClient(new UdpDiscoveryEndpoint());
                try{
                    discoveryClient.Find(new FindCriteria(typeof(ITestService)));
                } catch (Exception ex){
                    Console.WriteLine("Exception!");
                Console.WriteLine(ex);
                }
                discoveryClient.Close();

            Console.WriteLine("Test Ok... ENTER to end.");
            Console.ReadLine();
            }
________________________________________
As you can see, there is no user code involved in the socket binding process. The program runs fine on Windows 7 and Windows 2008 R2 but for my two XP machines it just crashed with the mentioned exception. All tested machines are IPv6 enabled.

Hello Ruxoz-

Thank you for your feedback on Windows Communication Foundation. The exception you are mentioning is normally hit when trying to bind the socket to an IP address that isn't valid. Can you please check this and if possible try on a machine with a different OS. There are currently no known limitations of the WCF Discovery feature on XP.

Thanks,
Erica

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)