"wireless authentication failed because of a timeout"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Trying to connect my new Acer laptop running Vista home premium to the
internet via wireless connection (router WPA).
and getting the following error message "wireless authentication failed
because of a timeout"
works okay if i plug it in direct to the router, my old laptop works okay
running on XP!!
have downloaded all the latest update for Vista.
any other ideas?
 
It could be security settings issue. Try switch from AES to TKIP or to WEP. Please post back with the result.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Trying to connect my new Acer laptop running Vista home premium to the
internet via wireless connection (router WPA).
and getting the following error message "wireless authentication failed
because of a timeout"
works okay if i plug it in direct to the router, my old laptop works okay
running on XP!!
have downloaded all the latest update for Vista.
any other ideas?
 
have the setting as TKIP already. Changing to AES or WEP doent let me even
try to connect so i know TKIP is the correct setting.
 
For a test, does it work if you don't setup security?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
have the setting as TKIP already. Changing to AES or WEP doent let me even
try to connect so i know TKIP is the correct setting.
 
Yes, we have tried switching off encryption on the router and can connect
without any problems.
 
which router? do you have the latest firmware for it?
do you even get an IP?

Trying to connect my new Acer laptop running Vista home premium to the
internet via wireless connection (router WPA).
and getting the following error message "wireless authentication failed
because of a timeout"
works okay if i plug it in direct to the router, my old laptop works okay
running on XP!!
have downloaded all the latest update for Vista.
any other ideas?
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
3com - no updates aval
not sure on your 'IP' question, we cant connect to the router when encrypted.
 
I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeoutâ€.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!
 
I understand all of that, but you still need to provide some
information. It might be the driver. Or something else. If the
router is so old that it does not support WPA2, this is a symptom
that can mean that it is time to replace it.

First, please post the text results of ipconfig/all.

start
programs
accessories
command prompt (right click and select run as administrator and
acknowledge the prompt)

ipconfig /all [enter]

click the icon on the menubar on the left and then edit, select all
(it will turn white)

click the icon in the menubar again then edit, copy

this copies to the clipboard.
paste into a reply

second, type or paste the following into the start/search box

mmc devmgmt.msc

acknowledge the prompt

expand the Network Adapters
right click on the wireless adapter
select properties
select the driver tab
now copy down the information and post it in your reply.

I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeout”.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Here's the information you requested:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-64-D5-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-16-D4-DB-F8-AC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{88786960-82BE-4254-9F01-755107806
846}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{887F2413-BF21-40E7-801F-5218B4ECB
CE8}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix .
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Wireless Network Adapter Details

Intel® PRO/Wireless 3945ABG Network Connection

Driver provider: Intel
Driver date: 30/04/2007
Driver version: 11.1.1.11
Digital signer: Microsoft windows hardware compatibility publish

I look forward to your reply.

Thanks,
Dan

Barb Bowman said:
I understand all of that, but you still need to provide some
information. It might be the driver. Or something else. If the
router is so old that it does not support WPA2, this is a symptom
that can mean that it is time to replace it.

First, please post the text results of ipconfig/all.

start
programs
accessories
command prompt (right click and select run as administrator and
acknowledge the prompt)

ipconfig /all [enter]

click the icon on the menubar on the left and then edit, select all
(it will turn white)

click the icon in the menubar again then edit, copy

this copies to the clipboard.
paste into a reply

second, type or paste the following into the start/search box

mmc devmgmt.msc

acknowledge the prompt

expand the Network Adapters
right click on the wireless adapter
select properties
select the driver tab
now copy down the information and post it in your reply.

I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeoutâ€.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
well, a Google Search tells me that you are not alone with this
issue. the combination of this 3Com wireless router and the Intel
3945 wireless and WPA issues seems a common issue.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PageIndex=7&SiteID=17&PageID=7&PostID=481371
was one of the links I found. I note there was one person who stated
he fixed the issue by changing from G only to B+G mode.

there really isn't much else I can offer you if this does not work.
(other than replacing the 3Com router).

Here's the information you requested:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-64-D5-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-16-D4-DB-F8-AC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{88786960-82BE-4254-9F01-755107806
846}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{887F2413-BF21-40E7-801F-5218B4ECB
CE8}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix .
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Wireless Network Adapter Details

Intel® PRO/Wireless 3945ABG Network Connection

