I tried that and it still thought that network was a public net so it blocks traffic on nic 1 also. I understand that is fixed in 08 r2. I did find something just after sending the original post, local security policy. Tell it any unidentified network is private. We'll see if that works. Steps. 1. run local security policy editor 2. select network list Manager Policies 3. At the right Side you can select & double click: Unidentified Networks 4. In the location type select Private , which means that all Unidentified networks will be consider as private profile network 5. you can also allow the user to change the Location profile
-----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Thursday, June 11, 2009 11:26 AM To: NT System Admin Issues Subject: Re: server 08 firewall On Thu, Jun 11, 2009 at 10:51 AM, Glen Johnson<[email protected]> wrote: > Every so often the second nic will think it is on a Public network and then > the windows firewall blocks lots of connectivity on all the nics. Can't you just disable Win Firewall for that NIC entirely? If it's just a crossover cable to a storage appliance, it's not like there's much danger of unwanted traffic. It might even help performance (I dunno if there's a significant difference in speed between "firewalled 'Private'" and "firewall disabled", but there conceivably could be.) -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
