Strange wireless connection problem

[Richard in AZ]

A friend has six XP Home Edition computers and a new Windows 7 Premium PC on a wireless home LAN.
The wireless router is setup with WPA-2 Personal security.
He is handicapped and has computers located around the house so that he does not have to move around
allot.
Two are in a basement sewing room for his wife and the new Win7 PC is in his garage workshop.

The XP computers all connect automatically when booting.
But right from the initial setup the Win7 PC has been a problem.
It would reject the WPA-2 security code as not valid. I have confirmed that it was being entered
correctly.
I was updating several of his other PC's, then later I went back to this WIN7 PC and found it was
connected and on the LAN.
But on the next reboot it refused the connection stating "the parameters are not setup correctly"
then in a little while I found it back on the LAN and connecting to the Internet even though I had
not worked on it.

Now then I found that when it reboots, it rejects the security code and will not connect. But if I
went to any of the other XP machines and open Network Neighborhood, the Win7 machine will suddenly
show up and when I go back to this PC it is connected. Now when the user want to use that machine
on the Internet, he boots it and goes to any other computer and just opens Network neighborhood and
it will be connected. Now he takes an XP laptop to the garage with him to challenge the Win7 PC
with Network Neighborhood.

The new Window 7 PC is an Acer desktop, as are several of the XP's, but two of the XP's are
Gateways. Sorry I don't have specs on any of them. But does anyone have any suggestions as how to
bully the new Win7 PC into accepting the LAN security on boot-up without going to another PC to
challenge it on the NETWORK?

 

[Patrick Keenan]

A friend has six XP Home Edition computers and a new Windows 7 Premium PC
on a wireless home LAN.
The wireless router is setup with WPA-2 Personal security.
He is handicapped and has computers located around the house so that he
does not have to move around allot.
Two are in a basement sewing room for his wife and the new Win7 PC is in
his garage workshop.

The XP computers all connect automatically when booting.
But right from the initial setup the Win7 PC has been a problem.
It would reject the WPA-2 security code as not valid. I have confirmed
that it was being entered correctly.
I was updating several of his other PC's, then later I went back to this
WIN7 PC and found it was connected and on the LAN.
But on the next reboot it refused the connection stating "the parameters
are not setup correctly" then in a little while I found it back on the LAN
and connecting to the Internet even though I had not worked on it.

Now then I found that when it reboots, it rejects the security code and
will not connect. But if I went to any of the other XP machines and open
Network Neighborhood, the Win7 machine will suddenly show up and when I go
back to this PC it is connected. Now when the user want to use that
machine on the Internet, he boots it and goes to any other computer and
just opens Network neighborhood and it will be connected. Now he takes an
XP laptop to the garage with him to challenge the Win7 PC with Network
Neighborhood.

The new Window 7 PC is an Acer desktop, as are several of the XP's, but
two of the XP's are Gateways. Sorry I don't have specs on any of them.
But does anyone have any suggestions as how to bully the new Win7 PC into
accepting the LAN security on boot-up without going to another PC to
challenge it on the NETWORK?

Can you try another wireless adapter?

 

[Oldster]

A friend has six XP Home Edition computers and a new Windows 7 Premium PC
on a wireless home LAN.
The wireless router is setup with WPA-2 Personal security.
He is handicapped and has computers located around the house so that he
does not have to move around allot.
Two are in a basement sewing room for his wife and the new Win7 PC is in
his garage workshop.

The XP computers all connect automatically when booting.
But right from the initial setup the Win7 PC has been a problem.
It would reject the WPA-2 security code as not valid. I have confirmed
that it was being entered correctly.
I was updating several of his other PC's, then later I went back to this
WIN7 PC and found it was connected and on the LAN.
But on the next reboot it refused the connection stating "the parameters
are not setup correctly" then in a little while I found it back on the LAN
and connecting to the Internet even though I had not worked on it.

Now then I found that when it reboots, it rejects the security code and
will not connect. But if I went to any of the other XP machines and open
Network Neighborhood, the Win7 machine will suddenly show up and when I go
back to this PC it is connected. Now when the user want to use that
machine on the Internet, he boots it and goes to any other computer and
just opens Network neighborhood and it will be connected. Now he takes an
XP laptop to the garage with him to challenge the Win7 PC with Network
Neighborhood.

The new Window 7 PC is an Acer desktop, as are several of the XP's, but
two of the XP's are Gateways. Sorry I don't have specs on any of them.
But does anyone have any suggestions as how to bully the new Win7 PC into
accepting the LAN security on boot-up without going to another PC to
challenge it on the NETWORK?

Range of valid addresses in the router?
Fixed addresses on the lan card?

 

[Jeff Layman]

(snip)

The new Window 7 PC is an Acer desktop, as are several of the XP's, but
two of the XP's are Gateways. Sorry I don't have specs on any of them.
But does anyone have any suggestions as how to bully the new Win7 PC into
accepting the LAN security on boot-up without going to another PC to
challenge it on the NETWORK?

May be worth checking the router manufacturer's website for a firmware
upgrade.

 

[Rasman99]

A friend has six XP Home Edition computers and a new Windows 7 Premium PC
on a wireless home LAN.
The wireless router is setup with WPA-2 Personal security.
He is handicapped and has computers located around the house so that he
does not have to move around allot.
Two are in a basement sewing room for his wife and the new Win7 PC is in
his garage workshop.

The XP computers all connect automatically when booting.
But right from the initial setup the Win7 PC has been a problem.
It would reject the WPA-2 security code as not valid. I have confirmed
that it was being entered correctly.
I was updating several of his other PC's, then later I went back to this
WIN7 PC and found it was connected and on the LAN.
But on the next reboot it refused the connection stating "the parameters
are not setup correctly" then in a little while I found it back on the LAN
and connecting to the Internet even though I had not worked on it.

Now then I found that when it reboots, it rejects the security code and
will not connect. But if I went to any of the other XP machines and open
Network Neighborhood, the Win7 machine will suddenly show up and when I go
back to this PC it is connected. Now when the user want to use that
machine on the Internet, he boots it and goes to any other computer and
just opens Network neighborhood and it will be connected. Now he takes an
XP laptop to the garage with him to challenge the Win7 PC with Network
Neighborhood.

The new Window 7 PC is an Acer desktop, as are several of the XP's, but
two of the XP's are Gateways. Sorry I don't have specs on any of them.
But does anyone have any suggestions as how to bully the new Win7 PC into
accepting the LAN security on boot-up without going to another PC to
challenge it on the NETWORK?

I had an issue like this.... it turned out to be a firmware upgrade for the
Router (Belkin) needed. The Win 7 machine wouldn't authenticate but
XP/Vista did no problem. The Win7 machine had worked on other WLAN routers
so I knew the individual elements of the solution all worked in isolation.

--

 

[Richard in AZ]

Can you try another wireless adapter?

No he is not interested in this option yet.

 

[Richard in AZ]

Range of valid addresses in the router?
Fixed addresses on the lan card?

Yes
No

 

[Richard in AZ]

I had an issue like this.... it turned out to be a firmware upgrade for the Router (Belkin)
needed. The Win 7 machine wouldn't authenticate but XP/Vista did no problem. The Win7 machine
had worked on other WLAN routers so I knew the individual elements of the solution all worked in
isolation.

Thanks, I will pass that suggestion on.