I ran out of adresses in the DHCP scope of my working guest network. The current config is Class C: 192.168.66.254/255.255.255.0 DHCP Scope is .1 to .252 DNS: IF-IP I changed IP/Mask to 10.19.66.1/255.255.248.0 I deleted the DHCP scope. I created a new scope and accepted the default result. I changed the subnet mask to 255.255.248.0 I changed DNS to specific and used 8.8.8.8 Clients receive correct addresses but can't access internet anymore. What am I missing here? Thank You!
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
You probably need to change your default route as well, I mean, the "default gateway" setting in the DHCP server settings. You can check that quickly on a client with "ipconfig -all".
Your scenario is the best example why the router should always get the .1 address in it's LAN address space. For example, if 192.168.66.1/24 is your LAN port's address, then changing that to 192.168.66.1/23 would double the address space from .66.2 to .67.254. Without any changes to the FGT required.
This is a natted VLAN (one of many, all are working all are using .254 in their respective SN). Gateways are allways IF IP, DNS Servers as well. There is only one static route 0.0.0.0/0 -> SDWAN.
I agree that using .1 as GW is nice but I got to work on an existing system and can't change the LAN-Port at the moment.
solved:
IP/Netmask:: 10.19.71.254/255.255.248.0 DHCP Scope: 10.19.64.1 to 10.19.71.253 DNS: 8.8.8.8
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
227 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.