Trouble connecting WL100/NX80 and Netgear ME102, Help!!

[Haken]

I've just gotten my WL100 card, and trying to connect with my Netgear ME102 Access Point, but have been unsuccessful after many tries.

The access point settings are as follows:

Settings:

DHCP : Enabled
SSID: clem
Channel : 10
Key: Shared
WEP: 64Bits, Key 1 **********

Network settings on NX80:
SSID: clem
WEP: clem
Connect Mode: Infrastructure

Under advanced setup,
IP address: Auto,
DNS Adress: Auto
PowerSaveMode: Disabled.

Have been trying for so many times, can somebody please help me?

Thanks.

Haken

[n2ifp]

I don't show a listing for a ME102? Also, if there is no router, then you most likely will need to use adhoc mode, instead of infrastructure. Does the AP go direct to a PC? What's the internet connection type.

Leave the WEP blank/disabled until everything is working. Make it easier on yourself. It also has to be in HEX format.

If you use adhoc mode, then the IP and DNS addresses most likely need to be set manually.

Additionally, if there is no router, then most likely you'll need ICS, (internet connection) sharing setup.

[Haken]

Thanks, Larry.

ME102 is probably an asian model release of netgear.
found more info listing at the following:
http://www.netgear.com.sg/products/prod_details.asp?prodID=92

The AP is connected the switch, and we use a leased line.

Have tried connecting with ad-hoc, and have manually keyed in the IP and DNS addresses. After connecting for a short while, there is a message that says 'connected'.
But when I try to access the internet via netfront after that, I get an error message that says network settings invalid.

Am really puzzled.

Also, does a firewall make a difference right?
Currently, we are using watchguard.

Really hope you can assist me in this.
Am quite new to wireless...and quite lost as well!!

[mjhamilton]

HI Haken... this looks like you WEP is wrong but I agree with Larry.. turn it off for both devices and set both to Infrastructure mode.. also as a matter of course the default channel for Netgear is 11 so set the ME102 to this channel.

Also make sure you have a DHCP server on your network and that it has free addresses.

Once connected goto the Network under Prefs and log from the pull down menus.. this should let you know if you have an ip address, gateway and dns servers setup... if any of these are blank then you have an issue.. if they are all there then enter

ping www.yahoo.com

you should get a reply.. if not then try to ping the ip address for your local firewall....

lst us know how you get on

[n2ifp]

Originally posted by Haken
Thanks, Larry.

Your getting up and running will be Thanks enough, we don't want unhappy campers. We, meaning all CS members! PS: Sometimes it's not so easy! Please remember, one setting doesn't fit all. Good luck! :cool:

ME102 is probably an asian model release of netgear.
found more info listing at the following:
http://www.netgear.com.sg/products/prod_details.asp?prodID=92

I have to make sure you have the right stuff, if I assume...

The AP is connected the switch, and we use a leased line.

So your PC and Clie will both use it?

Have tried connecting with ad-hoc, and have manually keyed in the IP and DNS addresses. After connecting for a short while, there is a message that says 'connected'.

Adhoc is only for peer to peer, so Infrastructure is what you want. If you were using the PC as your router, then it would be adhoc.

But when I try to access the internet via netfront after that, I get an error message that says network settings invalid.

You can try manual settings on the Clie, leave the WAP on DHCP as Martin has suggested. Some setups only work with manual settings. The addresses below are for illustration purposes, yours will vary.

Clie:
Infrastructure mode
WEP=None until you get it working!
IP address: 192.168.2.2 (first device address)
Subnet mask: 255.255.255.0
Default Gateway: 192.168.1.1 (this is the router address)
DNS: 192.168.1.1 (this is your ISP DNS)
PowerSaveMode=Leave unchecked, until you get it working!
---------------------------------
 
The router should assign IP addresses as follows:
192.168.2.1 (router)
192.168.2.2 (first device address requested)
192.168.2.3 (second device address requested)
192.168.2.4 (third device address requested)
192.168.2.5 (forth device address requested)
and so on....

Am really puzzled.

Isn't WiFi so much fun...:rolleyes:

Also, does a firewall make a difference right?
Currently, we are using watchguard.

Possible, but more likely it would only affect WiFi HotSync, unles the firewall is in the router. It another item that can be disabled while trying to get your WiFi working.

Really hope you can assist me in this.

WEP should be set to HEX on all wireless units, AFTER you get it working!

Am quite new to wireless...and quite lost as well!!

I am always lost, I don't need WiFi for that...:)

Then you can follow Martin's advice, use the pull down menu in Network Prefs and select the Network Log. This is where you can ping Yahoo from.

[Haken]

Tried changing some of the settings, but managed to get it connected only after WEP was taken out.
The connection was great and fast.

