Member Avatar for willbill

Hello, i recently formatted my HDD and then reinstalled Xp.

Theres been no serious problems, except i cant seem to run a internet connection on it.

I have a belkin 54g, and thats all plugged in via ethernet, and that allows the two other pcs in the house to connect to the internet, all fine, infact, im writing this on a laptop which is connected wirelessly to my belkin as we speak.

So, anyway, i want to make it work with Xp. All the lights are on, all green but Xp wont let me go on the web!!

So, i have to make a new internet connection, anyway run me through this, ive tried it before and nothing happens.
The belkin manual aint exactly the best as i cant go to the ultities page because i havent got a connection, i can however do it on my 2 computers fine!

So, any help?

  • 1 Contributor
  • 2 Replies
  • 105 Views
  • 14 Hours Discussion Span
  • Latest Post Latest Post by willbill

Dani AI

Generated

Scenario recap: reinstalled Windows XP on one machine, the Belkin 54g and the rest of the network worked fine, but the newly-reset XP box could not access the web even though the router lights were green. Below is a compact, practical checklist that fixes this exact class of problem.

Check basics and driver state. Confirm the Ethernet adapter appears in Device Manager with no warning icon and that the cable links to the router. A green LED does not guarantee a working driver. In Network Connections, right-click the LAN adapter and choose Repair; if that fails, disable then re-enable the adapter, or uninstall the adapter in Device Manager and reboot so XP reinstalls it. If a driver is missing, copy the vendor driver from another PC.

Gather IP info and interpret it. From a command prompt run:

ipconfig /all
ipconfig /release
ipconfig /renew
ipconfig /flushdns

A 169.254.x.x address means DHCP failed. If the adapter has no IP, check that Internet Protocol (TCP/IP) v4 is installed and set to obtain IP and DNS automatically (unless a static address is intended).

Isolate connectivity and DNS. From the command prompt:

ping <gateway-ip>
ping 8.8.8.8
nslookup www.google.com

If ping to the gateway fails, the problem is local (cable, port, NIC). If gateway responds but 8.8.8.8 does not, the router/modem upstream is the issue. If numeric pings work but nslookup fails, it’s a DNS problem—try setting DNS to 8.8.8.8 temporarily.

Repair networking stack and check services. Run:

netsh int ip reset
netsh winsock reset

Reboot after these. Verify the DHCP Client service is running. Check for proxy settings in Internet Options (Connections → LAN Settings) and temporarily disable third‑party firewalls/antivirus.

If DHCP is failing, a temporary static IP in the router subnet can confirm basic connectivity:

IP: 192.168.1.50
Mask: 255.255.255.0
Gateway: 192.168.1.1
DNS: 8.8.8.8

Common root causes: missing/incorrect NIC driver, DHCP client disabled, proxy/firewall blocking, or corrupted TCP/IP/Winsock. Collecting ipconfig /all and the ping/nslookup results generally reveals which of these it is.

Member Avatar for willbill

Anyone? Please...

Member Avatar for willbill

Well, i figured it out myself. :)

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.