Start a Conversation

Unsolved

This post is more than 5 years old

KD

29728

December 11th, 2007 00:00

Dell Latitude D600..Acquiring network address

Hi, I am having an issue with a dell D600 not being able to connect to my wireless router at home. I have 2 other wireless laptops that can connect without issue right away. What happens is it just says acquiring network address forever, but never connects. I tried repairing the connection but that did not fix it. I also tried disabling the internal wireless,and putting a belkin wireless card in the laptop which always works, and it still would not connect. Any thoughts on what i should try?

28K Posts

December 11th, 2007 00:00

To help troubleshoot this problem, go to Start > Run and type cmd then click OK. In the command prompt window that opens, type ipconfig /all then hit the enter key. Write down the output from this command or select it and save it to a txt file, then copy this output into a reply to this message.
 
Do you have encryption enabled?  If so, have you supplied the correct encyption key?
 
Steve

42 Posts

December 11th, 2007 23:00

I am using WPA encryption. this computer was actually just upgraded with some 600m parts (HDD (did not rebuild, and i understand this may cause issues), memory, and dvd burner) as the 600m in question motherboard failed. After changing a few drivers, i got the 600d to work with everything, including the wireless. Then the next day it would not connect, and has not connected since.

Windows IP Configuration

Host Name . . . . . . . . . . . . : DHB0GX41
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 5:

Connection-specific DNS Suffix . : domain_not_set.invalid
Description . . . . . . . . . . . : Dell TrueMobile 1300 WLAN Mini-PCI C
ard
Physical Address. . . . . . . . . : 00-90-4B-63-21-5D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
IP Address. . . . . . . . . . . . : fe80::290:4bff:fe63:215d%4
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 204.60.203.179
68.94.157.1
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

Message Edited by k-dubb on 12-11-2007 07:37 PM

28K Posts

December 12th, 2007 02:00

First, is there a reason you have ipv6 installed?  If not, try removing it and see if you can then connect:
 
 
Steve

42 Posts

December 12th, 2007 23:00

I have uninstalled it, but I still receive the same outcome.

28K Posts

December 12th, 2007 23:00

Run the ipconfig command again and post the results.
 
Steve

42 Posts

December 13th, 2007 00:00

Windows IP Configuration

Host Name . . . . . . . . . . . . : DHB0GX41
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell TrueMobile 1300 WLAN Mini-PCI C
ard
Physical Address. . . . . . . . . : 00-90-4B-63-21-5D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.1.1

28K Posts

December 13th, 2007 01:00

Ok.  You are getting a 0.0.0.0 IP address.   See if the suggestions in the following document help solve this:
 
 
Steve

42 Posts

December 13th, 2007 02:00

Everything checked out, still no go :(...Thanks for helping on this.

28K Posts

December 13th, 2007 02:00

Before this problem started did you do anything different.  For example did you uninstall or install new software.  In particular, did you happen to uninstall any Symantec Product?
 
If you connect this computer to the router by wired ethernet, can you connect?(This is just a troubleshooting step to try and narrow down the problem.  I'm not suggesting this as a solution).
 
Steve

42 Posts

December 14th, 2007 22:00

The only thing i did was like i said, i trasferred the hd from a 600m (loaded with windows and many files) to this 600d. I updated the drivers for the different wireless card. I was then able to connect fine. However, when i turned it on again, it would not connect and has not since. I have tried using a wireless card and get the same results. A wired connection connects fine.

28K Posts

December 14th, 2007 22:00

Any subtle difference in hardware can make a difference.  Since the hard drive had Windows installed with different hardware, this could be the problem.  Try installing the chipset drivers, notebook system software, all the network drivers appropriate to the new hardware.
 
Steve

42 Posts

December 18th, 2007 01:00

Well, all i did was reinstall the driver and it connected right away. I guess the true test will be when i try to connect to another network, and then come back to this one. that is when it seemed to stop working before. Thanks for all your help.
No Events found!

Top