MSN Messenger does not work - ERROR_INTERNET_CANNOT_CONNECT - 0x2efd

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Consider the following scenario:

��������� You have ISA 2006 EE with Single Network Adapter Template for CARP.

��������� Your network configuration is correct with all Internal Network addresses set.

��������� You have a rule Internal to Internal HTTP, HTTPS, FTP for All Users.

��������� Web Proxy on the Internal network is not requiring user authentication.

You receive the following error:

�

MSN Messenger ERROR_INTERNET_CANNOT_CONNECT - 0x2efd

�

�

On the Internet Explorer if you configure the Lan Settings to use Proxy and you specify the IP of the NLB or the IP of one of the nodes the MSN and WEB Access works fine.

�

However if we specify in the Internet Explorer to use �Automatically Detect Settings� you have Internet Access but MSN Messenger does not work and you receive the error message earlier in this section.

�

ISA does not show any access denied error message.

.

�

��������� ISA is in single network adapter this means that internal network has IP range from 0.0.0.0. - 255.255.255.255 with the exception of 127.0.0.0.

�

��������� Customer was checking the option: bypass all local addresses in ISA. This means that the CARP script had all those exceptions.

�

��������� Default browser was not Internet Explorer.

�

��������� To make sure if you have this problem, download and review the script:

http://isaserver:8080/array.dll?Get.Routing.Script

�

�

To resolve this issue, follow these steps:

1.������ Uncheck the option to bypass all local addresses in ISA so that the local ranges (in this case all ranges) do not appear in the script.

2.������ Change default browser to Internet Explorer.

