<div>
Try disaling your firewall while you initially connect.<br />
Check the Netgear does not have a list of MAC addresses for access control and if it does, add your MAC address to the list.<br />
Disable and reenable wireless network card and recreate the connection from scratch.<br />

</div>


<div>
tried that and no joy and no mac filtering enabled.<br />
<br />

</div>


<div>
its a WAG102 and i have the latest firmware installed and its local ip is on my lan range already.<br />

</div>


<div>
Hello,<br />
<br />
Do one thing open my network places - wireless connection - check there number of connections is increase. So please delete the connections which not required. Assign a static IP address with DNS.<br />
Also check the firewall settings.Restart your windows &amp;&nbsp;check.<br />
<br />
Regards,<br />
Tushar Kaskhedikar<br />
&nbsp; &nbsp;
</div>


<div>
sorry i dont follow &quot;check there number of connections is increase&quot;
</div>


<div>
I dont mean the local IP of the device. &nbsp;I mean because the client machine can't get an IP, it looks to APIPA for an alternate IP address, which is by default 169.254.x. , you can change this so it has an IP on the LAN for this error.<br />
<br />
its a work around, but it works.<br />
<br />
<a href="http://support.microsoft.com/kb/220874" rel="ugc">http://support.microsoft.com/kb/220874</a><br />
<br />
If DHCP fails, this works ( as a workaround)
</div>


<div>
No need to set a static IP, as when you move the machine you are going to be stuffed. &nbsp;just change the APIPA address as above.
</div>


<div>
Hi, I am sure I have had this problem in the past, you could try going into the properties of &nbsp;wireless network connections,wireless networks and tick the box to 'Use windows to configure my wireless network connections'
</div>


<div>
tried that charlie<br />
<br />
on the APIPA where do i change from 169........
</div>


<div>
Hello,<br />
<br />
Go to the windows wireless connection manager &amp;&nbsp;check the number of connections.<br />
<br />
Regards,<br />
Tushar Kaskhedikar
</div>


<div>
Hello,<br />
<br />
Right click on wireless connection - view available wireless connections &amp;&nbsp;then check how many connections is there?<br />
<br />
Regards,<br />
Tushar Kaskhedikar &nbsp; 
</div>


<div>
If DHCP is enabled on your computer, and DHCP is disabled on the router, you will never acquire authentication that way. What you need to do is ask your network administrator if DHCP is enabled on the router, and if it is and your are not able to get anything from DHCP on your laptop, try this:<br />
<br />
Open the wireless network connections in your system tray.<br />
Go to advanced options,<br />
click on the network (the one that you are using at work) and then click properties.<br />
go to the security tab.<br />
disable &quot;smart-card authentication&quot;. (Just uncheck the whole option, you need regular authentication).<br />
Disable the network card, and then re-enable it. It should now work.
</div>


<div>
I had a similar problem.<br />
i can tell you that dell someimes has some problem, i've got an xps m1330, i've called dell several times and they changes my motherboard 3 times. at the third all is working fine :)
</div>


<div>
The others notebooks connecting are using DHCP?... maybe they are not - you can check one of the to see if is mentioned a DHCP server in the network status (or use IPCONFIG /ALL)<br />
At work you are using a domain to log on - if YES - this could be a problem - if you are not authenticated agains a domain you will not reecive a DHCP address because server will not recognise you.
</div>


<div>
i've seen this a lot with WEP encryption, changing it to WPA fixed it in most cases... <br />
<br />
i think the previous comments about firmware (and the not said update the wireless driver) are good... firmware for the netgear, firmware for your wireless card, firmware for your bios.<br />
<br />
you could also let your wireless card driver handle the wireless networks, most will let you specify an ip address to use per profile.<br />
<br />
the wireless network at home, and at work, they don't have the same wireless network name, like 'netgear' do they? &nbsp;if so change one<br />

</div>


<div>
if all else fails, we could write two batch files you can put on your desktop icons... one that sets the laptop to dynamic (for everywhere else) and one that sets all the static info for work... so just a double click and you're good<br />

</div>


<div>
have you matched the encryption scheme on your laptop and access point.?<br />
have you tried by assigning the static IP of the same rage what you have in your office.?
</div>


<div>
ok first off we have dhcp server on the network<br />
all other laptops work fine and are dhcp<br />
we use WPA-PAk with TKIP<br />
<br />

</div>


<div>
static address works fine<br />
<br />
if i change encryption does that mean everyone else will be disonnected and then they will all need resetup?<br />
<br />
cheers<br />

</div>


