<?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 Re: pix and active directory in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-and-active-directory/m-p/680787#M497164</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Users normally need to sit in the same domain with AD. You can place the AD and end-users together in your internal network, but put them under separate/different Vlans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With firewall, it will break the domain, but I think you can still try and test it by allowing TCP 445 (open in ACL) from AD to end-users (and vice-versa).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There might be other ports needed as well, like netbios-ns (tcp/udp 137), netbios-dgm (tcp/udp 138) and netbios-ssn (tcp/udp 139)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Oct 2006 23:45:42 GMT</pubDate>
    <dc:creator>a.kiprawih</dc:creator>
    <dc:date>2006-10-10T23:45:42Z</dc:date>
    <item>
      <title>pix and active directory</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-active-directory/m-p/680786#M497162</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Please someone tell me ,where is the best place for active directory server when we have a pix with 6 ports and active directory users on inside interface ?&lt;/P&gt;&lt;P&gt;do i need to seperate active directory server from inside users ?&lt;/P&gt;&lt;P&gt;if i want to do that is there any fixup to permit RPS works ?&lt;/P&gt;&lt;P&gt;This is because of security for domain server and i want to restrict it from inside users that they have not full access to server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 09:13:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-active-directory/m-p/680786#M497162</guid>
      <dc:creator>mrmozaffari</dc:creator>
      <dc:date>2020-02-21T09:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: pix and active directory</title>
      <link>https://community.cisco.com/t5/network-security/pix-and-active-directory/m-p/680787#M497164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Users normally need to sit in the same domain with AD. You can place the AD and end-users together in your internal network, but put them under separate/different Vlans.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With firewall, it will break the domain, but I think you can still try and test it by allowing TCP 445 (open in ACL) from AD to end-users (and vice-versa).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There might be other ports needed as well, like netbios-ns (tcp/udp 137), netbios-dgm (tcp/udp 138) and netbios-ssn (tcp/udp 139)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Oct 2006 23:45:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-and-active-directory/m-p/680787#M497164</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-10-10T23:45:42Z</dc:date>
    </item>
  </channel>
</rss>

