WAN connected after default install, but no access from LAN
-
Someone else will have to help with the Windows setup because I don't have that sort of experience.
I'd setup pfSense to act as the DNS server and DHCP server but I'm not aware of the implications of that for your particular requirements.
pfSense has a single configuration file (including DNS and DHCP configuration) that is easily backed up so its pretty easy to get a pfSense system running again after (say) a hard drive problem and it can probably be done a lot more quickly than restoration of a Windows server. This could be an important consideration if (say) your Windows server has some sort of problem preventing it booting and you want to surf the internet for clues about suitable recovery action. If you are relying on the Windows server for DHCP and DNS you'll need some special inspiration to surf the net looking for a solution.
-
DHCP being moved to something else is perfectly alright _, but regarding Windows DNS I don't have the slightest clue. Looks like I'm going to have to phone up someone.
Thanks a million though._
-
After reading and looking at the network diagram I would recommend letting your pfSense box do the dns and dhcp. If the Win2k3 ain't doing anything but dns and dhcp it's wast of power imo.
As you are non profit it could be a solution for you.
Free email
Free websiteJust my 2 cent.
-
Is it possible to let pfsense handle the dns? Even if the dns box is also providing AD and PDC? Where would I find information on how to do that?
Many thanks for the links dude :)
-
Then it's correct to use win2k3 for DNS when AD is in play.
Is the DNS server ip's correct in Windows Server DNS Forwarders?
-
without knowing about the server, it is hard to say.
-
http://www.petri.co.il/install_and_configure_windows_2003_dns_server.htm
The "Enable DNS Forwarding for Internet connections" part
-
Ugh, my experience with windows is pretty much zero (certainly for something like this.) Sorry…
-
The server is currently running with ISA as a firewall. Its forwarding fine and its working fine. It is my intention to swap ISA with pfsense for the simple reasons that ISA's demo license will expire soon and it has proven to be a very complicated tool that is liable to bring the whole network to a halt. When I connect through pfsense, dns forwarding is not working, but connecting through ISA, everything works like a charm. I know I'm doing something wrong, I'm just not sure what it is; its regarding dns forwarding, but that's the extent of what I know is wrong.
-
okay that is clearer now. i had gotten the impression you needed pfsense AND the ISA box. it really is not a good idea to try to have both at the same time. if all the ISA is doing is dhcp and dns for LAN hosts, i would wait until off-hours, shut it down, and replace it with the pfsense. put the pfsense in with WAN and LAN interfaces set appropriately, enable the DHCP as you need it to be set, enable DNS forwarder, and check the "allow override" box. i know this sounds like a lot, but it really is not feasible to give you a 'become an IT guy in 5 minutes" lesson :(
-
OK, I got it working after much deliberation with friends, google and trial and error.
ISA was the problem. Brought it down, let pfsense handle DHCP, altered the values for the DNS on W2K3 and updated the gateway IPs on the clients.
Is beautiful when things are going like clock work! :D
Thanks to every one!
-
cool!