Unsolved

This post is more than 5 years old

2 Intern

 • 

139 Posts

13928

March 29th, 2004 03:00

DHCP Problem....IP address from network

I just did a clean install of xp pro on my 8600 and now I'm having a problem grabbing an IP address from my network. I go into CMD and try to release and renew it but no luck. The IP address that I get is 169.254.202.80...which is far off the normal 192.168.x.x that I should be getting. I've tried restarting several times and no luck. I've tried the resetting of the IP log file (netsh int ip reset dellip.txt) but no luck either. It worked fine before I did the clean install.

I've contacted Dell support but it takes time for them to respond, so if anyone can help me out I'd really appreciate your help. Thanks in advance.

3.1K Posts

March 29th, 2004 12:00

Baldie,

Thank you for using the Dell Community Forum.

Please try the following:

  1. Reload the device drivers with a current copy obtained from the Downloads tab (above). 
  2. See if you can ping the loopback address: 127.0.0.1
  3. Check to make sure that the hardware is functioning properly.  Look in the Device Manager for any marks, a yellow exclamation point or red X. 

2 Intern

 • 

139 Posts

March 29th, 2004 13:00

Will I be reloading all the device drivers or only the one for my wireless card? I sure hope this works.

Dell tech support finally emailed me back but they told me to contact my service provider.

2 Intern

 • 

139 Posts

March 29th, 2004 14:00

I will reload the drivers this evening and see if that works out. I'll let you know if that was the case.

88 Posts

March 29th, 2004 14:00

Well Dell Tech Support is completely wrong in this case....it is not your ISP...

I have the same problem frequently with a Linksys USB wireless adapter in windowsXP on another Desktop of mine.

I have had that problem a couple of times(literally) with the Tm1300 in my I600M.

the main reason it happens is that Windows can't reload them for some reason or another...I think it is because the Drivers that they provided you have some flaw in them that prevents Windows from loading them properly on startup...

37 Posts

March 30th, 2004 00:00

I just started seeing the same problem with my Inspiron 8100 with the Actiontec  V2? Mini PC unit.  It was working fine until 3 days ago and then started refusing to get a DHCP assigned IP addres from the network.  Tried to reload the drivers (device manaer says it is a Intel 8255xx based ethernet card) but I can't find the drivers for the actiontec.

 

The card works. I have verified that by putting it on my home network behind a Nat capable router and it worked fine with the 169.254 address. BUT it will not work at work as it needs to pick up a DHCP address and it will not.

4 Posts

March 30th, 2004 00:00

Er... Actually, it demonstrates that you're not finding a DHCP server. You might be finding the network, or you might not. Same checking steps.

4 Posts

March 30th, 2004 00:00

Here's the deal:

The 192.168.x.x address is part of a reserved set of IP addresses that are private. They're used all over the place because they permit non-public networks to have addresses that they know won't be used elsewhere, and they preserve the number of public addresses needed for the Internet to run. (They're in short supply, believe it or not.) Most of your cable or dsl routers will use addresses in this particular range for their DHCP services, if configured.

The 169.254.x.x addresses are also a set of private addresses. But these are used by a variety of systems as defaults for when the system can't find another address (i.e. via DHCP). So the fact that you're getting an address in this range demonstrates that your machine isn't finding the network. This could be for a variety of reasons:

  1. The network card (built-in or otherwise) is broken.
  2. The driver is wrong.
  3. The cable is bad.
  4. The cable is a crossover, used for interconnecting two network devices (i.e. two hubs)
  5. There's interference on the wire.
  6. There's a problem at the endpoint device (i.e. the router isn't working right)
  7. There's no DHCP server.

Those ought to hold you for now. So what you have to do is try to determine which of those is the problem, and then fix it. You do this by narrowing it down. For example, switch cables with a known good one. Check your router to make sure DHCP is enabled. Things like that.

Hope this helps! Good luck!!

d0ughb0y

2 Intern

 • 

7.3K Posts

March 30th, 2004 01:00

Use the link in my sig area below to get the best driver for the Intel 8255x chipset.

2 Intern

 • 

139 Posts

March 30th, 2004 01:00

I reinstalled the driver for my intel 2100 wireless card, the chipset, and broadcom ethernet controller but still I cannot retrieve an IP from my network. I double checked my router and it is enabled for DHCP. This is a wireless connection so no cables are involved. I can't think of anything else. My router seems to be working because it is giving connection to my wired desktops, it is only my wireless laptop having the problem.

I did do what another person suggested, pinging the loop back address 127.0.0.1 and it was successful.

Any other advice you can give me?

2.6K Posts

March 30th, 2004 01:00

Does the wireless card see the wireless network (i.e. does window popup and say it found a network?)

2 Intern

 • 

139 Posts

March 30th, 2004 01:00

Yes, it detects my network. The window pops up saying wireless network detected and it even says the name of my network. However it refuses to get an IP from my network. Help?

2 Intern

 • 

139 Posts

March 30th, 2004 02:00

I've already put the encryption key into my laptop. I believe my laptop will not detect the network unless the encryption key is inputed.I have inputed the key and it does detect the network but it will not grab an IP.

4 Posts

March 30th, 2004 02:00

Hey - Do you have WEP set up on the router? You can have SSID broadcast turned on (so you'd see the network name), but if you have WEP on, and haven't configured the key on your notebook, you won't be able to connect to the network. Just a thought.

d0ughb0y

2 Intern

 • 

139 Posts

March 30th, 2004 03:00

I tried that but I dont think thats the issue. I think I'm running out of troubleshooting techniques now.

4 Posts

March 30th, 2004 03:00

You're sure? As I mentioned before, if the router is set for SSID broadcast, you'll be able to find the network even with WEP turned on. You should probably try turning WEP off on the router, and on the laptop, just to see if your results differ. If suddenly you CAN connect to the WLAN, you're having WEP configuration issues.

d0ughb0y

No Events found!

Top