View Single Post
  #4  
Old April 28th 08, 11:59 PM posted to microsoft.public.windowsme.networking
Mart
External Usenet User
 
Posts: 1,190
Default Windows ME and Wireless Networking - Failure to Connect

Can't add much more Mike, as once I got them to be re-recognised, I was just
happy that they worked and moved on g Should have documented the detail,
I suppose but now work from the 'lesson learnt' and if/when it happens
again, I'll just go thru' 'delete' procedure and hope it remains successful.

(Having other issues with BT Broadband - it keeps failing. Proved it clear
of home - twice - so I'm living with Dial-up Pay & Go. Bl**dy Slow!!)

Mart


"Mike M" wrote in message
...
Mart wrote:

I'm not really into Networking but your problem sounds similar to a
couple experiences I had with my BT HomeHub router. I found that if a
working dongle or PCMCIA card on one PC was transferred to another,
like yours it could see the router but wouldn't shake hands.

I ended up by 'removing' or Deleting it/them from the list of
(previously) detected devices under the Configuration settings of the
Router (using another PC) and then let the router re-detect the
dongle/PCMCIA card and set it up again.

I never bothered to work out why, but did wonder if it had something
to do with possibly duplicated Physical or IP address settings. All
other (working) wireless/USB devices showed unique addresses.

Sorry if it doesn't relate, but it did work here. Good luck.


An interesting observation Mart and a very different experience from my
own. My current router (SpeedTouch 585v6 v6.1.4.3 firmware [later
firmware exists but does not support telnet access]) keeps a history of
all attached devices, last allocated IP address (if variable) and in the
case of wired hardware, the router port to which last connected. In fact
this is perhaps one of its better implemented features.

Let's hope this helps Robin with his problem.
--
Mike Maltby