<?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 Some VPN clients (windows 7) fail to get correct ip address in office mode in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12062#M13017</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running a small cluster of 2 R80.10 SG3100 firewalls. I tried to install some VPN clients on customer computers yesterday, and I got really weird IP address assignments on the clients. One got a 192.168.0.x address and the other a 172.x.x.x address. It's configured to give out admin ip's from manual gateway-defined IP-pools (192.168.3.x) and restricted addresses from ipassignment.conf (192.168.4.x). All of this is working correctly for admin/restricted users on 2 Windows 10 laptops, but 2 different Windows 7 laptops have the issue that they are getting weird addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running E80.64 client on all laptops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea how to troubleshoot? Just try and install a more recent client version? Could not find much fixed issues in E80.80 release notes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Nov 2018 07:32:54 GMT</pubDate>
    <dc:creator>Raine_Widjeskog</dc:creator>
    <dc:date>2018-11-01T07:32:54Z</dc:date>
    <item>
      <title>Some VPN clients (windows 7) fail to get correct ip address in office mode</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12062#M13017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running a small cluster of 2 R80.10 SG3100 firewalls. I tried to install some VPN clients on customer computers yesterday, and I got really weird IP address assignments on the clients. One got a 192.168.0.x address and the other a 172.x.x.x address. It's configured to give out admin ip's from manual gateway-defined IP-pools (192.168.3.x) and restricted addresses from ipassignment.conf (192.168.4.x). All of this is working correctly for admin/restricted users on 2 Windows 10 laptops, but 2 different Windows 7 laptops have the issue that they are getting weird addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running E80.64 client on all laptops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any idea how to troubleshoot? Just try and install a more recent client version? Could not find much fixed issues in E80.80 release notes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2018 07:32:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12062#M13017</guid>
      <dc:creator>Raine_Widjeskog</dc:creator>
      <dc:date>2018-11-01T07:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: Some VPN clients (windows 7) fail to get correct ip address in office mode</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12063#M13018</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One other thing : I also tried disabling the manual IP pools, so that only the restricted 192.168.4.x addresses would be assigned from ipassignment.conf, but this did not change anything on the 2 Windows 7 laptops where i wanted to assign these addresses.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Nov 2018 07:39:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12063#M13018</guid>
      <dc:creator>Raine_Widjeskog</dc:creator>
      <dc:date>2018-11-01T07:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: Some VPN clients (windows 7) fail to get correct ip address in office mode</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12064#M13019</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, managed to&amp;nbsp;reproduce this issue on a third windows 7 computer. It seems older operating systems do not work well with the "basic" securemote installation option. With the "endpoint security VPN" installation option even older windows 7 computers seem to get the correct IP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Nov 2018 07:19:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12064#M13019</guid>
      <dc:creator>Raine_Widjeskog</dc:creator>
      <dc:date>2018-11-02T07:19:02Z</dc:date>
    </item>
    <item>
      <title>Re: Some VPN clients (windows 7) fail to get correct ip address in office mode</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12065#M13020</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has nothing to do with being Windows 7,&amp;nbsp;SecuRemote does not support Office Mode at at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Nov 2018 14:11:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12065#M13020</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2018-11-02T14:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: Some VPN clients (windows 7) fail to get correct ip address in office mode</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12066#M13021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So it would seem. Funny thing i never thought of it since office mode has at least for me worked quite OK with securemote on Windows 10. So in practice - yes it does have something to do with Windows versions &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://community.checkpoint.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt; But it did indeed say in the manual this is not supported.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Nov 2018 06:02:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Some-VPN-clients-windows-7-fail-to-get-correct-ip-address-in/m-p/12066#M13021</guid>
      <dc:creator>Raine_Widjeskog</dc:creator>
      <dc:date>2018-11-05T06:02:21Z</dc:date>
    </item>
  </channel>
</rss>

