Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4459
  • Last Modified:

RV042 Port Forwarding Issue

I have a Linksys RV042 router which I cannot configure to allow incoming tcp traffic on port 80 or 443 but have other ports forwarding and functioning fine.

-forwarding PPTP traffic on port 1723, this is working great.

-forwarding HTTP on port 8080 and confirmed external connectivity, by hitting a test site on an internal IIS server.

-I have changed the remote management port of the RV042 to 8081.

-Attempting to allow port 80 for HTTP and 443 for HTTPS but am unable to open, the forwarding rules themselves are entered into the web UI and no errors are evident.

-All forwarding rules are being configured through the web UI under "Setup" --> "Forwarding".

-Built-in Firewall, SPI, DOS, Block WAN, Remote Management, HTTPS are all enabled.

Any help would be greatly appreciated!
0
joefreedom
Asked:
joefreedom
  • 2
1 Solution
 
Kerem ERSOYPresidentCommented:
Hi,

Did you try to change the management ports to a different ports? S0nce normally LinkSys would be using these ports to accept management connesctions sowould not allow them to be directed inside with reverse NAT. Try ro modify managemnt interface to toer ports like 81 and 4444 instead of 80 and 443.

Cheers,
0
 
joefreedomAuthor Commented:
Changed management port to 81, saved config, tested... 80/443 still closed, 81 open.
Changed management port to 4444, saved config, tested... 80/443 still closed, 4444 open.

Ok, I changed mgmt port to 4444, saved configuration, then I disabled Remote Management to see if it would close 4444.

To my surprise, 4444 is still open!? and of course 80/443 are still closed.

*Running Firmware Version: 1.3.12.6-tm
0
 
joefreedomAuthor Commented:
Ok...

So my last post got me thinking after I re-read it...why not set the remote management port to 80, then disable it, re-create your forwarding rule and test functionality.  Sure enough...port 80 is now open, wow ok...

So I thought what the heck, lets try this again with 443...cleared my 80 forwarding rule and my 443 forwarding rule, set the remote management back to enable, set the remote management port to 443, disabled remote management, recreated my 443 forwarding rule, tested, and what do you know it didn't work....

But 80 is still open?! (which i'm happy about, but have no idea where the logic is in any of this...)

So now apparently only 443 is the one that won't forward...I will play around with this more tomorrow...any ideas or suggestions would be appreciated.

Thanks.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now