Cannot acknowledge ping request

[Luchito]

My system (Windows XP Pro SP2) can no longer acknowledge ping requests.
I ping other systems and apparently all applications are working but I
cannot ping my system from another one (request times out). I can
access network resources but all other systems on my network cannot
access any of my shared drives (\\xxxxxxxx cannot be accessed. network
path could not be found). My system has a static IP (reserved through
DHCP server) and DNS server seems to resolve correctly. I have
attempted turning my firewall complelety off and problem still exists.
Latest attempt was to restore windows firewall to default settings but
that did not resolve the issue. Please help!

 

[Steven L Umbach]

Assuming you have other firewall protection for the network from the
internet try booting into Safe Mode with networking to see if that makes any
difference or not and if it does you may have another application/services
that is filtering ICMP and other traffic. Also try accessing your share
using \\xxx.xxx.xxx.xxx using the actual IP address of your computer instead
of name and try pinging by IP address if you are only trying name
urrently. --- Steve

 

[Luchito]

I rebooted the system in Safe Mode with networking and I got the same
results when trying to ping my system (request timed out). I also
attempted to access the shared drive using the actual IP address of my
system but again, the network path could not be found.

 

[Steven L Umbach]

Could you possibly run the command ipconfig /all on that computer and a
computer that can not ping it and netsh firewall show state on the computer
than can not be pinged and paste the results here in a reply? --- Steve

 

[Luchito]

MY SYSTEM:

Windows IP Configuration

Host Name . . . . . . . . . . . . : lburitica
Primary Dns Suffix . . . . . . . : midwest.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : midwest.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Controller
Physical Address. . . . . . . . . : 00-11-43-48-72-0C
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.100.106
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.5
DHCP Server . . . . . . . . . . . : 192.168.100.6
DNS Servers . . . . . . . . . . . : 192.168.100.4
192.168.100.208
Lease Obtained. . . . . . . . . . :Thursday, January 26, 2006
8:49:17 AM
Lease Expires . . . . . . . . . . : Sunday, February 19, 2006
8:49:17 AM


SERVER:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : mwffil
Primary DNS Suffix . . . . . . . : midwest.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : midwest.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C996B Gigabit Server
NIC
Physical Address. . . . . . . . . : 00-04-76-EA-B5-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.5
DNS Servers . . . . . . . . . . . : 192.168.100.4
192.168.100.208

NETSH FIREWALL SHOW STATE:

Firewall status:
-------------------------------------------------------------------
Profile = Domain
Operational mode = Enable
Exception mode = Enable
Multicast/broadcast response mode = Enable
Notification mode = Enable
Group policy version = None
Remote admin mode = Disable

Ports currently open on all network interfaces:
Port Protocol Version Program

 

[Steven L Umbach]

It shows that the computer is a domain computer that is getting Windows
Firewall configuration probably from Group Policy at the domain level in
that the domain profile is applying settings and it shows the Windows
Firewall is enabled and currently does not allow exceptions for file and
print sharing which is why shares can not be accessed and probably ping is
not allowed which would be if file and print sharing exception was in place.
You can run rsop.msc on that XP Pro computer to see what Group Policy is
managing Windows Firewall settings. If you are a local administrator you can
use gpedit.msc to see local Group Policy and look under computer
configuration/administrative templates/network/network connections/Windows
firewall/domain profile though if a domain level Group Policy [as shown by
rsop.msc] is enforcing those settings you can not override then in local
Group Policy. --- Steve

 

[Luchito]

I ran gpedit.msc like you said and accessed the Windows Firewall Domain
Profile. However, none of the settings were configured. The "State" of
all these settings came up as "Not Configured". Do these need to be
configured?

 

[Steven L Umbach]

It sounds like a domain level Group Policy may be implementing the firewall
settings - not local Group Policy. Try running rsop.msc on it to check to
see if those settings are configured via Group Policy and what GPO is
applying the settings. It is also possible that the registry had been
modified without the use of Group Policy. The link below explains what
registry settings to check if you are sure that no Group Policy is applying
the settings. --- Steve

http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/depfwset/wfsp2ngp.mspx

The registry keys to add to disable Windows Firewall for both the domain and
standard profiles are the following:

. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall
\DomainProfile \EnableFirewall=0 (DWORD data type)

. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall
\StandardProfile \EnableFirewall=0 (DWORD data type)

 

[Luchito]

Despite completely disabling the windows firewall I still cannot ping
my system and my shares are still inaccessible from other systems.
Currently there aren't any GPOs being applied so I'm not really sure
what else to do.

 

[Steven L Umbach]

Dang! Does running netsh firewall show state show that the firewall is
disabled? If so try booting into Safe Mode with networking again to see if
that works which should disable the ipsec service if there is an ipsec
policy assigned to the computer that could also block access or other
startup service doing the same. If none of that works I would try resetting
tcp/ip as described in the KB article below. If that does not work I would
remove the computer from the domain and try again after using netsh firewall
show state show to verify that the firewall is disabled. If still a no go I
would probably try replacing the network adapter. I also assume the
computers you are trying to ping it from are on the same network with the
same subnet mask and otherwise an incorrect default gateway on one of the
computers involved can cause a problem like you describe. If you have a
crossover cable available try connecting another computer directly to your
computer with that crossover cable plugged into the network adapter of both
computers to act as a simple network. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;299357