Failure to auto-grab an IP address using DHCP network setting in a printer

[Wen Le]

As we know, an IP address needs to be created by the server team when a static or manual network settings is used to configure an IP address in a printer. Recently, when we switched to the DHCP (Dynamic Host Configuration Protocol) setting to auto-grab an IP address from the subnet, the printer (Fuji Xerox Apeos350, 450 & 550 category / 1st generation printer) failed to detect so even though the port was enabled and the MAC address registered. The problem was that the control panel screen was hanged and the interrupt light button blinked. The printer could only return to the normal condition after the network cable was disconnected. I heard that it was caused by the incompatibility of protocol in the printer. Could anyone enlighten or advise on how to tackle this kind of problem?

Thank you.

[ApeosMan]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

Does this happen if you set the IP details into the device as static? How was the device setup on the network prior to your changes?

It's rather unlikely if the IP address is reserved, but have you checked to see if there is another device on the network with same IP? Though this shouldn't' cause the device to freeze like you mentioned, usually it would just drop off the network and give a fault code, but anything is possible.

Also is there any network management/monitoring software that could be polling the device? I once heard a story where a fleet of MFP's were freezing due to a network management/monitoring program constantly polling the devices for network related information.

If possible try updating the firmware.

[Wen Le]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

Does this happen if you set the IP details into the device as static? How was the device setup on the network prior to your changes?

It's rather unlikely if the IP address is reserved, but have you checked to see if there is another device on the network with same IP? Though this shouldn't' cause the device to freeze like you mentioned, usually it would just drop off the network and give a fault code, but anything is possible.

Also is there any network management/monitoring software that could be polling the device? I once heard a story where a fleet of MFP's were freezing due to a network management/monitoring program constantly polling the devices for network related information.

If possible try updating the firmware.

There was no problem when we tried using a laptop to auto-grab an IP address from the port. We have tried at 3 printers of same model category at 3 different locations / levels and the same problem occurred. This problem does not happen when manual or static configuration is used. There is also no problem to auto-grab an IP address when the model is APC2200 as well as another latest model during DHCP testing.

I don't think there is another device with the same IP address. I am not sure whether there is any monitoring software that could be polling the device. If there is, the other model APC2200 should also have the same problem.

It is not possible to update or upgrade the firmware anymore as this is the first generation printer. This is also true when our request to upgrade the firmware of an old model hand-phone is always turned down. No latest version is available.

[blackcat4866]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

So let me ask you this: Why not use a static address? You'll have a lot less problems in the future if you set your MFP's to static addresses.

So just use a free utility like NetScan to check for dupes, then assign a static address. Voila. =^..^=

[ApeosMan]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

Well this is an interesting problem. I've never come across this particular issue on that family of device. I'd still advise to set the address as static, as mentioned above you will get less issues, and I know with the devices you're having troubles with that they do tend to drop off the network or DNS troubles from time to time using DHCP when coming out of a deep sleep mode.

Have you tried using just DHCP or did you give DHCP/Autonet a go? I doubt swapping them around will make much of a difference. It could be that the problematic devices just don't like what the DHCP server is sending down, though this is highly unusual. What is the DHCP server? A Windows server or a switch with DHCP capabilities?

Once again check to see if there is any duplicate IP's or if the MAC addresses are assigned to multiple IP's.

[Hansoon]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

then assign a static address. Voila.

.....hopefully not within the DHCP range of the router that's why I always try to use the high numbers in the last octet such as xxx.xxx.xxx.200 and upwards.

Hans

[ApeosMan]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

.....hopefully not within the DHCP range of the router that's why I always try to use the high numbers in the last octet such as xxx.xxx.xxx.200 and upwards.

Hans

Yup very good practice that I'm sure blackcat would follow.

I've seen an entire subnet as a DHCP scope once

[Wen Le]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

It is the bank recent practice to stop using manual and start using DHCP when a printer is relocated to a certain port. The reason is that it is quite troublesome and more admin work to be done such as submitting a request form and going through several layers of approval etc. when applying for a IP address (manual). It is not my decision, anyway. Since the printer is having a problem with DHCP, the staff would have to apply through the server team and request for manual configuration.
The engineer tried using DHCP, DHCP (autonet) and other options but the same problem occurred.
I don't know what type of server the server team is using. If we think that the server is causing a problem, their staff might argue that APC220 and new model can auto-grab the IP address.

[blackcat4866]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

It is the bank recent practice to stop using manual and start using DHCP when a printer is relocated to a certain port. The reason is that it is quite troublesome and more admin work to be done such as submitting a request form and going through several layers of approval etc. when applying for a IP address (manual). It is not my decision, anyway. Since the printer is having a problem with DHCP, the staff would have to apply through the server team and request for manual configuration.
The engineer tried using DHCP, DHCP (autonet) and other options but the same problem occurred.
I don't know what type of server the server team is using. If we think that the server is causing a problem, their staff might argue that APC220 and new model can auto-grab the IP address.

