<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Windows Socket Initialization Failed upon restarting Windows??? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/windows-socket-initialization-failed-upon-restarting-windows/m-p/148373#M1061732</link>
    <description>&lt;P&gt;I have a remote user that is not able to install the VPN Client 3.6.1 without receiving the error:  Windows Socket Initialization Failed upon restarting Windows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He is using XP Home from his own LAN.  Note there is another user on that same LAN (also with XP Home) that has installed the software successfully (VPN Client 3.6.1) and is able to use the resource without any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I resolve this problem?  They both need to be able to have access to the VPN connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 06:59:48 GMT</pubDate>
    <dc:creator>hufcor</dc:creator>
    <dc:date>2020-02-21T06:59:48Z</dc:date>
    <item>
      <title>Windows Socket Initialization Failed upon restarting Windows???</title>
      <link>https://community.cisco.com/t5/network-security/windows-socket-initialization-failed-upon-restarting-windows/m-p/148373#M1061732</link>
      <description>&lt;P&gt;I have a remote user that is not able to install the VPN Client 3.6.1 without receiving the error:  Windows Socket Initialization Failed upon restarting Windows.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He is using XP Home from his own LAN.  Note there is another user on that same LAN (also with XP Home) that has installed the software successfully (VPN Client 3.6.1) and is able to use the resource without any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do I resolve this problem?  They both need to be able to have access to the VPN connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:59:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/windows-socket-initialization-failed-upon-restarting-windows/m-p/148373#M1061732</guid>
      <dc:creator>hufcor</dc:creator>
      <dc:date>2020-02-21T06:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: Windows Socket Initialization Failed upon restarting Windows</title>
      <link>https://community.cisco.com/t5/network-security/windows-socket-initialization-failed-upon-restarting-windows/m-p/148374#M1061751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Restack your tcpip, and make sure you are not missing the winsock dll. Quite often, restarting the windows machine would also help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Sep 2003 18:05:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/windows-socket-initialization-failed-upon-restarting-windows/m-p/148374#M1061751</guid>
      <dc:creator>umedryk</dc:creator>
      <dc:date>2003-09-22T18:05:33Z</dc:date>
    </item>
  </channel>
</rss>

