Wireless works on all Devices EXCEPT Sharp UM32W

[IanGlinka]

I have no idea why, but the wireless network at work is functional with ALL devices EXCEPT users who have Sharp UM32W notebook PCs.

The SSID shows up in the available networks list... I type in the WEP encryption key, but then it just kicks back and a few seconds later it pops up again "wireless networks available."

Again, the wireless network is working for all other devices here. It is only the Sharp notebook PCs that are unable to connect.

I have tried updating the drivers for the integrated wireless NIC, I've tried setting a 64 bit hex key instead of a 128 bit hex key, I've tried changing the channel from 1 to 6 to 7.... no luck at all.

I do not understand why these notebooks refuse to connect to my wireless network!

Anybody have any ideas?

Thanks
Ian

 

[IanGlinka]

Some additonal info:

The WAP (A D-Link DI-624 revision A) is setup with the following settings:
TX Rate: Auto
Beacon interval: 100msec
RTS Threshold: 2432
Fragmentation: 2346
DTIM interval: 3
Preamble Type: Short Preamble
Authentication: Open System
SSID Broadcast: Enabled
802.11g Only Mode: Disabled
Frame Burst: 0

I have a 128 bit hex WEP encryption key set for the wireless network.

It is running on channel 7 currently.

 

[IanGlinka]

Interesting...

I just noticed the activity log in my DI-624 is showing 20 pages worth of the following error:

"Jun/07/2004 09:01:43 Target IP(192.168.255.255), Target Port(137) Packet Dropped
Jun/07/2004 09:01:43 Spoof IP(192.168.37.103), Spoof Port(137)
Jun/07/2004 09:01:43 Spoof Attack fromd MAC(00-0D-56-7A-08-F2) Detect,
Jun/07/2004 09:01:42 Target IP(192.168.255.255), Target Port(137) Packet Dropped
Jun/07/2004 09:01:42 Spoof IP(192.168.37.103), Spoof Port(137)
Jun/07/2004 09:01:42 Spoof Attack fromd MAC(00-0D-56-7A-08-F2) Detect,
Jun/07/2004 09:01:42 Target IP(192.168.255.255), Target Port(137) Packet Dropped
Jun/07/2004 09:01:42 Spoof IP(192.168.37.103), Spoof Port(137)
Jun/07/2004 09:01:42 Spoof Attack fromd MAC(00-0D-56-7A-08-F2) Detect, "

and so on and so forth...

Trying to figure out what this is, but I do know these messages started popping up in the log the moment the Sharp computer users started trying to connect wirelessly.

 

[IanGlinka]

hmm... I got it working... and this makes no sense...

I set the preamble to long on my WAP and bam... came up instantly on the Sharp notebooks.

Anybody have any idea why this would be?

I originally set the preamble to short so the WAP wouldn't crash and reboot as much (I read in a few web forums that setting the preamble to short would help out with D-Link's all to familiar crashing/rebooting problem).

In light of that, I would prefer to use short preamble, however, short preamble seems to be incompatible with the Sharp notebook integrated wireless NICs.

So that brings me to my new question... how are we supposed to get the Sharp integrated wireless adapters to work with short preamble?

Ian