Driver provider: Intel
Driver date: 30/04/2007
Driver version: 11.1.1.11
Digital signer: Microsoft windows hardware compatibility publish

I look forward to your reply.

Thanks,
Dan

Barb Bowman said:
I understand all of that, but you still need to provide some
information. It might be the driver. Or something else. If the
router is so old that it does not support WPA2, this is a symptom
that can mean that it is time to replace it.

First, please post the text results of ipconfig/all.

start
programs
accessories
command prompt (right click and select run as administrator and
acknowledge the prompt)

ipconfig /all [enter]

click the icon on the menubar on the left and then edit, select all
(it will turn white)

click the icon in the menubar again then edit, copy

this copies to the clipboard.
paste into a reply

second, type or paste the following into the start/search box

mmc devmgmt.msc

acknowledge the prompt

expand the Network Adapters
right click on the wireless adapter
select properties
select the driver tab
now copy down the information and post it in your reply.

I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeout”.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!




:

what wireless NIC/radio and what driver version?

On Wed, 12 Sep 2007 12:54:01 -0700, Dan

3com - no updates aval
not sure on your 'IP' question, we cant connect to the router when encrypted.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
That's very disappointing. I found that post (along with several others)
during my own research, but the router is already operating in B+G mode, so
unfortunately that isn't a solution. It does appear that many other people
are having this problem, but it doesn't seem to be limited to this particular
router, so I'm reluctant to replace it in case the new one doesn't work
either! Besides which, I hadn't expected to have to spend the extra money on
a new router when Windows Vista is supposed to be compatible with WPA. I'm
currently feeling very, very disappointed with Vista


Barb Bowman said:
well, a Google Search tells me that you are not alone with this
issue. the combination of this 3Com wireless router and the Intel
3945 wireless and WPA issues seems a common issue.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PageIndex=7&SiteID=17&PageID=7&PostID=481371
was one of the links I found. I note there was one person who stated
he fixed the issue by changing from G only to B+G mode.

there really isn't much else I can offer you if this does not work.
(other than replacing the 3Com router).

Here's the information you requested:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-64-D5-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-16-D4-DB-F8-AC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{88786960-82BE-4254-9F01-755107806
846}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{887F2413-BF21-40E7-801F-5218B4ECB
CE8}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix .
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Wireless Network Adapter Details

Intel® PRO/Wireless 3945ABG Network Connection

Driver provider: Intel
Driver date: 30/04/2007
Driver version: 11.1.1.11
Digital signer: Microsoft windows hardware compatibility publish

I look forward to your reply.

Thanks,
Dan

Barb Bowman said:
I understand all of that, but you still need to provide some
information. It might be the driver. Or something else. If the
router is so old that it does not support WPA2, this is a symptom
that can mean that it is time to replace it.

First, please post the text results of ipconfig/all.

start
programs
accessories
command prompt (right click and select run as administrator and
acknowledge the prompt)

ipconfig /all [enter]

click the icon on the menubar on the left and then edit, select all
(it will turn white)

click the icon in the menubar again then edit, copy

this copies to the clipboard.
paste into a reply

second, type or paste the following into the start/search box

mmc devmgmt.msc

acknowledge the prompt

expand the Network Adapters
right click on the wireless adapter
select properties
select the driver tab
now copy down the information and post it in your reply.

On Thu, 13 Sep 2007 09:40:01 -0700, Dan

I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeoutâ€.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!




:

what wireless NIC/radio and what driver version?

On Wed, 12 Sep 2007 12:54:01 -0700, Dan

3com - no updates aval
not sure on your 'IP' question, we cant connect to the router when encrypted.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
from a wired connection, go to
http://www.microsoft.com/windows/using/tools/igd/default.mspx and
run the tests. I'd be curious to see the output to see if there are
other failures in addition to the wireless.

it may be the wireless driver written by Intel that is responsible
for the issue.

I'm using a D-Link DIR-655 which is certified for Windows Vista.
There IS a certification program, so if you do decide to replace the
3Com, you may want to pick something from that list. or at least one
marked "compatible".

http://winqual.microsoft.com/HCL/ProductList.aspx?m=v&cid=712&g=d

I don't see any 3Com products listed, BTW.




