can't configure MN-500 (revisited)

Okay, a while ago I posted about a problem I was having trouble trying to
configure my MN-500.
My new house has prewired cat 5 so I wanted to setup the MN-500 for use in
base station mode. After setting it to basestation mode, I was no longer
able to connect to it via 192.168.2.1 or 0.1

Despite multiple resets to the unit I can not configure. I don't know if
anyone remembers me posting before but here's a link to the original thread
via google groups

http://www.google.com/groups?hl=en&l...gbl%26rnum%3D1

(here's a recap)
My notebook has an integrated ethernet and pcmcia mn-520 I've tried
configing the 500 using both.
When I try with wifi I'm asked for a wep key
(http://www.wowcentral.com/random/wifi_error.gif), if I try with ethernet
(http://www.wowcentral.com/random/eth_error.gif)
Now, mind you, without any configuration the mn-500 works fine as a hub if I
uplink it to our wired lan and I can connect my desktop and notebook through
it to connect to other computers and printers

I'm pretty frustrated with the whole thing. I just gave up last time because
I had just lost broadband and didn't need it that much anymore since any
file sharring between my main and laptop can be done via quick USB key
exchange. However, I'm getting DSL on the 1st and I want to have my wifi
back again so I can just connect our main router to internet and be up and
running.

I don't know WHY it's asking me for a WEP key or why it's picking up a BAC
wireless network...unless it's just picking up on the fact that my hardwire
lan is on BAC workgroup


In response to annon 1:
I believe he was saying, after I configure everything again, just leave it
in router mode and uplink to my hardwire lan? Wont that screw everything up
if it tries to use DHCP while our main router is doing the same thing? it
sounds iffy to me.

In response to Christ H:
those ip's were for my wifi cards, ethernet cards were on 192 etc when I
connected them to my main lan

In response to Jason Tsang:
I knew/know that's the problem (on the wifi), I wish you could have been
more helpful as to a solution...I can't get the wifi to pickup dhcp because
I can't configure the mn-500. Hopefully, what annon 1 was saying is that the
mn-500 would handle dhcp for wifi and my main router would handle dhcp for
wired lan?

In response to annon 2: Yes, if only I could configure the unit. I never got
around to posting how I wasn't able to configure. I don't think I actually
took the time to get the snapshots etc until a while had past and I figured
the thread would have been long gone by then so I just blew the whole thing
off.

So guys, HELP!
Hopefully I'm making sense here, if you are confused, please let me know so
I can try to explain better. I really want to get this up again.
I'll be in and out of the office tomorrow but I'll try to get on when I can,
but if anything I'll atleast be able to post after work.
Thanks in advance!

I just skim your posting. A few quick comments.

1- The MN500 cannot be accessed in bridge mode. Reset the
MN500 using the reset hole on the back. The router comes
back in router mode (password is admin). Use IE and go to
http://192.168.2.1 to configure the router. Leave in
router mode -- don't change to switch mode (once you do
that you can't access the configuration of the MN500).

2- You can run the MN500 in router mode using the DHCP.
It will get an IP from the DHCP from the other device and
will provide DHCP to the other computers. Install it
first this way and get everything working (especially
wireless access). You can turn it into bridge mode later,
once everything is working and you have saved the
settings, but keep in mind that once you do it, you can't
reconfigure it anymore without a reset (I have mine in
router mode all the time).

3- When setting the wireless set it without WEP first.
Make sure SSID broadcast is ON -- the MN520 does not work
if SSID is disabled. Once this is working add WEP. Once
WEP is working, add MAC filtering.

>-----Original Message-----
>Okay, a while ago I posted about a problem I was having
trouble trying to
>configure my MN-500.
>My new house has prewired cat 5 so I wanted to setup the
MN-500 for use in
>base station mode. After setting it to basestation mode,
I was no longer
>able to connect to it via 192.168.2.1 or 0.1
>
>Despite multiple resets to the unit I can not configure.
I don't know if
>anyone remembers me posting before but here's a link to
the original thread
>via google groups
>
>http://www.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-
8&threadm=%23TGieMSwDHA.3216%
40TK2MSFTNGP11.phx.gbl&rnum=1&prev=/groups%3Fq%
3Dgroup:microsoft.public.broadbandnet.hardware%
2Bauthor:blackwell%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%
3DUTF-8%26selm%3D%2523TGieMSwDHA.3216%
2540TK2MSFTNGP11.phx.gbl%26rnum%3D1
>
>(here's a recap)
>My notebook has an integrated ethernet and pcmcia mn-520
I've tried
>configing the 500 using both.
>When I try with wifi I'm asked for a wep key
>(http://www.wowcentral.com/random/wifi_error.gif), if I
try with ethernet
>(http://www.wowcentral.com/random/eth_error.gif)
>Now, mind you, without any configuration the mn-500
works fine as a hub if I
>uplink it to our wired lan and I can connect my desktop
and notebook through
>it to connect to other computers and printers
>
>I'm pretty frustrated with the whole thing. I just gave
up last time because
>I had just lost broadband and didn't need it that much
anymore since any
>file sharring between my main and laptop can be done via
quick USB key
>exchange. However, I'm getting DSL on the 1st and I want
to have my wifi
>back again so I can just connect our main router to
internet and be up and
>running.
>
>I don't know WHY it's asking me for a WEP key or why
it's picking up a BAC
>wireless network...unless it's just picking up on the
fact that my hardwire
>lan is on BAC workgroup
>
>
>In response to annon 1:
>I believe he was saying, after I configure everything
again, just leave it
>in router mode and uplink to my hardwire lan? Wont that
screw everything up
>if it tries to use DHCP while our main router is doing
the same thing? it
>sounds iffy to me.
>
>In response to Christ H:
>those ip's were for my wifi cards, ethernet cards were
on 192 etc when I
>connected them to my main lan
>
>In response to Jason Tsang:
>I knew/know that's the problem (on the wifi), I wish you
could have been
>more helpful as to a solution...I can't get the wifi to
pickup dhcp because
>I can't configure the mn-500. Hopefully, what annon 1
was saying is that the
>mn-500 would handle dhcp for wifi and my main router
would handle dhcp for
>wired lan?
>
>In response to annon 2: Yes, if only I could configure
the unit. I never got
>around to posting how I wasn't able to configure. I
don't think I actually
>took the time to get the snapshots etc until a while had
past and I figured
>the thread would have been long gone by then so I just
blew the whole thing
>off.
>
>So guys, HELP!
>Hopefully I'm making sense here, if you are confused,
please let me know so
>I can try to explain better. I really want to get this
up again.
>I'll be in and out of the office tomorrow but I'll try
to get on when I can,
>but if anything I'll atleast be able to post after work.
>Thanks in advance!
>
>
>.
>

actually it can be. see my latest Expert Zone column

On Thu, 26 Feb 2004 01:17:39 -0800,
<(E-Mail Removed)> wrote:

>The MN500 cannot be accessed in bridge mode

--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)

plug the cable into one of the LAN ports and not the modem port on the
500 and try again (see my latest Expert Zone column for info on
accessing the 500 in bridge/access point/base station mode)

On Thu, 26 Feb 2004 00:01:19 -0800, "Robert Blackwell"
<robatwowcentraldotcom> wrote:

>After setting it to basestation mode, I was no longer
>able to connect to it via 192.168.2.1 or 0.1

--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)

"plug the cable into one of the LAN ports and not the modem port on the"

Hey come on now Barb, give me a little more credit here please, I'm not that
obliviou to the obvious.
Anon: I have reset it MANY many times, and I still can't access it.
Either by 192.168.2.1 or 192.168.0.1

If I could just do that, I'd skip the whole MSBN software setup wizard.
Now, since I've reset it, I dont' know what mode is default, but I'd assume
it was routing mode. However, since I can't access it, I figured the wizard
would be the best way.

If you can't get to it, start by eliminating any hardware
or TCP/IP stack problem. Can you still browse the
Internet if the 500 is out of the equation?

Also try pinging the router. After a reset it comes in
routing mode and at 192.168.2.1 -- maybe the cable is
defective or not well connected.

>-----Original Message-----
>"plug the cable into one of the LAN ports and not the
modem port on the"
>
>Hey come on now Barb, give me a little more credit here
please, I'm not that
>obliviou to the obvious.
>Anon: I have reset it MANY many times, and I still can't
access it.
>Either by 192.168.2.1 or 192.168.0.1
>
>If I could just do that, I'd skip the whole MSBN
software setup wizard.
>Now, since I've reset it, I dont' know what mode is
default, but I'd assume
>it was routing mode. However, since I can't access it, I
figured the wizard
>would be the best way.
>
>
>.
>

Well, no because I didn't have broadband at the new house when I moved. I'm
getting DSL activated today so I'll have to see. If it will just distribute
internet via wifi that will be cool, BUT it would be nice if I could still
configure it so the wifi comps can access the wired lan computers and
printers etc.

What do you mean eliminating hardware or TCP/IP stack problem?

I can plug my laptop or desktop into the wall outlet and access the wired
lan just fine with any of the cables. AND if the mn-500 is plugged into the
wall and the computers into it via ethernet, I can access all of my network
resources. So, I doubt it's a wire problem.

Okay, DSL all setup works great on the wired lan, even with my desktop
connnecting to the lan via uplinked MN-500. My deksop has both ethernet and
wifi. Currently, it's connected to the mn-500 via ethernet.

I checked the IP's on my desktop my ethernet is 192.168.0.9 and it's wifi is
192.168.0.11

on my laptop both ips for eth and wifi have APIPA...but that's fine for the
eth cause it's not connected anyway...I know it works so I don't care about
that one.

Any ideas guys?

So, no ideas huh?

You need to restate the problem. I can't tell if you are still trying to
configure the 500 as a bridge or just what the issue is. You've trimmed the
thread and all I see is the single sentence below. As I recall I made one
comment previously and you discounted it as something that was obvious to
you. I'm hesitant to comment further.

Robert Blackwell wrote:
> So, no ideas huh?


--
Barb Bowman
Expert Zone Columnist
http://www.microsoft.com/windowsxp/expertzone
MS-MVP (Windows)