Wired LAN won't connect but wireless works

Dell Latitude e6500 notebook - customiza...
April 5, 2010 at 17:44:36
Specs: Windows XP, sp 3, Intel Core2 Duo CPU/ 2.98 GB RAM
When I connect my ethernet cable, it will say "acquiring address" then clicks back to "a network cable is unplugged". My wireless connects fine.

I am using a Lynksys WRT54G wireless G broadband router. All my settings are marked to automatically determine address except for the alternate setting is set to a specific address (changing to automatic private IP address doesn't help). I have this problem with my work network as well.

I'm using an "Intel(R) 82567LM Gigabit Network Connection" ethernet card.

I've searched and searched for a solution but can't find one. Any help would be immensely appreciated.

See More: Wired LAN wont connect but wireless works

Report •

April 5, 2010 at 18:03:56
remove the alternate addy ip.

Clearly what ever you are doing wrong is being repeated at both home and work.

find that commonality and don't repeat it.

The lan interface is enabled right?

Report •

April 5, 2010 at 18:36:12
I changed the alternate address to use with no change in behavior. The fact that it won't work on the work network either tells me it is something in this computers settings but I can't figure out what.

Further info that I don't know if it will be helpful or not: Under the Local Area Connections properties there are 3 listings: File and Printer Sharing for Microsoft Networking, QoS Packet Scheduler and TCP/IP internet protocol.


Report •

April 5, 2010 at 20:01:29
where is the microsoft client [client for microsoft networks]? You need that.

tcp/ip set to automatically obtain ip address?

Report •

Related Solutions

April 5, 2010 at 20:12:49
There was no client for microsoft windows. I have added that client but it continues with the same problem.

The TCP/IP is set to automatically obtain IP address.

Report •

April 6, 2010 at 12:00:12
OK after a reboot do a ipconfig /all and post the results for review

Report •

April 6, 2010 at 12:29:56
This time, when I connected the LAN cable, it actually connected rather than alternating between acquiring and unplugged but it says limited or no connectivity.

the ipconfig/all settings are:
Windows IP Configuration
primary DNS suffix:
Node type: Hybrid
IP routing Enabled: NO
WINS proxy enabled: NO
DNS suffix search list: ph.cox.net

Ethernet adapter wireless network connection:
Connection-specific DNS suffix: ph.cox.net
DHCP Enabled: Yes
Autoconfig. enabled: Yes
IP address:
Subnet mask:
Default gateway
DHCP server:
DNS servers:

Ethernet adapter Local Area Connection:
Connection-specific DNS suffix: [blank]
Physical address 00-21-70-F3-4B-7D
DHCP Enabled: Yes
Autoconfig enabled: Yes
Autoconfig IP Address:
Subnet mask:
Default gateway: [blank]

Thanks for your help. I await your next suggestions.

Report •

April 6, 2010 at 13:24:07
disable the wireless interface by right mouse click on in in Lan Connections and choose disable.

Is this a known good patch cable? ie you have used it successfully elsewhere.

Appears the nic and tcp/ip properties are good. After disabling the wireless interface and rebooting do a ping to test that tcp/ip is working on that nic.

Report •

April 6, 2010 at 13:35:14
I am able to ping and 4 of 4 packets go through. The cable is good (used elsewhere successfully).

Interestingly, now it is back to alternating acquiring/unplugged again. I'm stumped.

Report •

April 6, 2010 at 16:09:53
do a direct connect from your internet modem to this pc with the cable you are using now. This is to test if its the router or the pc that is the problem.

Report •

April 7, 2010 at 19:59:38
It's working! Thanks for all your recommendations and assistance in trouble shooting this. It turns out my motherboard was bad. It was replaced and now it connects just fine. I had the warranty folks come directly look at it and they figured out the bad board.

Sorry to put you through your paces on trying to solve this one. I really appreciate all your help.

Report •

April 7, 2010 at 20:33:27
Thanks for posting back.
Glad it worked out for you!

Report •

Ask Question