Desktop

Ask something
Discussion Locked

Windows2000 PC does not respond to PINGs

0 helpful
9 replies

by willidh

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Windows 2000 PC (call it A) that is not responding to ICMP packets although it can issue PINGs to other machines (e.g. B) and receive positive replies. NetBEUI works fine in both directions (A to B and B to A)

A can see B's MAC address in its ARP cache and B can see A's MAC address.

When B pings A, if the LAN Status window is open on A, you can see the number of Received packets increases with each ICMP packet sent from B but the number of sent packets on A remains static.

I have removed and reinstalled TCP/IP on A as well as the adapter. All other machines on the LAN work fine. The problem is definitely with A. I have tried different network cables and hub ports.

Any ideas gratefully received,

Danny

9 replies

by qballrail

Try removing NetBEUI and installing IPX/SPX. NetBEUI is problematic at best. Also if you are running a software firewall on either or both PC's, that could be blocking your pings. Zone Alarm can be pretty bad that way. Although I use it myself..I recently had a similar issue, but removing NetBEUI all together and installing IPX protocol should help.

Do you have your network on a router?

by willidh

Thanks for the ideas.

I tried removing NetBEUI and installing IPX/SPX - didn't help. I also tried disabling and uninstalling my software firewall - again no change.

Danny

by cg it

Trying to answer this question without more background on your network is difficult. Are you using ISA server on your network? Do you use static routing or allow DHCP? What security settings do you have in place on your W2K pc? Does it allow inboundtraffic? If static routing is your RRAS configured correctly? Is the NAT corrupted? Are you using a 3rd party router as a gateway? Your problem sounds more like a filter is not allowing inbound traffic via TCP IP but allows outbound traffic re "A" (computer in question) can ping out, but other computers can't ping in. There are command line utilities for checking network paths, open and closed ports, port assignments, etc. Click start, click run, type in cmd. At the command prompt type netstat -an -p tcp. This will list all TCP/UDP IP addresses and ports that are on your computer with corresponding status. Once you know your TCP/UDP IP addresses and ports and their status as open or closed, you can configure those routes. Other command line utilities are, route, route print ,ping with the switches, Tracert. Again, without further information as to the network this computer is on, it's hard to tell what the problem is in not accepting inbound traffic other than either the security settings do not allow inbound traffic or there is a firewall and filter not allowing inbound traffic.

by cg it

This is an addendum to my post. You have a firewall in place as at the end of your question you mentioned uninstalling and reinstalling your firewall software. It is my understanding that most firewall software's default upon installation is to denyall inbound traffic (as safety security measure). If you have not configured your firewall software after installation, then that is probably you problem with not receiving inbound traffic. Also...I mentioned a command line utility and when it was posted did not show the proper spacing... the comand line utility netstat. at the command prompt type netstat then space type -an then space type -p then space type tcp hit enter.

by cg it

Addendum. Further, on W2k machines NETBEUI isn't a protocol that is recommended. For Internet and just basic networking, TCP/IP protocol is recommended as it's a routeable protocol. Check your local area connection properties and make sure TCP/IP protocol has been enabled.

by cg it

Ok. the other possiblity is that the security settings for your Windows 2000 pc will not allow access from the network to that machine. To change your security settings for your pc, go to control panel, open administrative tools. Open local securitysettings, expand local security settings in the right pane, expand user rights assignment. The first entry is "access this computer from the network". Double click to open the property sheet. The property sheet should have the following. Everyone, Administrators, backup operators, power users, users. Make sure the boxes for each group are checked for local policy settings. Close all panes and programs. Restart you computer to apply security settings. This should allow others on the network to access your computer. Further, to access certain folders on you computer via the My Network Places link, file sharing on those folders you wish to share must be enabled. Other than this and the above comments, I was unable to reproduce your problem ona test network.

by willidh

Here's some additional information:

Flat network - static IP addresses of 192.168.0.1 and 192.168.0.2. Subnet masks 255.255.255.0 on both boxes. No routers. It all worked fine until a week ago. I have no recollection of making any changes that would cause this to happen. If the firewall isn't installed then there must be something else that is blocking the TCP/IP traffic. I am guessing that something has gone wrong in the registry.

by cg it

Corruption of your registry wouldn't necessarily cause network connection problems as it would cause your computer or programs to not run. You might want to check your TCP/IP filtering via network and dialup connection, local area connection status,local area connection properties, advanced TCP/IP settings, options, TCP/IP filtering. make sure that permit all TCP and UDP filtering has been enabled. If your directly connecting two computers to each other, try rerunning the connection wizard. This should resolve connection problems.

by willidh

Thanks for the ideas.

I have tried configuring the LAN connection to use TCP/IP filtering and permit everything as well as configuring the connection not to use TCP/IP filtering. Neither setting resolves the problem.

The two computers are notdirectly connected. There are actually several computers on the LAN. They can all commmunicate with eachother apart from "A" in my simplified example above.

Thanks,

Danny

This discussion is closed to new replies.