That's very disappointing. I found that post (along with several others)
during my own research, but the router is already operating in B+G mode, so
unfortunately that isn't a solution. It does appear that many other people
are having this problem, but it doesn't seem to be limited to this particular
router, so I'm reluctant to replace it in case the new one doesn't work
either! Besides which, I hadn't expected to have to spend the extra money on
a new router when Windows Vista is supposed to be compatible with WPA. I'm
currently feeling very, very disappointed with Vista


Barb Bowman said:
well, a Google Search tells me that you are not alone with this
issue. the combination of this 3Com wireless router and the Intel
3945 wireless and WPA issues seems a common issue.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PageIndex=7&SiteID=17&PageID=7&PostID=481371
was one of the links I found. I note there was one person who stated
he fixed the issue by changing from G only to B+G mode.

there really isn't much else I can offer you if this does not work.
(other than replacing the 3Com router).

Here's the information you requested:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-64-D5-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-16-D4-DB-F8-AC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{88786960-82BE-4254-9F01-755107806
846}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{887F2413-BF21-40E7-801F-5218B4ECB
CE8}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix .
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Wireless Network Adapter Details

Intel® PRO/Wireless 3945ABG Network Connection

Driver provider: Intel
Driver date: 30/04/2007
Driver version: 11.1.1.11
Digital signer: Microsoft windows hardware compatibility publish

I look forward to your reply.

Thanks,
Dan

:

I understand all of that, but you still need to provide some
information. It might be the driver. Or something else. If the
router is so old that it does not support WPA2, this is a symptom
that can mean that it is time to replace it.

First, please post the text results of ipconfig/all.

start
programs
accessories
command prompt (right click and select run as administrator and
acknowledge the prompt)

ipconfig /all [enter]

click the icon on the menubar on the left and then edit, select all
(it will turn white)

click the icon in the menubar again then edit, copy

this copies to the clipboard.
paste into a reply

second, type or paste the following into the start/search box

mmc devmgmt.msc

acknowledge the prompt

expand the Network Adapters
right click on the wireless adapter
select properties
select the driver tab
now copy down the information and post it in your reply.

On Thu, 13 Sep 2007 09:40:01 -0700, Dan

I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeout”.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!




:

what wireless NIC/radio and what driver version?

On Wed, 12 Sep 2007 12:54:01 -0700, Dan

3com - no updates aval
not sure on your 'IP' question, we cant connect to the router when encrypted.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Hi
have just run the tests and all returned as supported (with exeption of
"UPnP Support Test" which is turned off as recomended by 3com)

Thanks

--



Barb Bowman said:
from a wired connection, go to
http://www.microsoft.com/windows/using/tools/igd/default.mspx and
run the tests. I'd be curious to see the output to see if there are
other failures in addition to the wireless.

it may be the wireless driver written by Intel that is responsible
for the issue.

I'm using a D-Link DIR-655 which is certified for Windows Vista.
There IS a certification program, so if you do decide to replace the
3Com, you may want to pick something from that list. or at least one
marked "compatible".

http://winqual.microsoft.com/HCL/ProductList.aspx?m=v&cid=712&g=d

I don't see any 3Com products listed, BTW.




That's very disappointing. I found that post (along with several others)
during my own research, but the router is already operating in B+G mode, so
unfortunately that isn't a solution. It does appear that many other people
are having this problem, but it doesn't seem to be limited to this particular
router, so I'm reluctant to replace it in case the new one doesn't work
either! Besides which, I hadn't expected to have to spend the extra money on
a new router when Windows Vista is supposed to be compatible with WPA. I'm
currently feeling very, very disappointed with Vista


Barb Bowman said:
well, a Google Search tells me that you are not alone with this
issue. the combination of this 3Com wireless router and the Intel
3945 wireless and WPA issues seems a common issue.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PageIndex=7&SiteID=17&PageID=7&PostID=481371
was one of the links I found. I note there was one person who stated
he fixed the issue by changing from G only to B+G mode.

there really isn't much else I can offer you if this does not work.
(other than replacing the 3Com router).

On Thu, 13 Sep 2007 12:42:03 -0700, Dan

Here's the information you requested:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Laptop2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network
Con
nection
Physical Address. . . . . . . . . : 00-19-D2-64-D5-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated
Controlle
r
Physical Address. . . . . . . . . : 00-16-D4-DB-F8-AC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{88786960-82BE-4254-9F01-755107806
846}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{887F2413-BF21-40E7-801F-5218B4ECB
CE8}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix .
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


Wireless Network Adapter Details

