Archive > 19.1 Legacy Series

NAT - Port Forward not working from Windows PC's

(1/3) > >>

WJScott:
Odd situation...

I have setup a NAT/PF that redirects port 4433 to 443 for the dashboard UI so that I can access it externally (This is a personal setup). The odd thing is that from my phone Android/Chrome I can access it.
Trying from 2 different laptops (One Corporate controlled and the other personal) I am not. I have tried IE, Chrome, Opera and Firefox browsers to no avail.

What is going on?
Any help would be appreciated!

WJScott:
and for clarity, I have also tried to the do this for RDP using an alternate port inbound and redirect it to 3389 to no avail.

WJScott:
This is baffling!

I've inserted a NAT to redirect 3389:

-Interface:                                WAN
-TCP/IP Version:                      IPv4   
-Protocol:                               TCP
-Source:                                 Any
-Source port range   
                     from:                MS RDP
                     to:                MS RDP
-Destination:                          WAN Address
-Destination port range   
                     from:                MS RDP
                     to:                MS RDP
-Redirect target IP:                 192.168.0.240
-Redirect target port:              MS RDP
-NAT Reflection:                      Enabled (Have tried disabled also)
-Filter rule association:            Yes

Automatic Rule Created:
-Proto:                                    IPv4 TCP
-Source:                                  *(Any)
-Port:                                      3389(MS RDP)
-Destination:                           192.168.0.240
-Port:                                      3389(MS RDP)
-Gateway:                               *(Any)
-Schedule:
-Description:                           NAT

With the above F/W rule the attempt is denied:

__timestamp__   Jul 3 15:30:53
ack   
action    [block]
anchorname   
datalen   0
dir    [in]
dst   192.168.0.250
dstport   3389
ecn   
id   53827
interface   em0
ipflags   DF
label   Default deny rule
length   52
offset   0
proto   6
protoname   tcp
reason   match
ridentifier   0
rulenr   3
seq   2596550757
src   174.228.133.87
srcport   1240
subrulenr   
tcpflags   S
tcpopts   
tos   0x20
ttl   110
urp   64240
version   4

Create a manual rule:
-Proto:                                    IPv4 TCP/UDP
-Source:                                  *(Any)
-Port:                                      *(Any)
-Destination:                           192.168.0.250
-Port:                                      3389(MS RDP)
-Gateway:                               *(Any)
-Schedule:
-Description:                           

Nothing gets entered into the log with the manual rule enabled, disable it and the deny continues?
I dont see how this could be expected behavior, help?

WJScott:
WOW!

Not sure what else to say!
Its been multiple months and over 100 have read the thread but not one contributor to help me resolve the issue.

tong2x:
you are redirecting to itself?
whats whit the 4433 and 433?
based on the rules you created it was never used?

to open a port goto
Firewall: NAT: Port Forward
disabled: unchecked
interface: {your wan interface}
TCP: ipv4 or 6
Protocol: TCP
Destination: {This firewall}
destination port range: what ever ports you want to open ex. external ports 4433
redirect target ip: {internal IP, ex 192.168.0.240}
redirect port: {it not the same with external... ex http or 80 if an internal webserver)


Firewall: NAT: Port Forward EXAMPLE a webserver
disabled: unchecked
interface: {WAN1; your wan interface}
TCP: ipv4 or 6
Protocol: TCP
Destination: {This firewall, or ip of firewall}
destination port range: 99 (what ever ports you want to open)
redirect target ip: 192.168.0.240 {your target internal IP or internal server ip}
redirect port: 80 {becuase it is a webserver)

Navigation

[0] Message Index

[#] Next page