• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 774
  • Last Modified:

port forwarding problem

hi,

I have ADSL router with public ip address, I did the port forwarding for port 80 to redirect to IIS in a web server in case client put my public ip address in his browser and its working fine.

now, the company brought another device which can be controlled and configured in a web portal,
so when I click 192.168.1.75:90 I can view the web based application for that device,
my manager asked that he wants to view this from his home, so when he just put the public ip address and port 90 he would view the web portal of that device ((98.45.x.x:90))


I did that but its not working, I couldn't view the web application of the device, but its working fine for port 80 !

((98.45.x.x:80)) is working and pointing to iis server but ((98.45.x.x:90)) is not working!


so how can I solve that?
0
njgroup
Asked:
njgroup
  • 3
  • 3
  • 2
1 Solution
 
Anton74Commented:
To clarify, the 2nd device is listening on port 90 instead of the standard port 80?

The port forward for this device is going to the right IP? And the IP is static?
0
 
njgroupAuthor Commented:
yes, I have modifies the port, it was 80 but I changed it to 90 so the ADSL router will point to that device

(I have test it on browser 192.168.1.38:90 and it works in LAN)
0
 
Anton74Commented:
In your original question you mention testing it on 192.168.1.75:90, and now you mention testing it on 192.168.1.38:90 - is the IP on this device dynamic (assigned through DHCP)? Or has it been changed by you?

For the port forward to consistently work, you want the IP to be static (unchanging) - either a static configuration on the device, or a DHCP reservation will do the trick.

Once the device has its IP statically fixed, ensure the port forward on the router points to this IP. Is this the case?
0
What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

 
njgroupAuthor Commented:
sorry, its 192.168.1.75:90, I wrote other ip in my mind by mistake, but its 192.168.1.75:90 and the 192.168.1.38:90 is written by mistake
0
 
Anton74Commented:
Does the device have any ACLs that restrict access to the web interface (e.g. local subnet only)?

Can you post a screenshot of the port forward settings on the router?
0
 
njgroupAuthor Commented:
I can confirm the device ip is static (192.168.1.75:90) and the ADSL has public static ip address ((98.45.x.x:90))

but its not working
0
 
kbireckiCommented:
One more confirmation:  Can you access the device "inside" the network on port 90?  If not, then you need to verify this works correctly first.  And as Anton74 suggested, the device may have restrictions to only accept connections from an internal subnet.  These two points really need to be resolved and verified first before continuing.

Another idea: If I understood you correctly, there is a "first" device that works correctly on port 80, correct?  If so, are they the same?  Can you use that as a model to verify the config on the second device?

Also, if there is one working device and one non-working device (same or different, does not matter), can you temporarily swap the port assignments.  In other words, change the first device on port 80 to respond on port 90, and vice versa on the second.  Then change the ip addresses to which each port forward rule points to on your firewall and see if the problem follows the device or the port forwarding on the firewall.  Basically you are checking to see if the problem is in the firewall or in the device's config.

Hope that helps some.
0
 
kbireckiCommented:
Did you get any resolution to this issue?
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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