Persistent Port Forwarding (MN-700) - remotely connecting to Base Station /

Ok, so if I hit a port outside using a differnt ISP
outside my LAN I can see the ports forwarded. The only
thing I cannot do with the MN-700 that I could with all
other wireless routers is to connect to the base station
remotely (192.168.2.1) - That IP is locked down somehow.
Has anybody been able to access the base station remotely
so you can reset it or make changes?

Also, I am using one of the MN-700's as a access point.
The device connected to that is a Tivo box using one of
the 4 ports in the back of the base station. The access
point regularly becomes unaccessible and reaching the
Tivo is impossible remotely or within the LAN without
rebooting both the MN-700 and Tivo device (Linux desktop
that uses a IP address, otherwise just like a Windows
client desktop for instance).

Please email me if you have answers to either of these
issue @ (E-Mail Removed) and I'll ship you a set of
Billy-Bob Teeth (as seen on http://www.faketeeth.com )

Thanks,

Jeff
>-----Original Message-----
>If everything seems to be set up properly, then I imagine
>you are experiencing the same problem as me. If I hit my
>server from outside of my lan, then it works. However,
if
>I hit my server from inside my lan, it just times out.
>It looks like a bug (to me anyway).
>Looking at this forum, there seems to be many others with
>the same problem. Who knows if it will ever be
addressed.
>
>>-----Original Message-----
>>Both the wired and the wireless portions of my MN-700
are
>>working fine. Cable modem is sharable by all networked
>>devices. All is swell.
>>
>>Next step, however, is to enable SSH (port 22) and HTTP
>>(port 80) port forwarding.
>>
>>The machine that I would like to have receive these
>>requests is a RedHat9 Linux OS, configured on my LAN as
>>192.168.2.80
>>
>>All other devices on my LAN use DHCP.
>>
>>I have made four entries in the "persistent port
>>forwarding" table of my MN-700:
>>
>>Two for port 80 (TCP + UDP), and two for port 22 (TCP +
>>UDP) -- all directed to the same 192.168.2.80 IP
address.
>>
>>I see not the slightest sign of any port forwarding
taking
>>place, however. No response when I point a browser at
the
>>WAN-side IP address. No response when I aim an SSH
client
>>at the WAN-side IP address either.
>>
>>Both SSHd and httpd are working fine on the LAN side. I
>>can reach both servers from the non-routable, local
address.
>>
>>Any guidance from someone who's accomplished this?
>>
>>
>>.
>>
>.
>

You cannot access the Base Station Management Tool from outside of your
network (i.e the Internet).

You can remote desktop into your network (if you have the appropriate OS)
and then from the remote desktop session access the BSMT.

--
Jason Tsang - Microsoft MVP

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

"Jeff" <(E-Mail Removed)> wrote in message
news:248a01c41b46$0c130410$(E-Mail Removed)...
> Ok, so if I hit a port outside using a differnt ISP
> outside my LAN I can see the ports forwarded. The only
> thing I cannot do with the MN-700 that I could with all
> other wireless routers is to connect to the base station
> remotely (192.168.2.1) - That IP is locked down somehow.
> Has anybody been able to access the base station remotely
> so you can reset it or make changes?
>
> Also, I am using one of the MN-700's as a access point.
> The device connected to that is a Tivo box using one of
> the 4 ports in the back of the base station. The access
> point regularly becomes unaccessible and reaching the
> Tivo is impossible remotely or within the LAN without
> rebooting both the MN-700 and Tivo device (Linux desktop
> that uses a IP address, otherwise just like a Windows
> client desktop for instance).
>
> Please email me if you have answers to either of these
> issue @ (E-Mail Removed) and I'll ship you a set of
> Billy-Bob Teeth (as seen on http://www.faketeeth.com )
>
> Thanks,
>
> Jeff
> >-----Original Message-----
> >If everything seems to be set up properly, then I imagine
> >you are experiencing the same problem as me. If I hit my
> >server from outside of my lan, then it works. However,
> if
> >I hit my server from inside my lan, it just times out.
> >It looks like a bug (to me anyway).
> >Looking at this forum, there seems to be many others with
> >the same problem. Who knows if it will ever be
> addressed.
> >
> >>-----Original Message-----
> >>Both the wired and the wireless portions of my MN-700
> are
> >>working fine. Cable modem is sharable by all networked
> >>devices. All is swell.
> >>
> >>Next step, however, is to enable SSH (port 22) and HTTP
> >>(port 80) port forwarding.
> >>
> >>The machine that I would like to have receive these
> >>requests is a RedHat9 Linux OS, configured on my LAN as
> >>192.168.2.80
> >>
> >>All other devices on my LAN use DHCP.
> >>
> >>I have made four entries in the "persistent port
> >>forwarding" table of my MN-700:
> >>
> >>Two for port 80 (TCP + UDP), and two for port 22 (TCP +
> >>UDP) -- all directed to the same 192.168.2.80 IP
> address.
> >>
> >>I see not the slightest sign of any port forwarding
> taking
> >>place, however. No response when I point a browser at
> the
> >>WAN-side IP address. No response when I aim an SSH
> client
> >>at the WAN-side IP address either.
> >>
> >>Both SSHd and httpd are working fine on the LAN side. I
> >>can reach both servers from the non-routable, local
> address.
> >>
> >>Any guidance from someone who's accomplished this?
> >>
> >>
> >>.
> >>
> >.
> >