New Windows 2003 unable to ping Firewall

Hi, All

I have some weird problem here on 2 instances in 2
different location when I setup windows 2003 standard
edition with AD and Exchange2003. After successful
installation, I did some ping test to the firewall to
ensure the connectivity is up. The problem is after
pinging for a few time I will get request time out from
the firewall.

The other servers have no problem pinging to the firewall
and the network is a flat network without any VLANs. The
first incident happen in just a few hours of successful
installation to a Check Point 4.1 firewall. The second
incident happen a few days after installation on a
Watchguard Firebox II 700.

In the end I resolve the problem by changing the IP
address of the server, but if I change it back the same
problem will occur again.

Has anybody hit this sort of problem before ??

Thanks
Mike

--------------------
>Content-Class: urn:content-classes:message
>From: "Mike" <(E-Mail Removed)>
>Sender: "Mike" <(E-Mail Removed)>
>Subject: New Windows 2003 unable to ping Firewall
>Date: Sun, 11 Apr 2004 22:48:12 -0700
>Lines: 25
>Message-ID: <1b37401c42051$bdfbc490$(E-Mail Removed)>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcQgUb37+eW4rja8S22aCQDrf9B9wg==
>Newsgroups: microsoft.public.windows.server.networking
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.networking:11490
>NNTP-Posting-Host: tk2msftngxa13.phx.gbl 10.40.1.165
>X-Tomcat-NG: microsoft.public.windows.server.networking
>
>Hi, All
>
>I have some weird problem here on 2 instances in 2
>different location when I setup windows 2003 standard
>edition with AD and Exchange2003. After successful
>installation, I did some ping test to the firewall to
>ensure the connectivity is up. The problem is after
>pinging for a few time I will get request time out from
>the firewall.
>
>The other servers have no problem pinging to the firewall
>and the network is a flat network without any VLANs. The
>first incident happen in just a few hours of successful
>installation to a Check Point 4.1 firewall. The second
>incident happen a few days after installation on a
>Watchguard Firebox II 700.
>
>In the end I resolve the problem by changing the IP
>address of the server, but if I change it back the same
>problem will occur again.
>
>Has anybody hit this sort of problem before ??
>
>Thanks
>Mike
>
Mike,

The Request Times Out message is key in this situation. This says the server sent out the ECHO Request but something happened in the
communication:

1. The message never made it to the target host. The TTL expired before reaching the host.
2. The host received the message but chose not to reply.
3. The host replied, but the reply never made it back to the sender.

The only way to be sure of what is happening here is to take a Network Monitor trace on both sides of the communication to see what is happening. Also
check for the latest driver for the NIC. The fact that the initial ping is working and then subsequent pings fail is definitely strange.

T.J. Campana [MSFT]
Microsoft EPS Networking
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.