Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 2 subscribers
  • Views 11916 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Accessing internal website on external IP

mronald87
I think I'm missing a few steps here in creating a NAT to access a internally hosted website externally.

Here's what I have so far:

I've told our ISP to designate an external address for us (78.x.x.59). When a smartphone application connects to that address, I want them to access 10.62.149.115 internally. 

I've set up a DNAT Accordingly:

Traffic Source: Any
Traffic Service: Any
Traffic Destination: External (78.x.x.59) 
NAT Mode: DNAT
Destination 10.62.149.115
Destination Service: HTTP (1:65535 -> 80)
Log initial packets: yes
Automatic packet filter rule: yes

Whenever anyone externally tries to access the 78.x.x.59 address, nothing happens. I don't see it logged on the packet filter log. I can also ping 78.x.x.59 as well as its DNS, but when I traceroute it, it times out after about 15 hops on some unknown address. Our firewall external address is 78.x.x.60. Do I need to somehow include the firewall external address in this DNAT setup?


This thread was automatically locked due to age.
Parents
  • 0
    Another bit of information: I can ping the 78.x.x.57 address from an external workstation, but when I do a traceroute, if fails on about 15 hops at some unknown address. I don't know if that helps anybody.
Reply
  • 0
    Another bit of information: I can ping the 78.x.x.57 address from an external workstation, but when I do a traceroute, if fails on about 15 hops at some unknown address. I don't know if that helps anybody.
Children
No Data