This does, indeed, seem to solve the DHCP floods.
I was under the assumption that everything settable from the front panel could also be set from the CWIS.
Hi, Friend !
We`re comrades in misfortune.
We`re also have the same problem.
But by chance we found that problem is being solved when wi-fi is turned off.
P.S Question to Xerox support. Why?!
Thanks for your reply.
TCP/IP, in particular DHCP, is configured and functioning.
Network Setup
TCP/IP Settings | |
TCP/IP Enabled: | Enabled |
Host Name: | b205 |
IP Address: | 192.168.1.81 |
Subnet Mask: | 255.255.255.0 |
Default Gateway: | 192.168.1.1 |
Automatic Addressing: | DHCP/Auto IP |
The problem is that, after the DHCP handshake:
May 4 08:38:30 srv1 dnsmasq-dhcp[479]: DHCPDISCOVER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 May 4 08:38:30 srv1 dnsmasq-dhcp[479]: DHCPOFFER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 May 4 08:38:30 srv1 dnsmasq-dhcp[479]: DHCPREQUEST(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 May 4 08:38:30 srv1 dnsmasq-dhcp[479]: DHCPACK(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 b205
the printer gets its lease and should refresh after 6 hours (the DHCP lease time). However, it reissues DHCP requests every two seconds.
Hi sciurius,
Thank you for using the Support Forum. The only thing I could find is this article in the online support for your product Fault Code 17-800: DHCP Problem Auto IP Run Message. Solution 2 in this article might help you. If not please consider contacting your support centre for further assistance.
Xerox B205 with firmware V3.50.01.60_20200715 connected via ethernet cable.
TCP/IP version 6 is disabled.
TCP/IP version 4 is configured to use DHCP. This works, but the B205 repeats the DHCP query every 2 seconds, flooding the DHCP server and clogging the logfiles.
Apr 30 08:25:27 srv1 dnsmasq-dhcp[9786]: DHCPDISCOVER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:27 srv1 dnsmasq-dhcp[9786]: DHCPOFFER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:27 srv1 dnsmasq-dhcp[9786]: DHCPREQUEST(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:27 srv1 dnsmasq-dhcp[9786]: DHCPACK(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 b205 Apr 30 08:25:29 srv1 dnsmasq-dhcp[9786]: DHCPDISCOVER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:29 srv1 dnsmasq-dhcp[9786]: DHCPOFFER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:29 srv1 dnsmasq-dhcp[9786]: DHCPREQUEST(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:29 srv1 dnsmasq-dhcp[9786]: DHCPACK(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 b205 Apr 30 08:25:31 srv1 dnsmasq-dhcp[9786]: DHCPDISCOVER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:31 srv1 dnsmasq-dhcp[9786]: DHCPOFFER(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:31 srv1 dnsmasq-dhcp[9786]: DHCPREQUEST(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 Apr 30 08:25:31 srv1 dnsmasq-dhcp[9786]: DHCPACK(eth0) 192.168.1.81 9c:93:4e:b0:b7:80 b205
I have now disabled DHCP and entered static data, but this is not desired.
What can I do to stop the B205 from flooding the DHCP server?
Solved! Go to Solution.