But due to the fact that I need the WEP to be on for security purpose, tried the connection again with the WEP 64bit Hex on, everything else remaining the same, it failed to work.

Any idea what the problem may be with the WEP?

[williepalm]

Originally posted by Haken
I've just gotten my WL100 card, and trying to connect with my Netgear ME102 Access Point, but have been unsuccessful after many tries.

The access point settings are as follows:

Settings:

DHCP : Enabled
SSID: clem
Channel : 10
Key: Shared
WEP: 64Bits, Key 1 **********

Network settings on NX80:
SSID: clem
WEP: clem
Connect Mode: Infrastructure

Under advanced setup,
IP address: Auto,
DNS Adress: Auto
PowerSaveMode: Disabled.

Have been trying for so many times, can somebody please help me?

Thanks.

Haken

Try changing your NX's setting on :

SSID: Any

WEP: 64bits Key 1 **********(same as your AP)

[n2ifp]

Originally posted by Haken
Tried changing some of the settings, but managed to get it connected only after WEP was taken out.
The connection was great and fast.

But due to the fact that I need the WEP to be on for security purpose, tried the connection again with the WEP 64bit Hex on, everything else remaining the same, it failed to work.

Any idea what the problem may be with the WEP?

If you use the any for SSID, it has to be all lower case.

The WEP Hex Key should be generated in the Wireless AP. Then select 64 bit Hex on the Clie and then type in the 10 Hex figures! There are two Hex figures for each character. You take a 5 character text string, plug it into the WAP, then let the WAP create the 10 figures Hex code. Then you add the 10 figure Hex code to the 64Bit Hex on the Clie.

Your example shows clem for the WEP, you need 5 instead of 4 letters, then it needs to be converted to Hexadecimal format! You can do that in most WAP's or you can do it manually, but it's harder to figure the Hex number for each character.

Microsoft Bookshelf gives a real nice explaination and examples.

[ultraman]

If you check the message boards you will find out that the Netgear wireless equipment doesn't really work with WEP. I have a ME102 and the only security I have on is MAC filtering. this doesn't really stop people from seeing what you transfer but does stop them from using your network (ok lets not get into mac spoofing)

back to WEP, if you keep it on, the access point will keep dropping connections on you. this should also happen to your laptop wireless connection (if you have one). you can test this out to verify it.

if you call the netgear support them they will tell you this. you might try and get a refund from them or something. ( i tried but didn't work :( )

[jmg_NX21]

Is that why my connection drops on our PC?

We had trouble with ours. I have to ask my bro what he did *something in the settings*

[williepalm]

Originally posted by n2ifp


If you use the any for SSID, it has to be all lower case. 



But I've been using "Any" with a capital A and have no problems with connecting with hotspots.

[n2ifp]

Originally posted by williepalm


But I've been using "Any" with a capital A and have no problems with connecting with hotspots.

I went by my experience and what other CS members have related.

This the first time I had heard anything about Netgear having issues with the WEP? Everything I have seen posted so far, indicates it's not being setup right. At the very minimum, the phrase for WEP has to be FIVE characters long! Netgear historically has been one of the easier units to setup per past CS memebers with the Clie! Now if Netgear mades changes, as they all do, then of course it may now be a problem that didn't exist before.

[Haken]

Have actually tried keying as per the instructions for WEP with the same number of characters as per the settings on the AP, and it still doesn't work.

As well, have been using a Netgear card with my laptop, on the same wireless network with the same AP, and it works great.
Not sure how well it the Netgear AP works with other cards, but it seems to be okay for Netgear cards.

Can't figure out why there poses a problem with the WEP, and none when it's taken out.

Is it the way it's being encrypted via the WL100 as opposed to the normal wireless cards on laptops?

[Unregistered]

Did you input all 10 HEX figures into your Clie's for the WEP?

Some devices, laptops for example, can use a pass phrase instead of a Hexidecimal code. The Clie has to use Hexidecimal not a name! I am not sure if you understand that?

[n2ifp]

Originally posted by Unregistered
Did you input all 10 HEX figures into your Clie's for the WEP?

Some devices, laptops for example, can use a pass phrase instead of a Hexidecimal code. The Clie has to use Hexidecimal not a name! I am not sure if you understand that?

This is a pain, got interuppted by a phone call from my doctor and was logged out for some reason.

[Haken]

Yes, have actually input in all 10 HEX figures for the WEP.
So for example 1234567890 is being input for both AP and Clie, it's fine right?

[n2ifp]

Okay, good. The Hex figures are 0 through 9 and A though F.

I use 128 bit WEP key, works fine!

For a 128 bit WEP Key, I use a 13 letter pass phrase in lower case and let my WAP convert it to a 26 figure HEX code for both the WAP and Clie!

Both use the same HEX figures! Additionally, you must use Key one only in the WAP!!!