ME102 (wireless access point) setup - help!

[zcacogp]

Chaps,

Slight desperation here.

I have just bought (2nd hand, from eBay) a Netgear ME102 wireless access point (WAP), intending to make a small wireless network. And I can't make it work!

Situation is this:

I have a BT Voyager 205 combined ADSL Modem and Router. This has a network port on the back, which I have plugged the wireless access point into. Via a "straight" cable (i.e. not a cross-over cable.)

I have also plugged it into the mains (doh!), and am trying to make it work.

There are two LED's on the front of the WAP, and they are both on all the time.

The "Ethernet" light on the modem/router is on, and flashes from time to time, suggesting that there is (occasional) traffic between the router and the WAP.

I have a personal laptop, and a work laptop, and I cannot make either laptop "see" the router, or the network that the router (should be) creating.

The WAP also has a USB port, to allow you to plug a computer into it to act as a configuration console. This is all working, and I can access loads of settings via this. However, no matter what I do with the settings, neither laptop will see the network. (I know that at least the work laptop works with wireless networks, as I connected to a public one with it yesterday. The personal one does as well, but hasn't for the last 6 months or so - not broken, just haven't tried it.)

I have tried everything, including allowing the WAP to broadcast the ESSID, and setting it so that there is no security (not enabling encryption). Still, no joy.

Any ideas? I am aware that the WAp is second hand, so think that a. it may be duff (which I hope it isn't), or b. it ha some setting set in it somewhere which is mega-secure and is therefore refusing to allow me to play.

Any ideas? (No matter how simple!)

Thanks,


Oli.

[xiphias]

Make sure the usb and network cable aren't plugged in at the same time. Other than that, reset everything to defaults and see if you can see anything. I can't really remember, but don't you have to set it a static ip? I might be able to log into parents from here and find out.

[zcacogp]

Chaps,

OK, if anyone was thinking of posting an answer (pause ... anyone there? No!), I have solved it.

Lappie 1 (personal one) had Wireless Networking turned off in the BIOS (must be an auto default when I rebuilt it about 3 months ago. I worked 6 months ago.)

And I was using lappie 1 as a check to see whether it was working. Only used Lappie 2 (company) at the start, when there must have been something else wrong.

Therefore, apply the rule of Occums razor (or something, i guess) and it works! (This is being posted from my lounge, via wireless! Woo Hoo!)


Oli.

[zcacogp]

xiphias said:

Make sure the usb and network cable aren't plugged in at the same time. Other than that, reset everything to defaults and see if you can see anything. I can't really remember, but don't you have to set it a static ip? I might be able to log into parents from here and find out.

Xiphas,

Sorry mate, you were writing that at the same time as I was writing my last post.

Thanks for your input. As it is, all is OK now.

But thanks for your help none the less. (As it is, the USB and network cable can be both plugged in at once. IP is on DCHP. I think. Must check.)


Oli.

[JonRB]

xiphias said:

Make sure the usb and network cable aren't plugged in at the same time.

Why on earth not? If the USB port is for diagnostics as stated, rather than data, then it would be a pretty bloody stupid diagnostics port if you had to disconnect the unit from the network in order to diagnose it.

[xiphias]

JonRB said:

xiphias said: Make sure the usb and network cable aren't plugged in at the same time. Why on earth not? If the USB port is for diagnostics as stated, rather than data, then it would be a pretty bloody stupid diagnostics port if you had to disconnect the unit from the network in order to diagnose it.

Because the manual states so. And mine didn't work if you did. So less please.

[JonRB]

xiphias said:

Because the manual states so. And mine didn't work if you did. So less please.

Well to the manufacturer then!

>> Edited by JonRB on Sunday 22 January 20:09

[zcacogp]

JonRB said:

xiphias said: Because the manual states so. And mine didn't work if you did. So less please. Well to the manufacturer then!

Hats off to Xiphias - he reads his manuals very closely. Although I will say that mine works qite nicely with the USB lead plugged in.

(And I'll add that it seems like a cracking bit of kit - less than a tenner on eBay, and worth every penny!)


Oli.

[zcacogp]

xiphias said:

Because the manual states so.

Back to a slightly old topic ... I have found that if you have the console UCB cable attached when you power-down the machine the USB cable is attached to, the machine doesn't close down properly, and does a full memory dump (blue screen of death).

Not sure if this is the thing the manual is referring to. Or just a peculiarity of my desktop machine.


Oli.