Configure NETGEAR Wireless Access Point (ME103)

I just got a Netgear ProSafe wireless access point to put on my network.
It seems to be working just fine with all the default settings,
however I don't want to leave it wide open to anyone who walks by with a
wireless card. I need to get to the admin interface. Unfortunately, I
can't seem to figure out what IP address it is using... Does anyone know
what IP address the access point would use for its Web based
administrative console?

--
Chuck Tryon

Charles Tryon wrote:

>
> I just got a Netgear ProSafe wireless access point to put on my
> network.
> It seems to be working just fine with all the default settings,
> however I don't want to leave it wide open to anyone who walks by with
> a
> wireless card. I need to get to the admin interface. Unfortunately,
> I can't seem to figure out what IP address it is using... Does anyone
> know what IP address the access point would use for its Web based
> administrative console?

Ever try reading the Installation Guide;

ftp://downloads.netgear.com/files/ME103_InsGuide.pdf

192.168.0.224


--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759

Lenard wrote:
> Charles Tryon wrote:
>
>
>>I just got a Netgear ProSafe wireless access point to put on my
>>network.
>> It seems to be working just fine with all the default settings,
>>however I don't want to leave it wide open to anyone who walks by with
>>a
>>wireless card. I need to get to the admin interface. Unfortunately,
>>I can't seem to figure out what IP address it is using... Does anyone
>>know what IP address the access point would use for its Web based
>>administrative console?
>
>
> Ever try reading the Installation Guide;
>
> ftp://downloads.netgear.com/files/ME103_InsGuide.pdf
>
> 192.168.0.224

Yes, I did go through the documentation that came up when I
configured the AP, but it didn't have that address. Then, I tried but
found I still couldn't connect to the address.

The problem turned out to be that I am running on a different subnet:
192.168.1.x, so I wasn't connecting. I presume I could have added an
appropriate route, or changed the subnet mask, but the quickest solution
was just to change the address on one box to that 0 subnet. Everything
worked fine from that point.

Thanks!

--
Chuck