What Am I Missing? Port Forwarding/Websites not working New to Networking.
-
Why would you create another thread? Moving this to the first thread you started.
-
@johnpoz Didn't do it on purpose, sorry
-
@gertjan Everything else works but access to my ISP website and email. I can access any other website. It doesn't matter what I do, I don't have access to my isp email or website after a clean install with no config changes. I have firewall rules for my cctv equipment and that works fine now. I have a regular arris cable modem, none of that wireless/cable/router combo garbage. It seems like maybe a dns issue? I can ping it from the router, tracert from windows "unable to resolve target"
-
And what is this fqdn your trying to resolve.. Here is the thing its possible that your mail server doesn't resolve on the public, and the only way to resolve it is if you use their DNS... This is freaking HORRIBLE design... But if that is the case you would just need to create a domain override pointing the domain your fqdn of your mail server is to your isp NS..
Out of the box pfsense resolves.. so if your isp is only allowing its mail server or website to resolve from their NS then yeah that would fail.
Post up the fqdn of this mail server and website your trying to access and will tell you for sure if it resolves on the public or not.
Is it something like smtp.yourisp.com or www.yourispdomain.com
-
Forgive my ignorance, I don't understand what you are asking for. Are you asking for the mail server? The mail server is mail.echoes.net port 993. Their website, adamscable.com.
-
@itstheburns said in What Am I Missing? Port Forwarding/Websites not working New to Networking.:
mail.echoes.net:993 adamscable.com.
Those work fine from here.
What do you have DHCP configured to give to your clients? What are that windows client's active DNS servers?
What does
nslookup mail.echoes.netoutput? -
Yeah exactly
That resolves just fine
;mail.echoes.net. IN A ;; ANSWER SECTION: mail.echoes.net. 3600 IN A 72.28.1.14 mail.echoes.net. 3600 IN A 72.28.1.13And so does
;; QUESTION SECTION:
;adamscable.com. IN A;; ANSWER SECTION:
adamscable.com. 3600 IN A 72.28.3.145If you can not resolve it, then you dicked with the settings or your ISP is dicking with your ability to resolve.. Out of the box pfsense resolves, ie talks down from roots to find the authoritative NS for the domain your asking about.
If your ISP messes with that, or your latency is too high then yeah you could have problems.
Port 993 is encrypted IMAP.. If you did did not change the default lan rules any any is allowed. And prob just a DNS problem.. Go to pfsense dns lookup does that resolve? Can you please post the output of this screen
-
Same for me.
It works just fine outside of my network with pfsense. It works just fine if I connect my old router.
I got it working. I added 8.8.8.8 and 8.8.4.4. I kept glossing over this page for some reason and missed DNS Servers.
I don't know why they have their dns setup the way it is and I don't know why it works fine with my asus router but its working now. If theres a better or different way, I'm open to learning how to do it.
-
Great. What about resolving on the CLIENT that is failing?
nslookup mail.echoes.net -
Yeah its working. tracert as well to both mail.echoes.net, echoes.net and adamscable.com.
-
OK then what about in the browser? What does it say exactly when you try to go to adamscable.com?
-
It loads the page as it should, on all devices
-
So what's the problem?
-
No problem now, its all working as it should. I added google's dns servers to the dhcp server page.
@itstheburns said in What Am I Missing? Port Forwarding/Websites not working New to Networking.:
I got it working. I added 8.8.8.8 and 8.8.4.4. I kept glossing over this page for some reason and missed DNS Servers.
I don't know why they have their dns setup the way it is and I don't know why it works fine with my asus router but its working now. If theres a better or different way, I'm open to learning how to do it.
-
Without any idea what the non-working setup looked like it's really hard to say.
-
The original issue was that I could not get port forwarding to work with my camera NVRs (2 of them), some websites were slow or not loading and could not access my ISP's website and email.
I had port forwarding setup in the wrong order or something. I reinstalled pfsense and redid all of the port forwarding rules after I found a very detailed video that basically explained firewall aliases much better than the pfsense documentation. That made setting up my port forwarding so much easier and took only 5 mins Port forwarding is working as it should and lightning fast compared to before.
As for my ISPs website or email not working, I was not able to access those from within my network on any client, whether it be PC or mobile device. It all worked fine on my asus router before I started using pfsense so I was stumped. My ISP is probably doing some wonky stuff with resolving or whatever. By adding Google's DNS servers has fixed this issue. Nothing else I tried was able to fix it. I would only change one setting at a time, apply and retry. If that did not work, I would revert back and try a different setting.
In short, everything seems to be working on every client both within and outside my network.
