This problem occurs due to the presence of the bug CSCsd64333.
When this problem happens, the Domain Name System (DNS) cannot be resolved to internal hosts through the Secure Socket Layer [SSL] VPN Client (SVC) adapter. The DNS requests either seem to go to the wrong adapter or they do not occur at all. However, the routing table appears fine on the SVC client.
It seems that a restart of the physical adapter, either a disable or enable, could be the cause of the problem.
For a workaround,
Download and Install the latest SVC client package, sslclient-win-22.214.171.124.pkg.
hello, we have an ASA and with broadband line: 100M download / 50M uploadwe wanna to do a qos on a specific IP 192.168.47.30since ASA interface is 1G interface (but the broadband line only has 50M upload capacity), we decided to limited the outside ...
Hi,We have url filtering in place for various scores and also for the noscores urlBut I have an issue with whitelisting one kind of url that our friends of Microsoft sent in : https://companyexample.sharepoint.com:443/sites/140205 The :443 is th...
Hello Everyone, Here I have a specific requremtent from a customer. To make things clear. Customer = My Client Client = My Client's Client 1) Customer's Remote working employees will be connecting to en...