I've had similar experiences with other financial institutions. I cannot access the machines web inteface, because the network browser blocks that IP. I'm asked to diagnose scanning problems yet the IT staff will not grant access to the MFP settings or the credentials. Sometimes the machines admin password is changed. Now it's so secure I can't do anything. And neither can the endusers.

I don't envy your situation. =^..^=

[Tonerbomb]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

It is the bank recent practice to stop using manual and start using DHCP when a printer is relocated to a certain port. The reason is that it is quite troublesome and more admin work to be done such as submitting a request form and going through several layers of approval etc. when applying for a IP address (manual). It is not my decision, anyway. Since the printer is having a problem with DHCP, the staff would have to apply through the server team and request for manual configuration.
The engineer tried using DHCP, DHCP (autonet) and other options but the same problem occurred.
I don't know what type of server the server team is using. If we think that the server is causing a problem, their staff might argue that APC220 and new model can auto-grab the IP address.

If they assign a reserved IP address then enter that IP as a static IP. Also I've had some strange issues that were resolved by disabling SNMP.

[slimslob]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

You mentioned that the MAC address was registered. Make certin that the proper MAC was entered. Also, make certain that it was registered as an allowed MAC and not a blocked MAC. If the DHCP server is a network server and not a router, be sure to enter the proper domain name on the printer. The usual procedure for using DHCP is to let the DHCP find the device without registering it first. After the device has an IP address, merely set the DHCP to reserve the IP address to the connected device. Also check firewall settings on the network and the settings on an manageable switches.

[ApeosMan]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

I Also I've had some strange issues that were resolved by disabling SNMP.

Most likely some network monitoring software was polling the device causing issues and disabling SNMP would've stopped this from occurring.

The problem with disabling SNMP is that if there is a server based meter read capturing software, it's going to cut off the link to capture the meter reads, toner status etc.

This is a rather interesting issue, hopefully the OP will report back to us if they happen to find a fix. I think the I.T. reps at the company in question need to look into things on their end too. All to often I.T. reps pass the blame onto the printer people when in fact it's an issue on their end.

[Wen Le]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

Most likely some network monitoring software was polling the device causing issues and disabling SNMP would've stopped this from occurring.

The problem with disabling SNMP is that if there is a server based meter read capturing software, it's going to cut off the link to capture the meter reads, toner status etc.

This is a rather interesting issue, hopefully the OP will report back to us if they happen to find a fix. I think the I.T. reps at the company in question need to look into things on their end too. All to often I.T. reps pass the blame onto the printer people when in fact it's an issue on their end.

Agreed. It looks like disabling SNMP is not a good option. The people from IT team / server team tend to pass the problem to the printer end and I'd came across quite a no of them. Sometimes, they may not even know how to go about solving it. Their knee-jerk reaction is to push the problem to the people who manage the printers as the data passes through the machines. What we can do is to get the correct information or evidence & ask them to take the necessary action after we have done our part by troubleshooting the machines. If an obstacle is met, we can approach the Manager who takes charge of the fleet for advice and direction.

[qbert69]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

With the copy machine disconnected, do a CMD from the Windows Start Menu. Ping the proposed static IP address to make sure there are no other machines on the network with that IP address. Then do an ipconfig/all of the computer you are on, note all of the parameters such as the IP address (similar range as the static you just ping'd), Subnet Mask, DNS Server(s), Default Gateway, DHCP Server, etc. Copy these parameters to your MFP. Restart the machine and check the parameters you just entered to see if they stuck. If so, then go back to the computer to see if you can ping the MFP, if you can, you can probably go ahead and install the print drivers.


Good Luck!

[Ceechtay]

Re: Failure to auto-grab an IP address using DHCP network setting in a printer

If you have an inexpensive router, I'd take it to the location and plug the printer directly into the router and see if it gets a DHCP address. If it can't get a DHCP address when directly connected to a DHCP-enabled router, then you know the issue lies entirely within the printer.

Also, have you tried different Ethernet jacks at the location?

I know you have tested with a laptop, but I have seen one location where a Sharp copier couldn't get on the network, while a laptop could, when using the same network jack. I'm guessing that the laptop NIC has more fault tolerance or some OS feature that corrected any problems.

In the above case, we tried multiple Ethernet jacks and the copier couldn't get on the network at all. However, when we plugged the copier directly into the router, it obtained a DHCP address without issues. We also plugged it directly into the switch which the router connects to and it worked perfectly fine. The customer ended up running a new cable and things worked fine.