I have replaced a Windows XP PC (SP2) on my office network with an new pc running Windows XP SP3.

The network is connected via a NetGear 16 port GB Switch with each pc assigned a static IP address.

The new PC connects to all my printers , the internet and a Mac on the network (tested by pinging all the equipment) but will not connect to the only other PC on the network which previously was not a problem.

To make matters more interesting the other PC on the network, will ping all the peripherals and the mac but does not ping the new pc.

Does anyone have any suggestions as to how to resolve this issue?

Regards,


Mike

Dani AI

Generated

Good points from (firewall) and (subnet). With saying the new XP/SP3 box talks to printers, the Mac and the Internet, while the other XP also talks to everything except the new box, this looks like a host‑specific block or an addressing/adapter mismatch rather than a switch or cabling fault.

Start with basic addressing and L2 checks. Compare both machines' outputs from ipconfig /all and confirm IP, subnet mask and default gateway are in the same network (for a /24 the first three octets should match). From each host ping the other by IP and then check the ARP table to see if a MAC address appears. Also disable any extra adapters (wireless, VPN, virtual NICs) while testing in case traffic is returning on the wrong interface.

ipconfig /all
ping <other-PC-IP>
arp -a
nbtstat -A <other-PC-IP>

Rule out host firewalls and security suites next. Temporarily disable Windows Firewall and any third‑party firewall/AV on both machines, enable File and Printer Sharing and (under Windows Firewall Advanced → ICMP settings) allow incoming echo requests. If pings begin to work with firewalls off, re-enable protection and add exceptions for File and Printer Sharing or explicitly allow ICMP echo as needed. Always restore protection after testing.

If the issue remains, check NIC drivers and Windows event logs, try swapping switch ports or a direct cable between the two PCs to isolate the switch, and consider a packet capture (Wireshark) on the target machine to see whether ICMP arrives and whether replies leave. Useful diagnostics for deeper analysis: the outputs of ipconfig /all, arp -a, route print, plus raw ping results by IP and by hostname, and a note whether firewalls were disabled during tests.

Recommended Answers

All 2 Replies

Could it be a firewall issue?

Here is a thread about problems with SP3's firewall if your interested.

AJZ

Sounds like they may be on a different subnet, possibly one on the LAN and one on the WLAN? Are the IP's the same besides the last octet? i.e 192.168.1.xxx?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.