<div>
Create an access rule between the internal network and the loal host for the protocol you want ISA to use.<br />
Also open the ISA sytem policy and make sure the filtrs are enabled for the traffic you require.<br />
<br />
Everything is different to ISA2000 - it was a one-off....
</div>


Create an access rule between the internal network and the loal host for the protocol you want ISA to use.
Also open the ISA sytem policy and make sure the filtrs are enabled for the traffic you require.

Everything is different to ISA2000 - it was a one-off....

<div>
also monitor all traffic with isa logging when testing your ping, tracert...<br />
then u see which traffic is why denied!
</div>


also monitor all traffic with isa logging when testing your ping, tracert...
then u see which traffic is why denied!

<div>
<div class="content wysiwyg-content">
I upgraded my Web Server from 2000 to 2003, and did a new install of ISA2006. &nbsp;Everyone is able to browse the internet OK and my exchange server works fine with it.<br />
<br />
However, I cannot ping to the internal NIC. &nbsp;The server name cannot be resolved from the DC or my workstation, and the shares on the Web Server are no longer visible. &nbsp;I ran a tracert from my workstation and it resolved it, so DNS must still be able to find it.<br />
<br />
I suspect ISA 2006 has seized control of it somehow, but am at a loss how it could block a ping to the internal NIC.<br />
<br />
Anyone have any ideas what is different between ISA 2000 and 2006 that could cause this?
</div>
</div>


I upgraded my Web Server from 2000 to 2003, and did a new install of ISA2006.  Everyone is able to browse the internet OK and my exchange server works fine with it.

However, I cannot ping to the internal NIC.  The server name cannot be resolved from the DC or my workstation, and the shares on the Web Server are no longer visible.  I ran a tracert from my workstation and it resolved it, so DNS must still be able to find it.

I suspect ISA 2006 has seized control of it somehow, but am at a loss how it could block a ping to the internal NIC.

Anyone have any ideas what is different between ISA 2000 and 2006 that could cause this?

ISA 2006 has made server stealth; no ping, no browsing shares

Microsoft Forefront, formerly known as Internet Security and Acceleration Server (ISA Server), is a network router, firewall, antivirus program, VPN server and web cache that runs on Windows servers. It includes identity management and protection systems, and discontinued systems for threat management and network protection, along with protection for Sharepoint and Exchange. The scope of discussions includes forward and reverse proxy, application and service publishing, virtual private networks (VPNs), outbound access rules, SSL certificates and network routing within either a single node or an highly-available array pairing.

Microsoft Forefront ISA Server

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

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.