How to use a Windows DHCP Server on LAN instead of pfSense DHCP Server?
-
However, since I've disabled pfsense's DHCP server in favor of running DHCP on 192.168.0.5, when I try to do this, it completely blocks all internet access (both directions) to 192.168.0.5.
It is hard for me to imagine how enabling/disabling DHCP server on LAN would allow/block internet access from 192.168.0.5. Perhaps there is something else you are doing that you haven't told us yet.
-
"1 WAN interface obtaining DHCP IP from cable modem."
"My ISP has issued me 5 static IPs. Call them 200.x.x.1, 200.x.x.2, etc."You sure about that?? That your static IPs are active? Are they in the same segment as the IP you get via dhcp? Normally if you got static IPs from your ISP you wouldn't be using dhcp on your wan interface but static with one of the IPs you got.
I am thinking your getting say a 24.13 or something address via dhcp, and then your trying to use a 200. address as your public for your 1:1 – which no prob not going to work.
Setup pfsense with first IP in your static -- get that working, then you can do your 1:1 setup.
I have never ever heard of using dhcp on wan, and then adding static assigned IPs?? Makes no sense at all.
-
That your static IPs are active?
It would be a problem with 1:1 NAT and those static IPs inactive. But this setup supposedly works if DHCP server is enabled on pfSense LAN! How does DHCP server affect ISP routing to those static IPs? :)
I have never ever heard of using dhcp on wan, and then adding static assigned IPs?? Makes no sense at all.
Always get the same address from DHCP?
-
your not using .5 when your dhcp now are you - so that 1:1 nat would not be active.
Are you saying you setup the 1:1 nat with the dhcp address you get and that works??
I just don't see how your wan is dhcp and then your adding static vips to that.. That just makes no sense at all!
-
Sorry, to clarify, 192.168.0.5 is my win server. So it's my DHCP and DNS server address. My LAN DHCP range is 192.168.0.10-20.
Should .5 be a reservation within my DHCP range? In other words, 192.168.0.5-20? -
no that has nothing to do with your issue of your 1:1 NAT on static while your wan interface is using dhcp. When you use dhcp your getting say .10 which is not using your 1:1 nat to your static that doesn't work. Which would then prevent your win server from going out when using the 1:1 nat that is not working.
-
Turns out my original set of static IPs from my ISP were bad all along. They've since issued me a new block of 5 IPs. The first static IP in the series has been accepted by pfsense WAN interface (static) as expected along with the netmask and gateway. All the issues that previously "didn't make sense" were due to the invalid static IPs I had been issued.
Not only am I back online with a static WAN IP, but my NAT 1:1 mapping is working with the other static IPs in the range as I had hoped.
Thanks to everyone for helping me to determine the root cause of the issue.
-
Turns out my original set of static IPs from my ISP were bad all along.
That explains why it didn't work. However it doesn't explain why it worked/notworked according to whether pfSense DHCP server was disabled/enabled. Can you explain that?
-
Yeah it does, because he using dhcp for his wan IP. This worked, but setting his 1:1 nat to some static that was not valid. So when he set ip to .5 for the 1:1 nat does not work.
When set to dhcp and got .10 address not 1:1 nat and used his dhcp gotten wan IP to get to internet worked just fine.
-
Yeah it does, because he using dhcp for his wan IP. This worked, but setting his 1:1 nat to some static that was not valid. So when he set ip to .5 for the 1:1 nat does not work.
When set to dhcp and got .10 address not 1:1 nat and used his dhcp gotten wan IP to get to internet worked just fine.
Thanks.
