Windows Server DHCP can't connect from phone

E

evilarthas

New Member
Joined
Feb 22, 2021
Messages
1
Good day, dear colleagues. We have a Windows Server setup in our workplace. The structure is the following: the FTTB cable comes into the server, then one LAN cable goes into access point #1 which, at the same time, distributes other LAN cables to access point #2, #3, etc. I have set up Routing and DHCP on Windows Server and given the 10.0.0.1 - 10.0.1.99 subnet for automatic IP distribution. Access Points use static IPs and their ones are excluded from distribution. Windows Server's ip - 10.0.0.1 Access point #2 - 10.0.0.2 ... #3 - 10.0.0.3 ... 5 and then all ips from 10.0.0.6 are distributed. Everything works fine until some day when we leave the workplace and come the following day, our phones won't connect to Wi-Fi, however, our laptops can! Unless I restart both the access point #1 and windows server at the same time, we won't be able to connect. What I did wrong in the setting the server up? How to fix that?
 
Solution
The issue you are facing with the phones not connecting to Wi-Fi while laptops can is likely related to a problem with DHCP lease renewals or IP address conflicts. Here are some steps you can take to troubleshoot and potentially fix this issue: 1. Check DHCP Lease Time: - Ensure that the DHCP lease time set on the Windows Server is long enough to accommodate devices being powered off overnight. If the lease expires before devices reconnect, they may not be able to obtain a new IP address. Consider extending the lease time. 2. Check for IP Address Conflicts: - Verify that there are no IP address conflicts in your network. Two devices using the same IP address can cause connectivity issues. Monitor your network for any...
The issue you are facing with the phones not connecting to Wi-Fi while laptops can is likely related to a problem with DHCP lease renewals or IP address conflicts. Here are some steps you can take to troubleshoot and potentially fix this issue: 1. Check DHCP Lease Time: - Ensure that the DHCP lease time set on the Windows Server is long enough to accommodate devices being powered off overnight. If the lease expires before devices reconnect, they may not be able to obtain a new IP address. Consider extending the lease time. 2. Check for IP Address Conflicts: - Verify that there are no IP address conflicts in your network. Two devices using the same IP address can cause connectivity issues. Monitor your network for any conflicting IP addresses. 3. Check DHCP Server Logs: - Review the DHCP server logs on the Windows Server to see if there are any error messages related to DHCP lease renewals or assignments when the issue occurs. 4. Restart Access Points and Windows Server: - If restarting both the access point and Windows Server resolves the issue temporarily, this could indicate a problem with DHCP lease renewal. Restarting resets the lease process. 5. DHCP Relay Configuration: - Check if the DHCP relay agent setting is correctly configured on the access points to forward DHCP requests to the Windows Server. Incorrect relay settings can cause DHCP-related issues. 6. Static Reservations: - Consider setting up static DHCP reservations for critical devices such as phones or ensuring they have static IPs to avoid lease renewal problems. 7. Network Monitoring: - Use network monitoring tools to track DHCP leases and network activity to identify any patterns or anomalies that may provide additional insight into the issue. 8. Firmware Updates: - Ensure that the firmware on your access points is up to date. Sometimes, firmware updates can address connectivity issues. By following these steps, you should be able to diagnose and potentially resolve the Wi-Fi connectivity issues with phones in your workplace. If the problem persists, consider consulting with your IT department or a network specialist for further assistance.
 
Solution
You must log in or register to reply here.