Solved

Wireless adapter won't get IP address

Posted on 2014-01-29
7
1,185 Views
Last Modified: 2016-11-23
Wireless adapter in older Dell D530 won't get an IP address from DHCP server.  Wired connection works fine - gets IP address from DHCP server, gets DNS address, subnet mask, sees gateway.  When I plug in a static IP address for the wireless adapter to use along with subnet mask, gateway, DNS - it starts to work fine.  Why won't it get a dynamic IP address from DHCP server?
0
Comment
Question by:davidorz1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
7 Comments
 
LVL 8

Expert Comment

by:Lee Ingalls
ID: 39818695
Do you have access to the DHCP Server?
Does the DHCP Server have a limited range of IP leases?
Is the static IP in a different range than what the DHCP Server is issuing?
If you can check the DHCP Server to see if all the leases have been issued. Test for orphans by pinging; then delete/expire the lease if no response; then on the DELL D530 try IPCONFIG /releases, IPCONFIG /renew (or reboot).
0
 
LVL 44

Expert Comment

by:Darr247
ID: 39818716
Using Wireshark (I recommend the 'PortableApps' version on a USB stick... it's windows-only and starts up a little slower like that, but you don't have to install it on any windows machine where you want to run it), from any computer on the LAN, to monitor DHCP traffic (with a BOOTP 'view' filter applied) should show all the broadcasts of the entire DHCP process. If everything is being passed on broadcast (you *are* using a standard /24 IP range, right?), then use wireshark to check *from* the machine with the WiFi adapter to verify if it's actually seeing the DHCP offer.
0
 

Author Comment

by:davidorz1
ID: 39818826
DHCP server has many unassigned IP addresses available for assignment.  The static IP address that I plugged in is in a different part of the range than DHCP is using.  I tried ipconfig /release, then /renew.  The wired adapter got a renewed address OK - the wireless adapter, not so much.  It shows 169.254.178.72.  I'm not sure what this address is or where it came from.

I'll look into this Wireshark suggestion.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 44

Expert Comment

by:Darr247
ID: 39819032
169.254.x.x /16 is an address in the APIPA range. Network adapters with TCP bindings set to allow automatic configuration will assign themselves an address in that range if no response from a DHCP server is seen.

What IP range is the DHCP server set to use?  (i.e. its Scope.)

Did you watch the process with Wireshark?

You can trigger a new request by disabling the adapter, then enabling it again. The easiest place to do that is by right-clicking on the adapter in Network Connections (ncpa.cpl).
0
 

Author Comment

by:davidorz1
ID: 39819093
DHCP can assign addresses in the range 192.168.4.69 thru 206.  There are plenty of unassigned addresses available.
Disabling then re-enabling the adapter didn't work - still no addresses for the wireless.

I'm still working with the portable version of Wireshark.  No success in getting that to run yet.  It's a bit of a stretch for me.

Do you thing Winsock might have anything to do with this - or not since the wired connection is working.
0
 

Accepted Solution

by:
davidorz1 earned 0 total points
ID: 39819127
I just went into the DW WLAN Card Utility and told it to let Windows manage the wireless network.  Then rebooted, right clicked on the Windows wireless icon, told it to View Available Wireless Networks, selected the wireless network, plugged in the WPA2 encryption key -- and it took off.  It got an IP address like there was never any problem.  I guess Dell's Wireless WLAN Utility got corrupted.  All's well.  Thanks for your suggestions.
0
 

Author Closing Comment

by:davidorz1
ID: 39832009
I didn't offer a very technical solution and didn't even think about which app was managing the wireless connection when I posted the question, but when the wireless starting working with Windows managing it versus the Dell manager -- case closed.
0

Featured Post

Ready to trade in that old firewall?

Whether you need to trade-up to a shiny new Firebox or just ready to upgrade from whatever appliance you're using now, WatchGuard has the right appliance for you! Find your perfect Firebox today with appliance sizing tool!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Hello All, I have been training on Multicast for a while now and whenever I start the topic , I find out that my friends /  Colleagues mention that they do not know how to test Multicast Joins. As most of the multicast would be video traffic and …
#Citrix #Netscaler #MSSQL #Load Balance
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.
Suggested Courses

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question