Home > Ask the Networking Experts > Wireless networking Questions & Answers > Why can't our wireless NIC get an IP address?
Ask The Networking Expert: Questions & Answers
EMAIL THIS

Why can't our wireless NIC get an IP address?

Lisa Phifer EXPERT RESPONSE FROM: Lisa Phifer

Pose a Question
Other Networking Categories
Meet all Networking Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 27 March 2006
Have you ever had a problem with wireless NIC not being able to get an IP address from an access point that it can see and detect a signal from?


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



RELATED CONTENT
IP Networking
What is the definition of ATM (Asynchronous Transfer Mode)?
Do I have to disable DHCP on my router to create a DHCP server?
Windows Server 2008 IP routing configuration: Static and dynamic RIPv2
What is IP?
Connect your LAN to the Internet using static or dynamic NAT
Using tracert and TTL to troubleshoot network connectivity problems
Test your TCP/IP protocol stack to troubleshoot network connectivity
IP addressing and subnetting explained
Checking IP configuration to troubleshoot Windows network connectivity
Does IPv6 abandon TCP/IP fragmentation?

Troubleshooting Wireless Networks
Meru reinvents wireless LAN troubleshooting and management
APs drop connection in WLAN configured as a wireless mesh network
How to plan for 802.11n wireless LAN upgrades
Vendors strive to automate wireless LAN troubleshooting and management
Fluke gets WLAN design, management, security cred with AirMagnet
Wi-Fi RTLS for WLAN management, location-based security, asset tracking
How radio frequency (RF) of microwaves alter wireless signal strength
Distributed antenna systems and WLAN: A network management burden
Wireless LAN management platforms key differentiator for WLAN vendors
How is wireless access point (AP) coverage affected by frequency?
Troubleshooting Wireless Networks Research

Wireless networking
APs drop connection in WLAN configured as a wireless mesh network
How does Wi-Fi ad-hoc mode react when 802.11n and legacy peers are present?
Can wireless adapters operate as client access points to make SoftAPs?
Will using a VPN protect me against fake wireless hotspots?
WLAN QoS and SLA monitoring with 7/24 Wireless Quality Assurance costs
How can I hide my WLAN's SSID in an Aruba AP-61?
How radio frequency (RF) of microwaves alter wireless signal strength
Stolen laptop recovery using remote access and wireless network SSIDs
How is wireless access point (AP) coverage affected by frequency?
Wireless AP SSID and channel configuration for a distribution network

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
32-bit IP addressing  (SearchNetworking.com)
fixed-length subnet mask  (SearchNetworking.com)
GARP (Generic Attribute Registration Protocol)  (SearchNetworking.com)
route aggregation  (SearchNetworking.com)
route summarization  (SearchNetworking.com)
routing table  (SearchNetworking.com)
subnet  (SearchNetworking.com)
subnet mask  (SearchNetworking.com)
variable-length subnet mask  (SearchNetworking.com)
wildcard mask  (SearchNetworking.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


Wireless association followed by DHCP failure is not uncommon. The wireless association establishes the data link. Once associated, the station can transmit and receive data frames. At that point, most stations send a DHCP request: a UDP packet from port 67 to port 68. If a DHCP server is reachable on the LAN, it evaluates the request and responds -- usually by leasing an IP address to the requesting station. So what can go wrong?

First, the station can fail to associate with the AP. Even when signal is strong, the AP can reject the station's associate or authenticate requests. For example, it may be too busy, or there may be a mismatch in supported data rates or security parameters (e.g., the station may not have the right WEP key.) Look for a mismatch in capabilities and security settings between your wireless NIC and AP, and use your AP's log to verify that an association IS being established.

Second, a station that associates may still get disconnected by the AP. For example, the AP may be configured with a MAC Access Control List that does not include the station's address. Or the stations may fail WPA-PSK or WPA (802.1X) authentication. Using WPA-PSK, a station that does not present the right Pre-Shared Key will appear to associate, but never get an IP address. Using WPA (802.1X), a station may appear to associate for perhaps a minute, then get disconnected when the 802.1X exchange fails. Carefully watch the station's connection status and double-check authentication settings. If using Windows XP SP2, enable the Wzctrace.log using the command "netsh ras set tracing."

Third, a station that's really connected to an AP can still be unable to reach a DHCP server. Wireless routers often have built-in DHCP servers, but that service may be turned off. Wireless APs usually require a DHCP server somewhere upstream from the AP's Ethernet connection. Verify that a DHCP server exists on your LAN (or VLAN) and can be reached from your AP. It is also possible (but not very likely) that DHCP is being blocked by a personal firewall on the wireless station, or by IP filters on the AP. If you suspect a DHCP problem, watch IP packets using Ethereal, both on the station itself and somewhere on the wired LAN. On Windows, use "ipconfig /release" and "ipconfig /renew" commands to repeat DHCP while you're watching.

Finally, the DHCP server must be willing to lease an IP address to the station. We usually take this step for granted, but if you exhaust other possibilities, then examine logs on your DHCP server to verify that the station's requests are being received, and that an address is being assigned. For example, an unusually busy DHCP server may temporarily reject requests when its IP address block is exhausted.

The most common culprits are the first and second above. In particular, if your station is running Windows XP SP2 and has a connection that is enabled/active, but reports limited or no connectivity, then you are probably stuck on problem #2.




Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Expert networking advice and tips for IT professionals
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2000 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts