Member Avatar for ip2op01

I have a PC with on-board nforce Ethernet controller and a Acer 4736 laptop with Atheros Ethernet.

I have connected my computer and laptop via cross cable
Both systems has win xp sp2 and workgroup as 'WORKGROUP'.
And Firewall is Turned off on both machines.

Computer's ip -
Laptop's ip -

subnet mask for both -

When i connected both machines directly via cross cable (Cable is perfect) they are connected in LAN and the icon is shown on taskbar but when i ping 'Request timed out' message is shown.

I have seen the status of the connection which shows some KB of data is sent but Received section shows Zero.

How do i solve this problem.

Please Help me.

Thanks.

  • 3 Contributors
  • 2 Replies
  • 121 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by mjdodd

Dani AI

Generated

The symptoms reported by — a Windows XP link that shows "connected" while pings time out and the interface reports bytes sent but none received — point to a small set of common causes: missing or corrupted TCP/IP binding, driver/hardware or duplex/cable mismatch, or a third‑party network filter/firewall. 's suggestion to try the Network Setup Wizard is a reasonable quick check; 's idea of changing the private subnet can help if there is an IP conflict with another device, but it rarely fixes a one‑way receive problem on a direct cable link.

Prioritized checklist (run these locally on both machines):

  • Verify the TCP/IP stack and basic reachability:

    ping 127.0.0.1
ipconfig /all

    Successful loopback ping means the stack is present. If ipconfig /all shows an APIPA address (169.254.x.x) or unexpected configuration, correct the IPv4 settings.

  • Check layer‑2 and ARP after attempting a ping:

    arp -a

    If the peer's MAC never appears in the ARP table, the problem is at layer‑2 (cable/NIC/duplex) rather than IP.

  • Inspect routing/NetBIOS and bindings:

    route print
nbtstat -n

    Confirm no strange static routes and that Microsoft network components (Client for Microsoft Networks / Internet Protocol (TCP/IP)) are bound in the adapter properties.

Hardware and driver checks (common culprits)

  • Confirm link lights on both NICs. Try a different cable or use a simple switch/hub instead of direct cable. Some NICs require a cross‑over cable unless Auto‑MDI/MDIX is supported.
  • Force identical speed/duplex on both adapters (e.g., 100Mbps Full) to rule out mismatch.
  • Reinstall or update NIC drivers and disable virtual adapters, VPN clients, ICS or third‑party firewalls/filters.

If stack corruption is suspected, run and reboot:

netsh int ip reset resetlog.txt
netsh winsock reset

If the above still yields zero receive bytes, hardware (cable/NIC) or driver-level filtering is most likely; swapping the physical hardware or testing with a small switch will quickly confirm that.

Recommended Answers

All 2 Replies

Member Avatar for Xlphos

have you tried the network wizard?

Member Avatar for mjdodd

TRY USING HIGHER ip ADDRESSES LIKE &21 AS OFTEN CARDS,ROUTERS AND adsl MODEMS CHOOSE THESE AS STATiC ADDRESSES FOR THEIR OWN USE;
(oops caps lock on!)

m

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.