external network adapter show local connection only

I have 2 windows server 2008, both with 2 Nic, one for internal and one for
external, one of the server's external Nic showing status with "local only",
and cannot ping/access Internet, both configured with same settings, i have
check the pysical NIC and cable, it is working fine, the differences are the
problematic server is a domain controller installed with active directory and
DNS. When run a diagnotics, it shows:

Windows confirmed that "primary dns server" is currently online, but is not
responding to connection attempts at this time

The following policy might need to be adjusted to allow Windows to connect:

Pokicy provider:-
Filter Name:local send filter driver filter

fyi, the server's firewall had been disable.

and check on the audit logs, there is an error:
The Windows Filtering Platform blocked a packet.

Application Information:
Process ID: 0
Application Name: -

Network Information:
Direction: Outbound
Source Address: 202.157.152.85
Source Port: 0
Destination Address: 202.157.152.95
Destination Port: 0
Protocol: 0

Filter Information:
Filter Run-Time ID: 65980
Layer Name: IP Packet
Layer Run-Time ID: 4

any help please?

"wlmak" <(E-Mail Removed)> wrote in message
news71CC719-0F2E-40F2-A126-(E-Mail Removed)...
> I have 2 windows server 2008, both with 2 Nic, one for internal and one
> for
> external, one of the server's external Nic showing status with "local
> only",
> and cannot ping/access Internet, both configured with same settings, i
> have
> check the pysical NIC and cable, it is working fine, the differences are
> the
> problematic server is a domain controller installed with active directory
> and
> DNS. When run a diagnotics, it shows:
>
> Windows confirmed that "primary dns server" is currently online, but is
> not
> responding to connection attempts at this time
>
> The following policy might need to be adjusted to allow Windows to
> connect:
>
> Pokicy provider:-
> Filter Name:local send filter driver filter
>
> fyi, the server's firewall had been disable.
>
> and check on the audit logs, there is an error:
> The Windows Filtering Platform blocked a packet.
>
> Application Information:
> Process ID: 0
> Application Name: -
>
> Network Information:
> Direction: Outbound
> Source Address: 202.157.152.85
> Source Port: 0
> Destination Address: 202.157.152.95
> Destination Port: 0
> Protocol: 0
>
> Filter Information:
> Filter Run-Time ID: 65980
> Layer Name: IP Packet
> Layer Run-Time ID: 4
>
> any help please?

Why do you have a domain controller connected to two networks? This has
been a known problem since NT days (and it still is). My guess is that
Windows is protecting you from yourself!

I would reconfigure the network so that the DC uses only one NIC. The
domain firewall policy is probably preventing you from accessing the
Internet directly.
>