Wireless DHCP doesn't like security

[aleko.petkov]

Hi,

I have a Thinkpad T23, running WinXP SP2, with a TrendNet wireless
card.

The NIC is set to DHCP, and when the network I am connecting to has
low, or no security it connects successfully, and gets an IP address.
But if the security is high enough, I can't get an address. It stays at
the "Acquiring IP address" stage. Cable works fine; this only affects
wireless.

64-bit WEP works (intermittently), but anything higher, and the DHCP
negotiation fails.

I have tried using the Windows configuration, and the TrendNet utility,
and neither one works.

Has anyone else run into something similar? Is this a Windows issue, or
a dodgy NIC, or... I dunno, something else, altogether?

Thanks,

Aleko

 

[Lanwench [MVP - Exchange]]

In

Hi,

I have a Thinkpad T23, running WinXP SP2, with a TrendNet wireless
card.

The NIC is set to DHCP, and when the network I am connecting to has
low, or no security it connects successfully, and gets an IP address.
But if the security is high enough, I can't get an address. It stays
at the "Acquiring IP address" stage. Cable works fine; this only
affects wireless.

64-bit WEP works (intermittently), but anything higher, and the DHCP
negotiation fails.

I have tried using the Windows configuration, and the TrendNet
utility, and neither one works.

Has anyone else run into something similar? Is this a Windows issue,
or a dodgy NIC, or... I dunno, something else, altogether?

Thanks,

Aleko

I'd try a different NIC.
And WPA, not WEP....

 

[Steve Winograd [MVP]]

Hi,

I have a Thinkpad T23, running WinXP SP2, with a TrendNet wireless
card.

The NIC is set to DHCP, and when the network I am connecting to has
low, or no security it connects successfully, and gets an IP address.
But if the security is high enough, I can't get an address. It stays at
the "Acquiring IP address" stage. Cable works fine; this only affects
wireless.

64-bit WEP works (intermittently), but anything higher, and the DHCP
negotiation fails.

I have tried using the Windows configuration, and the TrendNet utility,
and neither one works.

Has anyone else run into something similar? Is this a Windows issue, or
a dodgy NIC, or... I dunno, something else, altogether?

Thanks,

Aleko

Downloading and installing the latest driver/firmware for the wireless
NIC and the latest firmware for the wireless router might help.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Joe Crown]

Try different wireless channels as it might be an interference issue.

Hi,

I have a Thinkpad T23, running WinXP SP2, with a TrendNet wireless
card.

The NIC is set to DHCP, and when the network I am connecting to has
low, or no security it connects successfully, and gets an IP address.
But if the security is high enough, I can't get an address. It stays at
the "Acquiring IP address" stage. Cable works fine; this only affects
wireless.

64-bit WEP works (intermittently), but anything higher, and the DHCP
negotiation fails.

I have tried using the Windows configuration, and the TrendNet utility,
and neither one works.

Has anyone else run into something similar? Is this a Windows issue, or
a dodgy NIC, or... I dunno, something else, altogether?

Thanks,

Aleko

--

Don't pay malware vendors - boycott Sony & Symantec for helping them

Please do not contact me directly or ask me to contact you directly for
assistance.

If your question is worth asking, it's worth posting.

If it’s not worth posting you should have done a search on
http://www.google.com/ http://www.google.com/grphp?hl=en&tab=wg&q= or
http://news.google.com/froogle?hl=en&tab=nf&ned=us&q= before wasting our
time.

If I sound hostile or arrogant you need to read the following before
posting a question "How To Ask Questions The Smart Way" at
(The site I've linked
to just has this article I think people should read before posting a
technical question.)

 

[Malke]

Try different wireless channels as it might be an interference issue.

Fix your sig. You gave the OP this link:


Read it to see the sig conventions.

Malke

 

[Joe Crown]

I see nothing about sig conventions at all in the entire web page. Also
all I've seen on his site about this FAQ is that you should have a
disclaimer that says something about this being something good to read,
but not necessarily the right place to ask a question about the topic
I'm replying to. So my question now is what sig conventions & where.

Fix your sig. You gave the OP this link:


Read it to see the sig conventions.

Malke

--

Don't pay malware vendors - boycott Sony & Symantec for helping them

Please do not contact me directly or ask me to contact you directly for
assistance.

If your question is worth asking, it's worth posting.

If it’s not worth posting you should have done a search on
http://www.google.com/ http://www.google.com/grphp?hl=en&tab=wg&q= or
http://news.google.com/froogle?hl=en&tab=nf&ned=us&q= before wasting our
time.

If I sound hostile or arrogant you need to read the following before
posting a question "How To Ask Questions The Smart Way" at
(The site I've linked
to just has this article I think people should read before posting a
technical question.)