<div>
Open the wireless network connections in your system tray.<br />
Go to advanced options,<br />
click on the network (the one that you are using at work) and then click properties.<br />
go to the security tab.<br />
disable &quot;smart-card authentication&quot;. (Just uncheck the whole option, you need regular authentication).<br />
Disable the network card, and then re-enable it. It should now work.
</div>


<div>
did you follow the APIPA instructions as per my link?<br />
<br />
As I said this is a workaround...<br />
<br />
Sayed's option looks good.
</div>


<div>
Well kingcastle, in this case my gues may be correct (90%) - At work you are on a active directory domain and your PC is not joined into the domain (or was outside domain for few weeks and lost its connection wit the domain).<br />
If your PC was working &quot;once upon &nbsp;time&quot; at work you have to rejoion the domain (put your computer into a workgroup then back to the domain - you will need an account that has the right to join computers to the domain, or ask your administrator how you can do this).<br />
If you are new to that work network - you have to ask your admin how you could join to that domain.
</div>


<div>
smart card option gaeyed out
</div>


<div>
Try this:<br />
<br />
Control panel --&gt; Network connections --&gt; Wireless card (Right click properties). -- Scroll down to TCP/IP --&gt; click &quot;Use the follwing Ip address:&quot; --&gt; Fill in the IP Address (range that the DHCP usually assigns, ie, if your colleagues are 192.168.0.100, 102, 103, etc. try something like 118; Subnet mask 255.255.0.0, gateway should be the routers IP, ie: 192.168.0.1 and the preferred DNS should be the same. --&gt; Disable the network card, re-enable the network card.<br />
<br />
Good luck
</div>


<div>
What is your DHCP server? <br />
and what is you DHCP lease time? <br />
<br />
Here's a fun project for you.<br />
Download and install Wireshark (<a href="http://www.wireshark.org" rel="ugc">www.wireshark.org</a>) on your computer.<br />
Start capture BEFORE you connect to wireless network at work.<br />
Let it capture until you're disconnected - or several minutes have gone by without you connecting.<br />
<br />
Then stop capture and sort by protocol and look for DHCP packets.<br />
Here's how DHCP works.<br />
<br />
Laptop connects to wireless and sends a DHCP DISCOVER broadcast packet looking for DHCP Server<br />
<br />
DHCP Server responds with a DHCP OFFER packet, offering an IP-configuration<br />
<br />
Laptop gets the offer, and responds with a DHCP REQUEST packet, claiming the offered address<br />
<br />
The server finally gives an DHCP ACK packet to acknowledge the address lease.<br />
<br />
If DHCP server is a Windows server, install wireshark on that server an look for the same sequence there.<br />
<br />
moreover, make sure you've deleted the wireless profile and reconnected to confirm PSK is correct. 
</div>


<div>
Dhcp is windows 2008 thought that maybe re adding was a good point but if I plug in LAN cable same dhcp server give &nbsp;me ip on LAN card
</div>


<div>
make sure you are also using the same wifi type, like G/N/A wirless G or N or A etcc...
</div>


<div>
We use g but I can't see anywhere to specify that
</div>


<div>
as long as you see the wireless connection; its the right type. Please refer to my previous post
</div>


<div>
Try download the latest wireless card driver from Dell; I doubt it's causing by incompatibility between Dell wireless card and Netgear access point.
</div>


<div>
<div class="content wysiwyg-content">
Hi<br />
<br />
I have a Dell Vostro 1510 which connects to my wireless network at home no problems. When im in work i get connected to our Netgear WAG102 ok but it nevers gives me an ip address, it just sits there saying acquiring network address and never gets one.<br />
<br />
There are other laptops connceting ok with no problem.<br />
<br />
I have googled this and found various stuff but none fixed the problem<br />
<br />
I am running Windows XP SP3.<br />
<br />
cheers<br />

</div>
</div>


Hi

I have a Dell Vostro 1510 which connects to my wireless network at home no problems. When im in work i get connected to our Netgear WAG102 ok but it nevers gives me an ip address, it just sits there saying acquiring network address and never gets one.

There are other laptops connceting ok with no problem.

I have googled this and found various stuff but none fixed the problem

I am running Windows XP SP3.

cheers


Dell Laptop and Wireless AP

Wireless networking is anything related to the transfer of data between two (or more) devices without the use of a physical connection, ranging from getting advice on a new Bluetooth headset to configuring sophisticated enterprise level networks.

Wireless Networking

Microsoft Windows XP is the sixth release of the NT series of operating systems, and was the first to be marketed in a variety of editions: XP Home and XP Professional, designed for business and power users. The advanced features in XP Professional are generally disabled in Home Edition, but are there and can be activated. There were two 64-bit editions, an embedded edition and a tablet edition.