Intel® PRO/Wireless 3945ABG Network Connection

Driver provider: Intel
Driver date: 30/04/2007
Driver version: 11.1.1.11
Digital signer: Microsoft windows hardware compatibility publish

I look forward to your reply.

Thanks,
Dan

:

I understand all of that, but you still need to provide some
information. It might be the driver. Or something else. If the
router is so old that it does not support WPA2, this is a symptom
that can mean that it is time to replace it.

First, please post the text results of ipconfig/all.

start
programs
accessories
command prompt (right click and select run as administrator and
acknowledge the prompt)

ipconfig /all [enter]

click the icon on the menubar on the left and then edit, select all
(it will turn white)

click the icon in the menubar again then edit, copy

this copies to the clipboard.
paste into a reply

second, type or paste the following into the start/search box

mmc devmgmt.msc

acknowledge the prompt

expand the Network Adapters
right click on the wireless adapter
select properties
select the driver tab
now copy down the information and post it in your reply.

On Thu, 13 Sep 2007 09:40:01 -0700, Dan

I’m afraid that question is a bit too technical for me!

Here’s what I can tell you. The router is a 3com 3CRWDR100A-72. We’ve
installed the latest firmware available from the 3com site, dated 26 April
2007.

We’ve been using this set-up to access the Internet, with WPA-PSK encryption
between the router and any PCs connecting to it, for about 3 years, with no
problems at all. Both the PCs we’ve used until now have been running Windows
XP. With our existing laptop, it was a simple matter of scanning for wireless
networks in the vicinity and entering the necessary WPA passphrase, and the
laptop then logged on to the router automatically every time it was booted
up. The router automatically allocates an IP address to any machine
connecting to it.

The new machine, running Windows Vista, finds the router with no problem and
recognises that it’s a secure network. We try to connect and are asked for
the passphrase. We enter this, there is a pause, then Vista says that it is
unable to connect. When we ‘analyse the problem’, we are told “wireless
authentication failed because of a timeoutâ€.

If we switch off the WPA encryption on the router and go through the same
process, Vista connects to the router and we are able to access the Internet.

Therefore, it seems clear that Vista is unable to handle some aspect of
communication with the router using WPA encryption. The router does not offer
WPA2 encryption, and obviously we don’t want to operate an unsecured network,
so we can’t see what alternative there is. This is a brand new laptop, with
Vista preinstalled, so we can’t understand why it fails to work with what is
obviously an extremely common set-up.

We’ve done some research on the Web and it appears that many people are
having exactly the same problem, but nobody seems to have a definitive
solution. We’ve updated the drivers for the wireless network card in the
laptop, with no effect. We’ve also tried the Microsoft Hotfix described in
KB935222, but that didn’t work either. We thought about trying the registry
change mentioned in KB928233, but decided that it wasn’t relevant, since we
can connect to the router without encryption, so the problem is not that
Vista can’t obtain an IP address from the router.

In short, we’re at a complete loss as to what else to do!




:

what wireless NIC/radio and what driver version?

On Wed, 12 Sep 2007 12:54:01 -0700, Dan

3com - no updates aval
not sure on your 'IP' question, we cant connect to the router when encrypted.
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/

--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
wonder why they would recommend turning UPnP off. Vista relies on
UPnP (and some other technologies) more than any previous OS.
Interesting (but it doesn't really have any bearing on the wireless
authentication issue).

Hi
have just run the tests and all returned as supported (with exeption of
"UPnP Support Test" which is turned off as recomended by 3com)

Thanks
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Rob, *I* don't have a problem. But if you are trying to convey that
you have an issue with a 3com router and it is the same model as the
other person who posted about this, the answer is probably the same.
You need to post the details of what issue you are trying to
resolve.

Hi all,

New to this but I have the same problem as Barb, I have a new Dell
Vestro laptop 1500 and using a 3 comm router - works fine with another
laptop on XP but get timeout.

Please can you let me know if this was resolved please - would be great
to get my laptop working.

Let me knwo
--

Barb Bowman
MS-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Hi
When using regular End-User Wireless hardware it is better to leave the
Wireless setting left at the default.
Playing with some of the variable just because they have "exotic" names
usually impede the signal rather than making it faster.
The None default setting are suitable for special networks that use more
sophisticated enterprise level equipment.
Jack (MS, MVP-Networking)
 
Back
Top