<div>
I solved the problem by enabling logging in the Windows Firewall using this page: <a href="http://articles.techrepublic.com.com/5100-10878_11-6171339.html" rel="ugc">http://articles.techrepublic.com.com/5100-10878_11-6171339.html</a>. &nbsp;This showed me the IP address that was being blocked.<br />
<br />
I would still be willing to award points if anyone knows how to customize the Firewall logs so that drop packets are in different file that accept?
</div>


I solved the problem by enabling logging in the Windows Firewall using this page: http://articles.techrepublic.com.com/5100-10878_11-6171339.html [http://articles.techrepublic.com.com/5100-10878_11-6171339.html].  This showed me the IP address that was being blocked.

I would still be willing to award points if anyone knows how to customize the Firewall logs so that drop packets are in different file that accept?

<div>
<div class="content wysiwyg-content">
I am confused on how the Windows Server 2008 Firewall handles it's exclusions. &nbsp;I am trying to limit access to the SQL server to specific IP addresses: 64.26.27.155,75.19.188.102<wbr />,127.0.0.1<wbr />. &nbsp;I may not need the 127.0.0.1, but it's in there.<br />
<br />
Connecting from localhost or 75.19.188.102 works fine. &nbsp;However, we have a website on another server which when I ping the website it goes to 64.26.27.155 (implying this is the IP address of the website I should use in the Firewall exception). &nbsp;When I try to access the application on this website that accesses the SQL server, I get an error that it cannot connect to the SQL server. &nbsp;I am not sure how to trace the connections and determine what is happening. &nbsp;If I allow any computer in the firewall exception, then it works fine from the website.<br />
<br />
Suggestions? &nbsp;Do I have an incorrect assumption in confirming the IP address?
</div>
</div>


I am confused on how the Windows Server 2008 Firewall handles it's exclusions.  I am trying to limit access to the SQL server to specific IP addresses: 64.26.27.155,75.19.188.102,127.0.0.1.  I may not need the 127.0.0.1, but it's in there.

Connecting from localhost or 75.19.188.102 works fine.  However, we have a website on another server which when I ping the website it goes to 64.26.27.155 (implying this is the IP address of the website I should use in the Firewall exception).  When I try to access the application on this website that accesses the SQL server, I get an error that it cannot connect to the SQL server.  I am not sure how to trace the connections and determine what is happening.  If I allow any computer in the firewall exception, then it works fine from the website.

Suggestions?  Do I have an incorrect assumption in confirming the IP address?

Firewall Scope Custom List

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Software firewalls, also known as host-based firewalls, provide a layer of software on one host that controls network traffic in and out of that single machine. Most operating systems now include firewall software, but many available software firewalls include central distribution, antivirus systems and disaster recovery.