01-24-2024 05:28 AM - last edited on 01-24-2024 06:39 PM by shule
Hey guys,
I have a DHCP issue on one of the subnets 10.0.1.0/22. IP addresses are released well however only with IP addresses between 10.0.1.1-254 are able to access internet ( browse ) the rest of the users up to 10.0.3.254 cannot browse. tried to queries DNS records for a particular domain name using NSLOOPUP but still it is not working.
your assistance, please
Solved! Go to Solution.
01-24-2024 06:11 AM - edited 01-24-2024 06:16 AM
Which software are you running ? and is there an external DHCP handing out the IPs?
Is the mask correct on clients not able to access internet ?
Do you got a firewall / router infront to NAT users to internet ? then check if they allow the full subnet of /22
01-24-2024 09:16 AM
90% of this issue is from the different mask between
1- GW interface
2- DHCP Pool
3- NAT list
this mismatch lead to this case
MHM
01-24-2024 07:04 PM
Sounds like the subnet mask or the gateway is incorrect in the DHCP scope.
Or upstream firewall/ NAT rule has wrong mask for the subnet
01-27-2024 10:05 AM - edited 01-27-2024 10:06 AM
Hi Guys,
Thank you very much for your responses. it was the wrong subnet mask on the interface gateway on the firewall. It was /24 instead of /22.
01-24-2024 06:11 AM - edited 01-24-2024 06:16 AM
Which software are you running ? and is there an external DHCP handing out the IPs?
Is the mask correct on clients not able to access internet ?
Do you got a firewall / router infront to NAT users to internet ? then check if they allow the full subnet of /22
01-24-2024 09:16 AM
90% of this issue is from the different mask between
1- GW interface
2- DHCP Pool
3- NAT list
this mismatch lead to this case
MHM
01-24-2024 07:04 PM
Sounds like the subnet mask or the gateway is incorrect in the DHCP scope.
Or upstream firewall/ NAT rule has wrong mask for the subnet
01-25-2024 08:37 AM
To add to the list of likely mistakes - wrong subnet mask in an ACL.
01-27-2024 10:05 AM - edited 01-27-2024 10:06 AM
Hi Guys,
Thank you very much for your responses. it was the wrong subnet mask on the interface gateway on the firewall. It was /24 instead of /22.
01-27-2024 10:06 AM
You are so welcome
MHM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide