Browsing website problem
-
Either:
- Put an entry in your internal DNS for www.MyCompany.org that translates to the internal (private) IP address of the web server (10.0.0.2) - then internal users will go straight there internally; or
- System-Advanced-Firewall/NAT - enable NAT reflection, to get pfSense to "turn around" those accesses to the external public IP.
-
thank you for fast reply,
actually i did that also, on DNS server i put *.mycompany.com and www.mycompany.com and i uncheck the NAT Reflection for port forwards but nothing changed, also before minutes i connect a laptop directly to webserver and i try to browse, and the same thing appear "the main page appear but messy" .
what should i do now?? :( :(
-
You should NOT uncheck the NAT reflection.
-
Confusingly you should uncheck the box because unchecking it enables NAT reflection. ;)
(the box, in System: Advanced: Firewall/NAT:, is labelled 'disable NAT reflection')Then reset the firewall states (or reboot).
Steve
-
Confusingly you should uncheck the box because unchecking it enables NAT reflection. ;)
(the box, in System: Advanced: Firewall/NAT:, is labelled 'disable NAT reflection)Call me confused… No such thing on 2.1 :D
-
Ouch even more confusing. ::)
In 2.0.3 it's the inverse! It's far more configurable in 2.1 so I guess a lot changed, not unreasonably.Steve
-
thank you everyone.
this is what i did "remove the check box", but as i told you nothing changed and the website still not working from inside company.
-
Did you reset the firewall states/reboot?
Steve
-
yes i did, but i found other issue, the DNS server can't see the webserver, i tried to bing from DNS and the result was "request time out". but the webserver can see DNS server.
DNS server 192.168.1.2 mask 255.255.0.0
web server 10.0.0.2 mask 255.255.255.0so how can we fix that??
-
So you're not using pfSense for DNS then?
Have you flushed any DNS cache, locally or at the server?
If you ping the web server by URL what address does it try to ping?Steve
