After Win2k3 Service Pack 2 unable to ping or enumerate

I've got 4 Proliant DL380s running Windows Server 2003 that I upgraded
to Service Pack 2, since the upgrade they haven't responded to pings.
All services run fine and accepts connections fine,but they do not
respond to pings from any other hosts on the network. Pinging the
loopback from the server works, and I've ensured that there are no
firewalls or anything else that would be blocking ICMP between the
servers and the client machines.

It was brought to my attention after we deployed a new asset tracking
system that enumerates Windows systems via RPC/DCOM, but pings first
to see if the host is alive, and it was unable to enumerate these 4
servers. There are 6 identical servers in the same rack with them
that also have SP2 installed that have no issues.

I've also confirmed that there is nothing in the NIC hardware
configuration itself that could be causing this issue.

Any ideas, because I'm stumped?

-------
Tyler Duzan
A+, Network+, Linux+, Security+, MCP

On Sep 11, 10:48*am, tris...@gmail.com wrote:
> I've got 4 Proliant DL380s running Windows Server 2003 that I upgraded
> to Service Pack 2, since the upgrade they haven't responded to pings.
> All services run fine and accepts connections fine,but they do not
> respond to pings from any other hosts on the network. *Pinging the
> loopback from the server works, and I've ensured that there are no
> firewalls or anything else that would be blocking ICMP between the
> servers and the client machines.
>
> It was brought to my attention after we deployed a new asset tracking
> system that enumerates Windows systems via RPC/DCOM, but pings first
> to see if the host is alive, and it was unable to enumerate these 4
> servers. *There are 6 identical servers in the same rack with them
> that also have SP2 installed that have no issues.
>
> I've also confirmed that there is nothing in the NIC hardware
> configuration itself that could be causing this issue.
>
> Any ideas, because I'm stumped?
>
> -------
> Tyler Duzan
> A+, Network+, Linux+, Security+, MCP

Bumping this

On Sep 12, 11:48*am, tris...@gmail.com wrote:
> On Sep 11, 10:48*am, tris...@gmail.com wrote:
>
>
>
> > I've got 4 Proliant DL380s running Windows Server 2003 that I upgraded
> > to Service Pack 2, since the upgrade they haven't responded to pings.
> > All services run fine and accepts connections fine,but they do not
> > respond to pings from any other hosts on the network. *Pinging the
> > loopback from the server works, and I've ensured that there are no
> > firewalls or anything else that would be blocking ICMP between the
> > servers and the client machines.
>
> > It was brought to my attention after we deployed a new asset tracking
> > system that enumerates Windows systems via RPC/DCOM, but pings first
> > to see if the host is alive, and it was unable to enumerate these 4
> > servers. *There are 6 identical servers in the same rack with them
> > that also have SP2 installed that have no issues.
>
> > I've also confirmed that there is nothing in the NIC hardware
> > configuration itself that could be causing this issue.
>
> > Any ideas, because I'm stumped?
>
> > -------
> > Tyler Duzan
> > A+, Network+, Linux+, Security+, MCP
>
> Bumping this

I'm guessing you already checked your firewall? I got that once before
after doing the sp update.

On Sep 14, 2:32*am, Neebski <neeb...@gmail.com> wrote:
> On Sep 12, 11:48*am, tris...@gmail.com wrote:
>
>
>
>
>
> > On Sep 11, 10:48*am, tris...@gmail.com wrote:
>
> > > I've got 4 Proliant DL380s running Windows Server 2003 that I upgraded
> > > to Service Pack 2, since the upgrade they haven't responded to pings.
> > > All services run fine and accepts connections fine,but they do not
> > > respond to pings from any other hosts on the network. *Pinging the
> > > loopback from the server works, and I've ensured that there are no
> > > firewalls or anything else that would be blocking ICMP between the
> > > servers and the client machines.
>
> > > It was brought to my attention after we deployed a new asset tracking
> > > system that enumerates Windows systems via RPC/DCOM, but pings first
> > > to see if the host is alive, and it was unable to enumerate these 4
> > > servers. *There are 6 identical servers in the same rack with them
> > > that also have SP2 installed that have no issues.
>
> > > I've also confirmed that there is nothing in the NIC hardware
> > > configuration itself that could be causing this issue.
>
> > > Any ideas, because I'm stumped?
>
> > > -------
> > > Tyler Duzan
> > > A+, Network+, Linux+, Security+, MCP
>
> > Bumping this
>
> I'm guessing you already checked your firewall? I got that once before
> after doing the sp update.- Hide quoted text -
>
> - Show quoted text -

Yes, the firewall is turned off on that system and we have no
firewalls between subnets, only routing, and the routing is not
excluding ICMP traffic.
I also posted about this over at MSFN and haven't found anybody there
with any ideas. Seems like it's a fairly weird issue.

-------
Tyler Duzan
A+, Network+, Linux+, Security+, MCP

Your probally looking at an ipsec issue

--
cristak
-----------------------------------------------------------------------
cristaki's Profile: http://forums.techarena.in/members/cristaki.ht
View this thread: http://forums.techarena.in/server-networking/1036471.ht

http://forums.techarena.i

I can't find the original message right now, but keep in mind that Windows
2003 SP2 automatically enables Windows Firewall.

--------

Networking and Telecommunications group
http://groups.google.com/group/networking_and_telecoms