Hey guys I'm using 2 computers a desktop computer and a wireless laptop. The
wireless laptop can connect to the internet while the desktop computer isn't
connected and it has "limited or no connectivity". The desktop computer
connects to the router which connects to the modem while the laptop is
directly connected to the router (wireless).

I tried doing:

1) netsh winsock reset
2) netsh int ip reset reset.log
3) netsh winsock reset catalog
4) winsockxpfix software
5) unplug the modem and the router
6) I have checked the services

But stil no luck.. :((
The os of my desktop computer is winxp/sp3
When i try to ipconfig/renew it says that "unable to contact your dhcp server.Request timed out.

This is my ipconfig/all:

C:\Documents and Settings\ram>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : KENNETH
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA PCI 10/100Mb Fast Ethernet Adapt
er
Physical Address. . . . . . . . . : 00-0D-87-32-3B-EE
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . :
Subnet Mask . . . . . . . . . . . :
IP Address. . . . . . . . . . . . : fe80::20d:87ff:fe32:3bee%4
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

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. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : A9-FE-F9-60
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Dani AI

Generated

A quick diagnosis and a focused checklist to narrow the cause.

The desktop is falling back to a self‑assigned address because it never gets a DHCP lease. Since already ran software-level resets and suggested copying the laptop’s working settings, the next steps should isolate physical/link issues and the router’s DHCP service before redoing OS fixes.

Try these layer‑1 and router checks first: swap the Ethernet cable and use a different LAN port on the router; then plug the laptop into that same cable/port to confirm the cable/port actually hands out an address. From the working laptop, log into the router admin page and confirm the DHCP server is enabled, look at the DHCP lease table for the desktop NIC’s MAC, check for MAC filtering or address reservations, and verify the DHCP pool isn’t exhausted. Router logs will show whether DISCOVER/REQUEST packets arrive.

On the PC side verify specific services and drivers: open Services and ensure the DHCP Client service is set to Automatic and running; temporarily disable any third‑party firewall/AV and remove virtual adapters (VMware/VirtualBox) that can intercept traffic; check Device Manager and reinstall or update the Ethernet driver. If available, test with a different NIC (USB‑Ethernet) or boot a known‑good live OS to rule out Windows/driver faults.

Useful quick tests (run from the desktop to interpret results):

ping <router-ip>
arp -a
nbtstat -n
route print

If a manual static IP in the router’s subnet (choose an unused host number outside the DHCP pool) allows pinging the gateway, the DHCP service or router config is the likely culprit. If a static IP still cannot reach the gateway, the problem points to cable, port, switch, or NIC hardware/driver. These focused checks will locate the fault without repeating the resets already tried.

Recommended Answers

All 3 Replies

have you tried: ipconfig /renew

Of course I tried it. It is stated above that when I ipconfig/renew, it states the error message "Unable to contact your DHCP server. Request timed out"

get the settings from your laptop
then try to manually key in all the ip configuation to your desktop computer check it it can connect to internet. :)

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.