Sign in with
Sign up | Sign in
Your question
Solved

Port Forwarding Not Working

Last response: in Networking
Share
July 24, 2013 4:15:33 PM


Hi,

Something that's never been an issue before is killing me now- I cant port forward!

So I'm trying to port forward a webserver on port 8080 (not 80 because my ISP blocks it).
Canyouseeme.org tells me "Success: I can see your service on xx.xx.xx.xxx on port (8080) Your ISP is not blocking port 8080". Same with the media port 34567. For any ports that I haven't forwarded I get a failure as expected.

Yet when ever I try to connect to xx.xx.xx.xxx:8080 I get an "Oops! Google Chrome could not connect to myiphere"

Now the funny thing is that everything used to be working before I pulled out the router. We have a SMCD3G-BIZ modem and used to have a Linksys Router(connected to it somehow [LAN 1 on modem to WAN on router]) running DHCP. We recently moved to a Windows Server with Domain which handles all the DHCP now so I pulled the router out and set it up as an access point. Boy do I regret that decision. Back when I had the router I could port forward any port! Including the blocked ports such as 80, etc. I don't know why, but it worked! My suspicion is that the ports were blocked only through the firmware on the modem.

Now I can't portforward anything and all surveillance systems and order processing software is offline- something we need to get fixed ASAP.

I really dont know how the router and modem were set up before, weather if the modem was acting a "dumb" modem or something, or if even DMZ had anything to do with it, I really dont know. The modem was setup by a IT guy that was long gone.

I really appreciate any help as this problem is really problematic for us.


Thanks again,
Sam



PS: sorry for the long post
July 24, 2013 5:08:49 PM

What device is the windows server running HTTP currently plugged into?

Are you going directly into the SMC?
July 24, 2013 6:22:12 PM

vnet said:
What device is the windows server running HTTP currently plugged into?

Are you going directly into the SMC?


The server is connected to a switch, which is connected to a switch, which is connected to the SMC.
Related resources
July 24, 2013 6:42:16 PM

And you have gone into the NAT section of the smc and configured port forwarding from there? If so, what is the config you have
July 26, 2013 5:03:51 PM

vnet said:
And you have gone into the NAT section of the smc and configured port forwarding from there? If so, what is the config you have



Yes, I have tried that. It still does not work.

Here's a screenshot:

Thanks for the help btw- I really appreciate it!

Best solution

July 27, 2013 7:11:30 AM
Share

Can you access the http server internally? http://192.168.1.111:8080
July 27, 2013 7:59:19 AM

vnet said:
Can you access the http server internally? http://192.168.1.111:8080


Hi Vnet, thanks so much for the help on the issue.

Thankfully I was able to get the issue resolved on another forum.
To those who are interested on seeing the outcome, the other thread is available here.

Thanks again!
Sam
!