After successfully establishing a connection with a PLC, I activate the "Enable BOOTP/DHCP" option and receive a confirmation message stating that the command was successful. This change is reflected in RSLinx, where the device port configuration switches from manual to automatic IP settings via BOOTP. However, when attempting to disable BOOTP/DHCP, the process does not take effect. There is no indication of any change, warning, or alteration in port configuration. Why is this happening and how can it be resolved? Your assistance is appreciated.
unsaint32 reported that enabling Bootp/DHCP was successful. After establishing a connection with a PLC, clicking on "Enable BOOTP/DHCP" resulted in a message confirming the successful command execution. The RSLinx displayed a change in the device port configuration from manual IP settings to automatic settings using BOOTP. However, disabling Bootp/DHCP did not produce any noticeable changes. No warnings or port configuration adjustments were observed. This raised the question of why it did not work as expected. Your assistance on this matter is greatly appreciated. It is worth noting that BOOTP/DHCP is enabled by default on all modules. Once an IP address is assigned, it remains in place until the power is reset. In the event of a power cycle with BOOTP enabled, the IP address must be reassigned either manually or through a "relation list". To retain the assigned IP settings, it is necessary to "Disable BOOTP/DHCP".
Ironically, I faced the same problem earlier this morning. To resolve it, I simply right-clicked on the relationship in the lower box and chose to Disable Bootp from the dropdown menu that appeared. This method worked perfectly for me. The reason why it didn't work using a different approach remains a mystery to me.
JZerb shared a tip for resolving a common issue with relations by disabling Bootp. Interestingly, I encountered the same problem this morning and found success by right-clicking on the relation in the lower box and selecting "Disable Bootp" from the drop-down menu that appears. It worked perfectly for me using this method. The reason why it doesn't work the other way around remains a mystery. Enabling Bootp is only necessary if you have previously disabled it. Bootp is the default power-up mode, unless explicitly disabled. The decision is straightforward - if you prefer to manually assign modules every power-up, or automate the process using a Bootp/DHCP server, then you should enable Bootp. If you want the module to retain its assigned IP settings, then simply disable Bootp once you have configured the IP settings desired.
In configuring network settings, the enable/disable buttons typically control DHCP/BootP assignment for the server, not the physical device itself. For example, enabling a BootP server instance for a specific MAC address assigns it an address that remains even after power cycles or changes via RsLinx, unless disabled. It is advisable to also disable BootP on the PLC through RsLinx. While I am not an expert in BootP configuration, I usually prefer setting my IP address over serial connection.
When using the enable/disable buttons, keep in mind that they are not just for server DHCP/Bootp assignments, but also for the physical device itself. For example, you can enable a BootP server instance for a specific MAC address and assign it an IP address. This assigned address will persist even after a power cycle or changes made via RsLinx, unless you click the disable button. It's important to note that you may still need to disable BootP on the PLC via RsLinx. While I personally prefer setting my IP over serial communication, it's good to know the options available. The buttons actually send essential commands to the remote device to ensure it remembers its IP settings (Disable BOOTP) or enters BOOTP mode (Enable BOOTP). So, be on the lookout for a "Command Successful" response to confirm your changes.
This could be due to a number of reasons, but one common issue is that the PLC may not have the correct permissions to make this change. Try to check your permissions first. Additionally, it could be a firmware issue, as some versions may have bugs related to DHCP settings. Make sure your firmware is up to date. Worst case scenario, it could be a hardware issue. If you can, try using another PLC to see if the problem persists. Finally, contact technical support; they might have come across this before and could possibly offer a more direct solution.
From your description, it sounds like your PLC isn't accepting the command to disable BOOTP/DHCP. This issue could arise from a couple of probable reasons, such as a network glitch or perhaps a firmware-related issue. If you haven't already, try resetting your connection to see if that'll help. Sometimes, the simplest solutions are the most effective. If that doesn't work, you might want to check if your PLC's firmware is up-to-date. Optimally running firmware is often overlooked, but it plays a crucial role in the effective functioning of PLCs.
It sounds like the command to disable BOOTP/DHCP isn't being acknowledged by the PLC. As for why this is happening, it could be due to a number of factors such as firmware bugs or communication issues. A good place to start troubleshooting would be checking your PLC's firmware version and updating it if needed, ensuring the command is being sent correctly, or possibly even trying a factory reset as a last resort. Also, confirm that you have the proper user rights to make this change, as some systems require higher level access to modify network settings.
It sounds like you're encountering a common issue with PLC devices when trying to toggle the BOOTP/DHCP settings. Sometimes, the PLC might need to be power-cycled or reset for the settings to fully take effect after making changes. Also, ensure that you're not inadvertently sending conflicting command sequences that could override your disable request. If it's still not working, checking the firmware version of your PLC might help, as updating it could resolve potential bugs related to network settings. Lastly, consulting the documentation for your specific model can provide insights into any special configurations needed for this process. Good luck!
It sounds like you’re dealing with a hiccup that can sometimes happen with automation devices. One possibility is that the PLC may require a power cycle or a specific reset after making changes to the network settings to fully deactivate BOOTP/DHCP. Additionally, ensure that you have the correct permissions or access level to change these settings, as some firmware versions impose restrictions. If the issue persists, checking the firmware version and considering a reset to factory settings could help, although the latter should be a last resort. Let us know what works for you!
It sounds like you’re experiencing a common issue with PLC settings. Sometimes, the configuration can get stuck due to cached settings or a glitch in the software. To troubleshoot, first, try power cycling the PLC after disabling BOOTP/DHCP to ensure it resets properly. Additionally, double-check if any overlapping settings or firmware restrictions are preventing changes. If it’s still not responding, consider checking the compatibility of your RSLinx version with the PLC firmware; updating them may help resolve the issue.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Why is the "Disable BOOTP/DHCP" button not working on the BootP server? - The issue could be due to a configuration error or a technical glitch in the server settings.
Answer: - You can try restarting the server, checking the network connections, verifying the settings, and updating the firmware to resolve the issue.
Answer: - Double-check the server settings, ensure proper communication with the PLC, and troubleshoot any network issues that may be affecting the configuration changes.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.