Re: Can't get port forwarding to work (LinkSys)

From: Randell D. (randelld@com.yahoo)
Date: 07/24/02 

From: "Randell D." <randelld@com.yahoo>
Date: Wed, 24 Jul 2002 21:15:03 GMT

I use a similar LinkSys Router and I was able to get port forwarding working
so I'm pretty sure you've just configured it wrong... I have since disabled
my router, so some of the detail below may not be 100% clear...

First... you say you tried to ping your routers WAN connection but it
failed... there is a feature in the control panel that allows you to switch
this on or off... I think its something called Stealt Mode - My
understanding is that it can respond to the ping packets or not, pending if
its disbabled or enabled... so you could try changing the settings... Go to
your Routers main config menu, then take the Advanced menu setting,
highlighted in orange on the top right... Open the window for Filters... and
page down... There, you should find settings for SPI, Block WAN Request,
Multicast Pass Through, IP Sec Pass Through, PPTP Pass Through, Remote
Management, Remote Upgrade, MTU.... I have Block WAN Request Enabled (to
prevent any response to a ping) and everything else Disabled. Earlier this
week I downloaded a newer version of their firmware and there is a note
about this router, Outlook/Outlook Express timeouts, and the MTU value - I
have not had problems with my mail clients and have not followed the
isntructions, but you might want to have a peek... I think it relates only
to Verizon DSL customers... check out the note at
http://www.linksys.com/support/support.asp?spid=87

Okay - if you Disable the Block Wan Request, you should find that you can
ping the router... so try that first... just to make sure everything is as
you believe...

Next...

Under the Forwarding tab (again, found from the Advanced Menu) I had put the
following values in

Customized Applications: SSH
Ext Port: 22 to 22
Protocol TCP: Ticked
Protocol UDP: Clear
IP Address: The local private network address (mine was 192.168.1.78)
Enable: Ticked

If I remember correctly, I also had problems like you encountered, however,
I went one step further which might be the solution for you too... Click on
UPnP.. I do not know what UPnP stands for (User Point to Point or something,
can't believ its Pug and Pay, is it?) Anyway, again, these were the values
I HAD in place for UPnP Forwarding in one of the free user setting boxes
(under the one that says SNMP you can put in your own)

Application Name: SSH
Ext. Port: 22 (External Port)
Protocol: TCP
Int. Port: 22 (Internal Port)
IP Address: 192.168.1.78 (the local private network address that I used,
yours might be different)
Enable: Ticked

And... after applying that... there is one important, but hidden box you got
to check...

Click on the Setup tab (ie you are moving out of the Advanced menu back to
the menu you get when you first enter the router config - the Advanced /
Setup option toggles so it is the right hand side of your browser)...

Here is what I think LinkSys don't want you to know... Click on Password...
and for some reason or other... under the fields that allow you to reset the
password are to boxes, one for UPnP Services (which you might want to
enable) and the other for Restore Defaults...

If you do enable UPnP Services - remember to re-enter your password, because
clicking apply to this screen might reset your password to something
cryptic...

Give that a try and see how she goes okay?

Oh! and Enable the logging feature as it might tell you if you are managing
to come in on the port or not... its basic info, but it could help steer you
in the right direction...

Now that I've gone and written this long speil... remember to consider the
security aspects of what port forwarding can do - Might I suggest you port
forward to a port higher than 1024 on your Linux box - I believe port
greater than 1024 won't give a hacker root access... I can't be 100% sure on
this though...

anyway - best of luck... and remember to consider downloading the latest
Firmware from Linksys that came out in the past few weeks before you go to
the hassle of changing your routers existing config (since new firmware
deletes the older config)

regards
randelld
at yahoo.com

"Scallica" <scallica@hotmail.com> wrote in message
news:H_mV8.36476$7e2.804951@news4.srv.hcvlny.cv.net...
> Disable SPI. Port Forwarding does NOT work when SPI is enabled
> .
> "Robert Oschler" <Oschler@earthlink.net> wrote in message
> news:daFU8.39628$N8.41106756@e3500-atl1.usenetserver.com...
> > I have a LinkSys BEFSR41 router with some Windows boxes and one Linux
box
> > behind it. I want to use the Linux box as a destination for a Port
> > Forwarding operation. I setup the Linux box with a static IP address
and
> > verified that it worked, it did. I put an entry into the LinkSys
router's
> > Port Forwarding table for the desired port range, and put the Linux
box's
> > now static IP address in as the destination.
> >
> > When I try to access the Linux box through a client external to the
> router,
> > I fail to connect. Here's how I run the test:
> >
> > On the Linux box I start the server program that listens for any
incoming
> > connection on the port # entered into the router's port forwarding
table.
> I
> > know this program works because other sibling stations on the LAN behind
> the
> > router can connect to it without problem.
> >
> > Using a computer with a dial-up connection which is running a custom
> TCP-IP
> > client program, I enter the LinkSys router's WAN IP address and the port
> > number I entered into the Port Forwarding table, into the Connect
settings
> > field of my test client program. (Note: this program connects fine with
> > other stations on the LAN.) The connection fails with a 10060 error.
> >
> > I tried pinging the router using its WAN IP address, but the request
timed
> > out and I'm guessing its because the router doesn't respond to pings for
> > security reasons. I know the WAN IP address is valid, because if I
> connect
> > to the dial-up station FROM a system behind the router, the router's WAN
> IP
> > address shows up as the IP address of the connecting client.
> >
> > Any ideas? I tried this with DHCP disabled on the router and with it
> > enabled, didn't work in either configuration.
> >
> > thx
> >
> >
> >
>
>

Relevant Pages

  • Re: Remote Assistance not working
    ... Using Remote Assistance to Get Help When You Need It ... Should I disable the NAT on the modem/router to allow the wireless router to ... using port forwarding makes it work that's one of those times. ...
    (microsoft.public.windowsxp.general)
  • Re: Using Remote Desktop From an SBS Domain
    ... when you tried to RDP while attached directly to a port on your router? ... So if 3389 needs forwarded on the client end too then that is what the ... Hopefully next week I can attempt a connection while my ISP watches the ...
    (microsoft.public.windows.server.sbs)
  • Need HELP on Configuration for access freeBSD webserver from Local LAN...
    ... Need help on config. ... to access freesbsd webserver ... 2 DSL router, ... set virtual server port 21,23,8080 address? ...
    (freebsd-questions)
  • Re: Remote Assistance not working
    ... Should I disable the NAT on the modem/router to allow the wireless router to ... using port forwarding makes it work that's one of those times. ... internet with a cable modem and DSL modem. ...
    (microsoft.public.windowsxp.general)
  • Re: RWW interal not external
    ... SBS Standard, one NIC, no ISA. ... I have set the port forwarding on the router as best I can. ...
    (microsoft.public.windows.server.sbs)