Member Avatar for garyemans

Hi, got a pc from a friend becuase my mobo on-board graphics went. tried to connect to internet which it couldnt.
Local area connection - cable unpluged - so checked cable and tried in laptop from router, which worked, tried straight from the broadband modem itself, worked on laptop not in pc.
Nic light on, which suggests that its working.
tried ipcongfig and i got for ip address and subnet mask.
After trwling the internet for answers tried winsockfix, which does nothing, this is what my ipconfig /all say:

Windows IP Configuration

Host Name . . . . . . . . . . . . : homepc

Primary Dns Suffix . . . . . . . : HOMEPC

Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-50-8D-A6-24-DB

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . :

Subnet Mask . . . . . . . . . . . :

IP Address. . . . . . . . . . . . : ?

Default Gateway . . . . . . . . . :

DHCP Server . . . . . . . . . . . :

DNS Servers . . . . . . . . . . . : ?

?

?

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : ?

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled


Please can anyone help, I am tairing my hair out???

I am running Win xp
512mb ram
abit at7
onboard nic

Gary

  • 2 Contributors
  • 3 Replies
  • 130 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by garyemans

Dani AI

Generated

As pointed out, a clean Device Manager entry can be misleading — Windows may show a working adapter while DHCP negotiation or driver support is failing. The symptom described is normally narrowed to three areas: DHCP/network-side problems, driver/software corruption, or a partial hardware failure that still leaves the link light alive. A short, ordered isolation routine separates those quickly.

Run the built-in network resets and check the adapter state:

ipconfig /release
ipconfig /renew
ipconfig /all
netsh int ip reset c:\ip-reset-log.txt
netsh winsock reset

If DHCP still fails, temporarily set a manual IP inside the router subnet (example: IP 192.168.1.50, Mask 255.255.255.0, Gateway 192.168.1.1, DNS 8.8.8.8). A working static IP points at DHCP/router configuration or access-control problems. If the static IP does not work, the problem is likely on the PC side (driver or hardware).

For the adapter itself, fully remove the device and driver (Device Manager -> Uninstall and choose to delete driver files), reboot, then install the official Realtek package for the correct chipset. In the adapter Advanced properties verify Speed & Duplex is set to Autonegotiate; if problems persist try forcing 100Mbps Full. Temporarily disable large offload/checksum offload options while troubleshooting. Check BIOS settings for the onboard NIC and look in Event Viewer for DHCP or driver errors for clues.

If software fixes fail, confirm hardware by booting a Linux live USB or by swapping in a known-good USB/PCI NIC. That quickly separates OS/driver issues from a failing physical NIC and avoids long trial-and-error.

Recommended Answers

All 3 Replies

Member Avatar for garyemans

Forgot to mention...in device manager nic looks fine no question marks or anything beside nic. I can alson ping 127.0.0.1 but cannot ping my router

Gary

Member Avatar for Bench

Not seeing anything wrong in device manager doesn't necessarily mean you have the correct driver, it just means that windows can't see any problems (This is often the case when windows installs some generic driver from its own database) - have you attempted to install the latest driver from Abit's website? (Making sure all traces of the old drivers are gone before you install the new one)

Edit : You should also check the speed & duplex settings in the NIC's Advanced properties are set to Autonegotiate

Member Avatar for garyemans

tried that and didnt work :( cheers anyways, just bought a wee cheap ethernet pci card and work.woo thanks again

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.