Forum Discussion
Gateway IP address conflicts
- Hace 3 años
You can open a console/terminal and ping the network broadcast address 192.168.12.255 and then check the client's ARP table (command arp -a). That should provide some idea of clients that are up and are responding. If you have set any static IP addresses on the network in the 101-254 range then remove the IP for any client with a static IP in that range and use an IP from 2-100. I am pretty sure the DHCP scope runs from 101-254. I never seen an IP assignment below 101 from DHCP. I can assign and I do assign static IPs below 100 so I am pretty sure it is safe to say it is ok and will not duplicate any IP addresses. You can easily test by pinging an IP address you want to set from a client that is connected with a valid IP address. If there is no response then the IP is probably free, assuming it is NOT part of the DHCP scope.
I confirmed using IP network monitoring software that the DHP is assigning all unique IP addresses on the network with no conflicts. Notably, the same network and switch never had this warning using a Verizon or Comcast router? Still getting the annoying "Windows has detected an IP address conflict” error message on every computer on the network every few minutes with that T mobile router.
Contenido relacionado
- Hace 8 meses
- Hace 8 meses
- Hace 2 años