Hi.

Just trying to use my AP with my laptop

The setup is Laptop has Avaya Gold PCMCIA card, connecting to the AP.

Up until several weeks ago, it was working fine, giving access to the net from around the house, NOW it isnt.

The Access point firmware (Settings browsable from wireless laptop) comes up when browsed, and the wireless itself is running, Laptop reports 100% (excellent) signal, but i cannot access any PC's on the wired lan from wireless

I have removed the CAT5 from access point and plugged directly into laptop, and it works fine, but I cannot access the LAN from wireless. (no ping, no web, nothing), but yet the Cable connectivity ligts on the AP and switch are active (lit).

Laptop ~~~(Wireless)~~~~ Minitar <--(Cat5)--> Switch to LAN

What could be wrong.
The firmware is running code version V2.34

From other machines on the LAN are you able to ping the MNWAPB ? Trying to see if it's a problem with the bridge or a problem with the ethernet interface itself.

S.

Okay, i have powered up the AP and laptop to give this a go again.

From the Laptop, I cannot find the AP IP whatsoever.

Laptop IP: 192.168.1.23
Laptop card diagnostics, finds the AP, correct MAC address, good signal and actually connects. Taskbar wireless icon also shows full signal, Network devices for the device shows "Active".
Laptop card: Avaya Gold PCMCIA (802.11B)

AP: Access point is visible from LAN, it can be pinged and firmware pages browsed from LAN, IP address set to 192.168.1.254
AP client table lists the Laptop.

But I cant ping the laptop from LAN, or Cannot ping LAN from Laptop, its as if no traffic is traversing the wireless.

So, Thats not an Ether problem but the bridge itself ?

Yep, the bridge. Have you tried a factory reset to clear the config ?

Yeah, thats the thing.

I tried the factory reset thing by holding the button in (power off) then plugging it in and holding it depressed for 5 or so seconds, but the unit appears to still hold the old config.

This is running the 2.53 firmware. Doesnt look factory default to me.

Power the device on, press and hold the reset button fof 30 seconds then release, wait 5 minutes and try and access the device. The firmware will still be 2.53 - but the settings should default.

I pray to SM the god of helping...

With the instructions, the unit reset to factory, I deleted the profile on the laptop and recreated a new profile for the AP, and it connected, and I sent a ping to the LAN, and back to the laptop with success.

Many thanks Serialmonkey.

Now to secure it back down again.

[edit]

okay thats one.

The other one, went awol at the same time as the first, so i was thinking it was just the same problem, because at the time, i was swapping configs around between them.

This one, i have tried the default reset (that I did to the first), except, this one....
is detected by the Laptop wireless (show up in the active wireless list), but upon resetting to default, and trying to access the firmware on the default 192.168.2.1 doesnt respond, and I dont know how else. I am pretty sure this one is running 2.53 too.



[additional edit]
ROFLOMGWTFBBQ !!!

The unit is running 2.53, IP address 192.168.1.254, and its not responding to Firmware requests from Ethernet, because its listening from the wireless.
Default settings activated, and set to LAN IP (192.168.1.*)

So running 2.53, the unit is not responding to firmware access requests on ethernet but the firmware is accessable from Wireless.

If it really was default it should be 192.168.2.1, not 192.168.1.*

Do you find that you have a link light on the other end of the Ethernet cable for the MNWAPB that isn't only responding over wireless ?

Thats my point SM, this is after the Default (or so i thought).

The Cable for the unit in question here, is fine (Tested elsewhere), and the Hub port indicator is lit.

I went and tried the Default on the unit again.

This time, The unit has now reset back to default password, wireless settings, IP (192.168.2.1) etc.

192.168.2.1 is unaccessable from the LAN, The Laptop has connected to 192.168.2.1 (firmware) from wireless, and it does indeed look default, the unit still claims to be 2.53 revision firmware.

A factory default doesn't reset the firmware you are running - just the flash memory that holds the configuration. So if you are running 2.53 and factory reset, then you still have 2.53 - just a 2.53 with the default config.

I guess the factory reset didn't 100% work last time - but at least you are back to 192.168.2.1

Saying that, if you are still having problems I'm afraid it is hardware related with that unit. Are you running them in any sort of odd configuration that may have damaged the ethernet port ? (i.e. attached to an outdoor antenna, etc).

Whiteb,

Can I surgest that you check the ip address on your laptop that you are connection to the AP.

If you are running DHCP this won't work as you the default setting on the AP doesn't have DCHP server running.

You will have to change your IP address on you laptop to be 192.168.2.* so that it can find the AP. Then you should be able to access the 192.168.2.1 address.

Hmmmm.

I have not had the unit in any sort of weird and wonderful places, mostly in the box, or upgrading it, or playing around with config.

@kman.

I have a personal hate of DHCP, I only run static IP's.

The Laptop (Wireless) is able to browse the unit's Firmware, from wireless, so the Laptop's IP is not in question.

The problem is accessing the Ethernet interface. I have actually employed an IP scanner program that gives me list of all active IP's on my LAN, and the Minitar isnt showing.

So it seems what SM has said, is probably the case, Ethernet is dead on the minitar.