BT Voyager 2110 Wireless Issue - Recognised but not connecting

Hi Guys

appreciate any help you might be able to give a wireless n00b with the following problem.

I have my PC connected via a LAN cable to a BT Voyager 2110 with wireless capability. The reason it's not wirelessly connected is that I although I could get my adapter to find the network, it wouldn't connect.

When my brother brought his Mac round, the Mac recognised the network, connected (with the wireless key, natch) and had no problems. So I put my problems down to a cheap EBAY bought adapter (a netkey TMB245).

Now my flatmate is trying to connect to the same network, with the same problem - it recognises the network. We click 'connect', it asks for the Network Key. We enter the network key and the 'connecting' dialogue box is displayed for several minutes, before disappearing but leaving the computer not connected to the network.

Any ideas?

I'm having the same problem. I can connect to the internet through the 2110's ethernet cable, but my adapter - Netgear WG111v2 will sometimes recognise the voyager's wireless signal but will not connect to it. I've used the Netgear smart wizard and Windows (XP Pro) to try to manage the connection, but neither work. I've tried on three different computers, two with the Netgear adapter, and one with an internal Linksys wireless PCI card.

Is this a Voyager problem? I can connect perfectly wirelessly with all three computers with my other router, Netgear DG834G.

Like RobRG1 - any ideas?

Alan

To anyone still interested - Voyager helpline answered promptly (no muzak) and was very helpful (surprise, for BT?). He advised that I changed the channel from 3 to 11, which my Netgear had been on. I did this and I could connect immediately.

Hope this helps.

Alan

Congrats!

If it's a radio interference problem like that, things like wireless phones, computer monitors, even HVAC ductwork in the way can cause service dropouts.

Also, some antennas might be slightly tuned better for a narrow channel range.

Hi, I,m new to the forum and would appreciate some assistance

I have a BT Voyager 2110 router and have been trying to get wireless-ly connected via my new laptop (Hewlett Packard 510). I can only connect to the interent when I plug in the ethernet cable, when I try and do it wirelessly it detects the Voyager, and the signal strength is excellent but it just wont connect. The laptop has built-in wireless ability. I previously used the router with my Toshiba laptop but used the external wireless card that came with the router and had no problems. The HP laptop is a replacement for the Toshiba which was stolen with the wireless card. Any assistance would be really appreciated.

You said the laptop was new. Some people are having trouble with computers running Vista, because the wifi hardware manufacturers haven't worked out all the bugs and released new firmware. Keep an eye out for new firmware.

In the interim, turn off fire walls and encryption and test systematically, to see if those might be obstacles.

Hi,
Thanks for the assistance. I should have mentioned that the laptop is running XP and Norton Internet Security. I tried uninstalling Norton and then connecting but it still did the same thing - says it is waiting for network and then just stops trying. I also turned off encyption but still couldn't connect. Since my first post I tried the second replacement laptop (I had two stolen), and it is identical to the first one (HP 510) and it worked wirelessly first time - the only thing I remember doing differently is when asked by Norton if I wanted it to manage networking I said no and I thik I said yes with the first laptop cos I didn't know better at the time. However, since I have removed Norton from the first laptop I don't see how that can be causing my problem. I have gone back and checked both settings one by one of the two laptops and they are identical! Help!

alanbo, thanks for the tip. I've just started having this exact problem with my Voyager 2110 today, and changing the channel _seems_ to have worked.

I haven't changed any hardware lately, but I guess that someone nearby must have done - causing the interference.