Basically it saw my old netgear (or when i added the netgear). Now it won't pickup the draytek even when I specify the details. It just doesn't see it - yet it sees next door. Any ideas?
Basically it saw my old netgear (or when i added the netgear). Now it won't pickup the draytek even when I specify the details. It just doesn't see it - yet it sees next door. Any ideas?
This is wireless I presume ?
have you enabled MAC filtering ?
What security are you running on the draytek ?
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
It's wireless
I'm running WPA-PSK
Mac filtering is off
ok a couple of silly questions ,
(you'll have to bear with me as I'm not too familiar with xbox 360 networking )
try dropping the security to WEP or ( very briefly disabling security )
can you connect the the xbox with a cable sucessfully.
Is the SSID set to boradcast on the router ?
do you have any other wireless devices ?
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
1) I'll try dropping it
2) I'll try a cable
3) The SSIS is set to broadcast
4) Yes and it sees the router perfectly and is working fine with it (a PC with a wireless netgear nic+hawking aerial).
EDIT- Turned WPA-PSK (1) off and it works fine...should I re-enable and see how it goes?
Edit - Turned it on and it no longer sees it and it doesn't find it by specifying it.
Last edited by Robert; 06-10-2006 at 03:15 PM.
are you using the standard MS wifi adaptor ?
my Virtualisation Blog http://jfvi.co.uk Virtualisation Podcast http://vsoup.net
Yeah. It's really odd. I turn off WPA-PSK and it's fine. I turn it on and it won't see it (yet it sees next doors which is WPA as well). It won't let me specify the router either (just doesn't find it).
I've tried changing the channel - which doesn't seem to help. I don't know what channel they're on, but they're using WPA. As I've said - it all works fine without WPA on, but with it on it's a definate no go.
Well a friend came up with a solution (he googled: +Xbox360 +draytek
) and basically it boils down to this:
You can select WPA+WPA2 OR WPA2 - the 360 has issues with WPA2, hence it has problems finding it. You have to into cmd and type:
telnet 192.168.0.1
wl (lower case L) space wpa 3
It works perfectly now
Here's an example. What usually happens is that the WPA+WPA2 is ticked, or just the WPA2 box. Now with that telnet command neither is ticked.
![]()
Last edited by Robert; 06-10-2006 at 05:01 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)