Archer C2 AP. DHCP Problems
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer C2 AP. DHCP Problems
Model :
Hardware Version :
Firmware Version :
ISP :
I just recently bought an archer C2 (AC750) router, to replace my old TP link router. Theres to say, I dont use it as a router, but as an accesspoint, behind a fiber router.
The Fibre-Router hosts the DHCP:
DHCP Range: 192.168.1.64 to 253. The router itself taking 254.
I assigned the Archer the IP 253 and disabled DHCP, NAT and nearly everything else.
I have internet access, but in short periods all my clients lose connection (several pcs and wlan clients)
The log from C2 look like that:
I already updatet the firmware. The Subnetmask ist 255.255.0.0 on both, the Router and the C2.
Any Ideas where the issue could have its origin?
Regards
Tim
Hardware Version :
Firmware Version :
ISP :
I just recently bought an archer C2 (AC750) router, to replace my old TP link router. Theres to say, I dont use it as a router, but as an accesspoint, behind a fiber router.
The Fibre-Router hosts the DHCP:
DHCP Range: 192.168.1.64 to 253. The router itself taking 254.
I assigned the Archer the IP 253 and disabled DHCP, NAT and nearly everything else.
I have internet access, but in short periods all my clients lose connection (several pcs and wlan clients)
The log from C2 look like that:
1 | 2017-06-19 20:31:11 | DHCPC | Notice | Recv no OFFER, DHCP Service unavailable |
2 | 2017-06-19 20:31:08 | DHCPC | Notice | Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 |
3 | 2017-06-19 20:31:05 | DHCPC | Notice | Send DISCOVER with request ip 0.0.0.0 and unicast flag 0 |
4 | 2017-06-19 20:31:00 | DHCPC | Notice | Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 |
5 | 2017-06-19 20:30:57 | DHCPC | Notice | Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 |
6 | 2017-06-19 20:30:54 | DHCPC | Notice | Send DISCOVER with request ip 0.0.0.0 and unicast flag 1 |
I already updatet the firmware. The Subnetmask ist 255.255.0.0 on both, the Router and the C2.
Any Ideas where the issue could have its origin?
Regards
Tim