Are DLink DWA-547 and USR 5451A MAXg incompatible?

Hello,

I have a DLink DWA-547 wireless card and
a USRobotics 5451A MAXg access point...
Both devices are wi-fi certified.

I've tried to realize a wireless network with them,
but something's not right.
I mean, both devices are configured correctly
(WPA2 passfrase, AES protocol, etc.), nevertheless
the access point doesn't want to authenticate
the wireless client (DLink DWA-547).


Is there a solution to my problem?


Regards.

ant <ant.mirabella@gmail.com> hath wroth:

>I have a DLink DWA-547 wireless card and
>a USRobotics 5451A MAXg access point...
>Both devices are wi-fi certified.

I won't say anything nice about Wi-Fi certification.

>I've tried to realize a wireless network with them,
>but something's not right.
>I mean, both devices are configured correctly
>(WPA2 passfrase, AES protocol, etc.), nevertheless
>the access point doesn't want to authenticate
>the wireless client (DLink DWA-547).
>
>Is there a solution to my problem?

Sure. Try WPA-PSK-TKIP. I've seen a few compatibility issues with
AES encryption between random devices and firmware mutations. Also,
make sure you have the router set to WPA-PSK (also known as
WPA-Personal) and not to WPA-RADIUS (also known as WPA-Enterprise).

The DWA-547 is a UK only card. Check for up to date driver software.

You might wanna check if you have the latest firmware on the USR
Router:
<http://www.usr.com/support/product-template.asp?prod=5451a>

If the problem persists, you might want to disclose the exact error
message instead of "doesn't want to authenticate", along with some
clue as to what hardware and operating system you're running with the
Dlink.

--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

I'm using the wireless card under openSuse Linux 10.3
(ndiswrapper + D-Link DWA-547 Windows XP driver).


The exact error message is (from KDE KNetwork Manager):

"Connection failure

Could not connect to the network NETWORK NAME"


I tried it under Windows 2000 Professional,
but it didn't work.

The wireless card software is up to date
and I've also upgraded the access point firmware
to the latest version.


Regards.

ant <ant.mirabella@gmail.com> hath wroth:

>I'm using the wireless card under openSuse Linux 10.3
>(ndiswrapper + D-Link DWA-547 Windows XP driver).
>
>The exact error message is (from KDE KNetwork Manager):
>
>"Connection failure
>Could not connect to the network NETWORK NAME"

Well, that's not particularly useful for troubleshooting. I'm
especially interested in how that error message leads you to suspect
that "it does not want to authenticate". Methinks the problem is
somewhat more fundamental.

Any particular connection manager that you're using with SUSE 10.3?
When you scan for available networks as in:
<http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.3/suselinux-userguide_en/sec.new.mobnet.html#fig.ki.scan>
did you your own SSID? Do you see any others? If so, your
NDISwrapper install is probably working. If not, then your DLink or
your install is broken.

>I tried it under Windows 2000 Professional,
>but it didn't work.

Any particular error message or condition? It's kinda difficult to
troubleshoot a problem when you only supply summary judgements. I
would prefer the evidence and draw my own conclusions (and guesses).

>The wireless card software is up to date
>and I've also upgraded the access point firmware
>to the latest version.

OK. Please re-read my previous posting and kindly do what I asked
with respect to WPA-PSK-TKIP.

Instead of fighting the alleged incompatibility (another bad guess),
perhaps it would be helpful to determine if the problem is in the
Dlink end, or the USR end. Find an accomplis that has a known working
laptop. Invite them over and ask them to try to connect to your USR
router. If that works, then your router is probably working
correctly. Similarly, drag whatever machine you installed the DWA-547
card inside and try it with someone elses access point. If the
machine is not portable, borrow the access point and bring it to your
machine. In other words, divide and conquer.

Incidentally, you didn't mention if you have MAC address filtering,
SSID broadcast disabled, or done some other form of alleged security
tweaking. Some of these actions cause connection problems. If you
get nowhere, try resetting the USR router to defaults, manually reload
just the basic settings necessary to get on the internet and establish
a wireless connection, and try again. When that's working, you can
then mangle your system with various useless security tweaks.

--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

On 9 Dic, 08:43, Jeff Liebermann <je...@cruzio.com> wrote:
> ant <ant.mirabe...@gmail.com> hath wroth:
>
> >I'm using the wireless card under openSuse Linux 10.3
> >(ndiswrapper + D-Link DWA-547 Windows XP driver).
>
> >The exact error message is (from KDE KNetwork Manager):
>
> >"Connection failure
> >Could not connect to the network NETWORK NAME"
>
> Well, that's not particularly useful for troubleshooting. I'm
> especially interested in how that error message leads you to suspect
> that "it does not want to authenticate". Methinks the problem is
> somewhat more fundamental.
>
> Any particular connection manager that you're using with SUSE 10.3?
> When you scan for available networks as in:
> <http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.3/suselinux-usergui...>
> did you your own SSID? Do you see any others? If so, your
> NDISwrapper install is probably working. If not, then your DLink or
> your install is broken.
>
> >I tried it under Windows 2000 Professional,
> >but it didn't work.
>
> Any particular error message or condition? It's kinda difficult to
> troubleshoot a problem when you only supply summary judgements. I
> would prefer the evidence and draw my own conclusions (and guesses).

There isn't a particular error message...
The wireless card works great under openSuse 10.3 or Windows 2000
Professional,
the problem is caused by access point. In fact, it receives
authentication request
from D-Link wireless card but doesn't want to authenticate it.
I can check this in the access point user configuration interface
(page "status"):

http://www.usr.com/support/5451/5451-ui/status.htm

I can see a client (D-Link wireless card) that requires access to the
network but it isn't authenticate.

> >The wireless card software is up to date
> >and I've also upgraded the access point firmware
> >to the latest version.
>
> OK. Please re-read my previous posting and kindly do what I asked
> with respect to WPA-PSK-TKIP.

I've tried WPA-PSK-TKIP, but I haven't solved the problem.

> Instead of fighting the alleged incompatibility (another bad guess),
> perhaps it would be helpful to determine if the problem is in the
> Dlink end, or the USR end. Find an accomplis that has a known working
> laptop. Invite them over and ask them to try to connect to your USR
> router. If that works, then your router is probably working
> correctly. Similarly, drag whatever machine you installed the DWA-547
> card inside and try it with someone elses access point. If the
> machine is not portable, borrow the access point and bring it to your
> machine. In other words, divide and conquer.

I also tried with other wireless adapters on my notebook (Dell
Precision
workstation): a Netgear pcmcia and a Broadcom mini-pci.
The first had the same problem as D-Link wireless card.
The second worked fine (it has the same wireless chipset - Broadcom -
of the access point).

> Incidentally, you didn't mention if you have MAC address filtering,
> SSID broadcast disabled, or done some other form of alleged security
> tweaking. Some of these actions cause connection problems. If you
> get nowhere, try resetting the USR router to defaults, manually reload
> just the basic settings necessary to get on the internet and establish
> a wireless connection, and try again. When that's working, you can
> then mangle your system with various useless security tweaks.
[cut]

the security configuration (wpa, mac filtering, etc.) is
correct... the SSID broadcast is disabled.