Wireless connections works ... then doesn't (XP Pro)

Wireless connection to the Access Point is shown as
Wireless Network Connection
Speed: 11.0 mbps
Signal strength: Excellent
Status: little or no connectivity

But no TCP apps can access the network.

When I open the Wireless Network Connection Status window, I see "Limited or
no Connectivity: You might not be able to access the internet or some network
resources. This problem occurred because the network did not assign a
network address to the computer."

Clicking on the Details button shows the IP address as 169.254.74.76. (This
is a self-assigned IP, no?)

When I click the Repair button, I get see "Windows could not finish repairing
the problem because the following action cannot be completed: Connecting to
the wireless network. For assistance, contact the person who manages your
network."

When my friend first arrived here, we tried to connect the laptop to the
network, unsuccessfully. After poking around, I found that the previous
network maven had assigned an IP address manually. I changed this to DHCP
(and entered the WEP key), and voila!, it connected to the 'net. For a half
hour. Then no network connectivity, again.

I've checked the TCP/IP Properties and "Obtain an IP Address Automatically"
is checked.

What can I do to get this computer on the network?

Dell Inspiron 600M (built-in wireless); Windows XP Pro

Thanks,
--
Please, no "Go Google this" replies. I wouldn't
ask a question here if I hadn't done that already.

DaveC
(E-Mail Removed)
This is an invalid return address
Please reply in the news group

An IP address of 169.254.x.x usually means you have a
misconfiguration. It can be something as simple as changing the
channel on your wireless router/AP, however, without knowing what make
and model of your wireless router/AP, I suggest you return to the
default settings and see if you can connect. If so, Change the SSID
to one of your choice and make sure you change the SSID settings with
your wireless card's configuration menu. If you can still connect
afterwards, enable encryption. If you can still connect okay, make
other changes that suits your needs. Let us know how it goes. Take
care.


On Wed, 20 Oct 2004 11:57:24 -0700, DaveC <(E-Mail Removed)> wrote:

Wireless connection to the Access Point is shown as
Wireless Network Connection
Speed: 11.0 mbps
Signal strength: Excellent
Status: little or no connectivity

But no TCP apps can access the network.

When I open the Wireless Network Connection Status window, I see
"Limited or
no Connectivity: You might not be able to access the internet or some
network
resources. This problem occurred because the network did not assign a
network address to the computer."

Clicking on the Details button shows the IP address as 169.254.74.76.
(This
is a self-assigned IP, no?)

When I click the Repair button, I get see "Windows could not finish
repairing
the problem because the following action cannot be completed:
Connecting to
the wireless network. For assistance, contact the person who manages
your
network."

When my friend first arrived here, we tried to connect the laptop to
the
network, unsuccessfully. After poking around, I found that the
previous
network maven had assigned an IP address manually. I changed this to
DHCP
(and entered the WEP key), and voila!, it connected to the 'net. For a
half
hour. Then no network connectivity, again.

I've checked the TCP/IP Properties and "Obtain an IP Address
Automatically"
is checked.

What can I do to get this computer on the network?

Dell Inspiron 600M (built-in wireless); Windows XP Pro

Thanks,

I've narrowed down the problem to the WEP security. If I configure the
AirPort AP with WEP (either 40 or 128 bit) Windows XP will allow you to enter
the WEP key and says it is connected, but won't give any TCP/IP connectivity
to TCP apps. If I disable WEP, XP is happy.

XP's firewall is disabled, for the time.

Ideas? Solutions?

Thanks,
Dave
--
Please, no "Go Google this" replies. I wouldn't
ask a question here if I hadn't done that already.

DaveC
(E-Mail Removed)
This is an invalid return address
Please reply in the news group

On Thu, 21 Oct 2004 09:12:09 -0700, DaveC wrote
(in article <(E-Mail Removed) et>):

> I've narrowed down the problem to the WEP security. If I configure the
> AirPort AP with WEP (either 40 or 128 bit) Windows XP will allow you to enter

> the WEP key and says it is connected, but won't give any TCP/IP connectivity
> to TCP apps. If I disable WEP, XP is happy.

The baffling part of this mystery is why wireless access worked for a half
hour using 40-bit WEP security, then quit working.
--
Please, no "Go Google this" replies. I wouldn't
ask a question here if I hadn't done that already.

DaveC
(E-Mail Removed)
This is an invalid return address
Please reply in the news group

DaveC wrote:
> On Thu, 21 Oct 2004 09:12:09 -0700, DaveC wrote
> (in article <(E-Mail Removed) et>):
>
>> I've narrowed down the problem to the WEP security. If I configure
>> the AirPort AP with WEP (either 40 or 128 bit) Windows XP will allow
>> you to enter
>
>> the WEP key and says it is connected, but won't give any TCP/IP
>> connectivity to TCP apps. If I disable WEP, XP is happy.
>
> The baffling part of this mystery is why wireless access worked for a
> half hour using 40-bit WEP security, then quit working.

If that's the depth you used, you were probably hacked and infected in less
than a half hour.