WSE 3.0 not Supporting IPv6 RRS feed

  • Question

  • My project uses webservices hosted in windows services to communicate between client and server which uses WSE 3.0(web service enhancements) component to create communication channels.

    When server and client are in IPv6 network then client is not able to communicate and throws error as screen shot below.

    1. No connection could be made because the target machine actively refused it. 2001::ff9b:0000:0000:0000:0000:1234:5678/96:8211.

    2. No connection could be made because the target machine actively refused it [::1]:8211.

    I have gone through many blogs and articles which has suggested that WSE should migrate to WCF.

    Looking for recommended solution from here is-:

    1. Can we enhance or is there any to support IPv6 in WSE 3.0?

    2. Is it mandatory to migrate existing FCS WSE 3.0 to WCF to support IPv6?

    Friday, July 26, 2019 1:01 PM

All replies

  • Hi,

    The below code is the usage of IPV6 address over https.
    Please consider using the above style in the actual address.
    Moreover, as far as I know, I don't think changes at the network level will affect the use of the framework. Maybe we just need to change the address when we specify the endpoint.
    If WSE does not support IPV6 address, you could also use other technology to create the backend service, such as WebAPI.
    Feel free to let me know if there is anything I can help with.
    Best Regards

    Monday, July 29, 2019 7:56 AM
  • how to get the IPV6 as you formed in the endpoint?

    is WSE 3.0 support IPv6?

    Monday, July 29, 2019 6:42 PM
  • Hi,

    Check you NIC status or we use Shell command, Ipconfig

    I did not know much about WSE, but I think the iPV6 address will work still.  The changes at the network level should not affect the framework of the application layer based on the OSI model. WCF supports IPV6 addressing.
    Anyway, we had better try it then come to a conclusion.
    Best Regards

    Tuesday, July 30, 2019 2:27 AM
  • My application windows services are completely dependent on WSE 3.0 and it is all working well with ISP IPv4 and also with the VPN connected when ISP is IPv6.

    if we disconnect the VPN and ISP is IPv6 then hosted windows service are failing to perform the task, it is not connecting.

    as you said it should work but I found that if IPv4 is working why it is stopping when IPv6 come into the picture?

    I am here to get the supportive and best solution from microsoft on WSE 3.0 Component that will it support the IPv6 communication or not if it supports please provide the solution?

    if WSE 3.0 does not support IPv6 enable network please make it clear and give the perfect recommendation about migration to WCF so it helps to make our decision on migration from WSE to WCF and our application will support IPv6.

    My application have a huge dependency on WSE 3.0 and if i have to migrate to WCF then it will take a huge effort that is what i am here if WSE supports IPv6 then why should i Migrate to WCF?

    Can you please let me know the solution to support IPv6 for my application with WSE or WCF?

    I am searching and going through many articles but not getting the proper solution but this time i have to come with some solution so my application will be able to support the IPv6.

    if WSE is obsolete and microsoft is not supporting it then why microsoft kept the download link for WSE component so request you to please get somebody involved who knows well about WSE 3.0 component and give a clear picture which helps us to come to conclusion and will able to go ahead with migration or solution with WSE?

    Tuesday, July 30, 2019 11:58 AM
  • Can i expect the reply here on my query?

    I am waiting for the response so please provide your suggestion.

    Thursday, August 1, 2019 3:45 AM
  • Bro,
    I am interested in the WCF framework, so I am here for a reply to the related WCF issue, but I am not a member of Microsoft. 
    Frankly speaking, I don’t know WSE3.0 and there is so little document for that on the internet. The only thing I am for sure is WCF support IPV6, while as you know, WCF is also being phased out. The latest backend service is typically restful or cloud-based, such as Azure function. I'm sorry for I didn't find any useful advice for you.

    Thanks for your understanding.
    Best Regards

    Thursday, August 1, 2019 9:03 AM