Reset Search
 

 

Article

KB29025 - DNS requests from WSAM/Pulse SAM connections fail on clients having dual stack (both IPv4/IPv6).

« Go Back

Information

 
Last Modified Date11/23/2015 10:17 PM
Synopsis
On dual stack end-points with Legacy WSAM/Pulse SAM launched, when a resource configured with a hostname is accessed, a quad-record (AAAA) DNS query is initiated first. Since IPv6 addresses are not supported by WSAM/Pulse SAM, it goes via the local DNS server. This article describes two workarounds which can be used in the meantime.
Problem or Goal
DNS requests from WSAM/Pulse SAM connections fail on Dual Stack end-points.
Cause
On a dual stack network with WSAM/Pulse SAM launched, when a resource configured with a Hostname is accessed, a quad-record (AAAA) DNS query is initiated first. Since IPv6 addresses are not supported by WSAM//Pulse SAM, it goes via the local DNS server.

Note: This happens even when the IPv4 Address is preferred by the use of KB (http://support.microsoft.com/kb/929852)

Due to this, the resource does not get SAMized.

Solution
Hostname based IPV4 resource access using WSAM/Pulse SAM is not currently supported from dual stack endpoints and an enhancement request is in place.

Also, you could use one of the workarounds mentioned below in the meantime based on feasibility.
  • Disable IPv6 on the client machines.
  • Use IP Addresses to configure WSAM resources.
Related Links
Attachment 1 
Created ByData Deployment

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255