No internet with surten user account (
-
Yeah. And you need to fix that first. It works for everyone. If it does not work for you, then you are doing something badly wrong. When totally basic things don't work, there's no point in making things more complicated with CPs, proxies or whatever.
-
That's the part where i'm stuck :-)
Excuse me in advance for my questions but i'm not familiar with pfSense and because even only rebooting results in no internet its hard for me to find where the problem is. Especially the configuration isn't changed, the only change there was made was an update and so i'm not sure if it is an configuration error or an problem due the update.You would assume that when the LAN-interface in pfSense has the correct subnet everything would work but now its the opposite: there's internet but surten accounts (domain users with no install rights) have an proxy error, although they can ping to both an IP and URL.
Yeah. And you need to fix that first. If works for everyone. If it does not work for you, then you are doing something badly wrong.
-
There is no information here to debug anything. What does "no internet" mean? Can you ping the pfSense box from LAN by IP? Can you ping it by hostname? Can you ping say 8.8.8.8? Can you ping www.google.com? Once again, get all proxies and everything else out of the way until you have basic things working!
-
Hi
When i change the subnetmask in the LAN-interface from pfSense, it works until I reboot. In the console the subnetmask is only updated after reboot.
I'm able to ping to 8.8.8.8 (from the pfsense console)
Not to www.google.com for example (from the pfsense console)There is an DNS forward to 192.168.0.2 (Windows server) yet for one or other reason the server and every host can't ping (no ip, no url). Despite the fact this does work if the lan interface on pfsense has the previous subnet and without rebooting pfsense.
Thanks in advance for your efforts and patience :)
-
We have not moved an inch further since this thread started…
You need to get basic setup working properly before trying anything advanced.
Suggest to get a paid support - https://www.pfsense.org/get-support/
-
I'm sincerely trying to explain my case and being thankful for your efforts.
I really don't understand what you mean, maybe thats because English is not my native language(?).
The configuration worked more then a year without any problems. In march the same error occurred saying the proxy server doesn't respond or isn't active with the domain-account from the students. There was and is no proxy-server configured. When that error occurred just rebooting pfsense solved the problem, pinging to an url or ip does work though. The installation of pfsense was done by someone else with help that doesn't does this work anymore.Now, couple weeks later the current scope in Windows Server was erased and replaced by one with an bigger range and ofcourse other subnet. On pfSense everything worked fine at first but then the LAN hadn't any internet anymore (no pinging possible to url and ip from lan side and no pinging to url from pfsense console). Recovering an previous configuration from file solved the problem.
So my problem now is that when pfsense is rebooted there isn't internet at all (hosts on lan side can't ping to an url or ip) and pfsense can only ping to an IP. It has something to do with resolving DNS and the forwarding to the server i think but i can't find what specifiek setting it is. Besides: i have the impression that maybe the update i've first did before changing the IP range has caused an error or problem in pfsense although I can't determine if this has something to do with my problem.
Paid support is to expensive for our school, thanks for the advise though :)
Thanks for the efforts. -
I damn mean that your should reset your firewall to factory defaults, reconfigure WAN and LAN from scratch and should NOT move to anything else until you get absolutely basic barebones functionality working. Until you have either /20 or /24 or whatever else matching and working on your LAN and on your pfSense. Noone cares about what's your beef with Windows server. Why are you even forwarding any DNS there when the absolute basics stuff that works out of the box after 1 minute work on every other pfSense install does not work for you.
Ditch the current mess. Back to basics.
-
dude if you change pfsense lan mask, your clients have to have the same mask or no you won't be able to talk to pfsense to do anything.
If you want pfsense lan to be /20 – for the life of me I can not fathom needing such a large mask for a segment.. Do you really have plan on putting 4k some devices on the same segment?? Really?
What I would suggest you do is do a clean install, let pfsense come up with its defaults.. Then if you change your mask on pfsense, then reboot. Your machine either needs to get this new mask from pfsense dhcp or you have to set it on your machine your wanting to use pfsense from.
But your lan segment and your machine on the lan segments masks have to match or your going to have a hard time!!
-
I see that there is an error with opening 'Proxy Server'.
Probably something went wrong while updating.
I will search a way to fix this and look if the problem still occurs.I'm sincerely trying to explain my case and being thankful for your efforts.
I really don't understand what you mean, maybe thats because English is not my native language(?).
The configuration worked more then a year without any problems. In march the same error occurred saying the proxy server doesn't respond or isn't active with the domain-account from the students. There was and is no proxy-server configured. When that error occurred just rebooting pfsense solved the problem, pinging to an url or ip does work though. The installation of pfsense was done by someone else with help that doesn't does this work anymore.Now, couple weeks later the current scope in Windows Server was erased and replaced by one with an bigger range and ofcourse other subnet. On pfSense everything worked fine at first but then the LAN hadn't any internet anymore (no pinging possible to url and ip from lan side and no pinging to url from pfsense console). Recovering an previous configuration from file solved the problem.
So my problem now is that when pfsense is rebooted there isn't internet at all (hosts on lan side can't ping to an url or ip) and pfsense can only ping to an IP. It has something to do with resolving DNS and the forwarding to the server i think but i can't find what specifiek setting it is. Besides: i have the impression that maybe the update i've first did before changing the IP range has caused an error or problem in pfsense although I can't determine if this has something to do with my problem.
Paid support is to expensive for our school, thanks for the advise though :)
Thanks for the efforts. -
Ok. Which part of get the fsckin' basics working is sooooooooooooo hard to get?!?!
Noone cares about your proxy. Fix your /20 first!!! It's like having a house without roof, with foundation floating on sand and caring about wall decorations. WTF!!! >:( >:( >:( >:( >:(
-
If that doesn't work i will follow your advise and start from scratch, i wanted to avoid this because it worked more then an year without problems.
Thanks for the advice.
-
Dude your really started get on dok's nerves it seems ;) Which I enjoy very much!! He is fun as all hell when he gets perturbed by stupidity..
Dude how hard is it to setup the same mask on both your pfsense interface and the rest of your network.. This is basic 101 stuff that really needs to be done before you start playing with proxies and shit..
-
I know but like i've said: when i do that and reboot pfsense then there's no more internet (no pinging from lan side to both url and ip) and no pinging to url from pfsense console. Thats why i assumed there maybe is another problem in pfsense.
Beginning from scratch could indeed ruled that out but i wanted to avoid resetting. As i get an error when loading i think that that should be solved and could be related but that will be something tot test later on.
Thanks though and i will follow your advise after getting pfsense fully functional without errors (that are not related to configuration but packages etc, or so it seems)
-
Beginning with an new configuration from scratch is what i didn't want to do.
I partly followed the above advise by resetting the firewall but in stead of building everything from scratch I uploaded the configuration file i exported before updating pfsense. For me that made sense because the previous configuration worked for two years (i thought one but i saw it worked 2) and so the only thing that had to be changed was the LAN-subnetmask (like you can read in previous posts: i already knew that but after rebooting pfsense it didn't work at all).
The problem with rebooting and pfsense not working anymore was solved after resetting en uploading my configuration file but the proxy error not. This was solved by installing squid3 (it first installed squid, the package that was used in the past).
Thanks for the help.
