EDIT: You replied before me ASF. Read on for some pertinent info...
unsaint32 said:
...apologies for not clearly stating that my Bootp disabling was unsuccessful...
No need to apologise. Your post was clearly titled...
unsaint32 said:
BootP server Disable Bootp button not working
...but you can see how the best of us can be confused from time to time with what the OP is about. A simple opening explanation that it was not a new out-of-the-box device and that BOOTP/DHCP was already disabled would have gone a long way toward clarifying the initial device status. Not to worry. Hindsight and all that...
Speaking of...
In fact, it's I who owe you an apology. I called you out on not providing details on the device in question, but your attached screenshot provided more than enough details to keep even me happy. It just failed to load and open when I first viewed and replied here using my not so smartphone. So I had not seen it until today on my fancy new 23" monitor in work.
unsaint32 said:
...After reading the replies, I tried Bootp-disabling from the drop down menu (right clicking on the relation). And it worked perfectly. I got the message at the bottom of the BootP server software saying it was successful. RS Linx port config changed...
That's good to hear and I'm glad the simpler advice helped you (because we don't have to get into the other possible causes!) but I want clarify something here, which, in doing so, could actually add more confusion than not. But I do like a challenge...
Having now viewed your screenshot, and your mention of which version of RSLinx Classic you are using (v3.81), you have triggered one of my mind's many storage pointers which makes me go "Hmm, I seem to recall something about that?"
I'm a Devil for reading release notes and they are one of the many resources I use to store tidbits of info for later recollection...
RSLinx Classic v3.81 Release Notes
...Updated BootP Tool - BootP DHCP Server renames to BootP DHCP EtherNet/IP Commissioning Tool...
RSLinx Classic, up to v3.80, installs "BootP DHCP Server" up to v2.3.2
RSLinx Classic, v3.81 or later, installs "BootP DHCP EtherNet/IP Commissioning Tool" starting at v3.00
The "Disable BOOTP/DHCP" button, in this particular software, may "never" have worked for ASF, or "always" worked for daba, but for the rest of us less absolute cases, this thread has prompted me to make a distinction between what has historically not worked for some and what has not worked, specifically, for you here...
unsaint32 said:
...I didn't know the disable-bootp button often does not work as Bit_Bucket pointed out...
Often, yes, but Bit_Bucket_07 is referring, no doubt, to the historical failures of this particular feature in previous versions of this configuration software. But your version is newer.
There are several reasons, which we have not gotten into here, as to why the older software (up to v2.3.2) might not have worked for disabling BOOTP/DHCP. Reasons which are external to the software. To my knowledge, there has never been any admission by Rockwell that the older versions of the software itself was to blame for such issues. Most to all cases I've encountered where disable will not work from the software was resolved by correcting one or more of the reasons we still haven't mentioned.
However, (patience, I'm getting there) for the newer software versions of this tool, they have publicly stated that there is a known specific issue with the Enable and Disable BOOTP/DHCP button and that you are advised to use the menu option instead (or right-click option in Relation List that I've mentioned)...
948444 - Enable/Disable BOOTP/DHCP buttons have no effect in Bootp DHCP Utility 3.00.00
Access Level: TechConnect
To be clear - the distinction I'm making here is this...
The older versions of the BootP software tool may appear not to function correctly for many reasons, but the buttons in the software themselves have never been proven or admitted as being a direct cause of such malfunctions.
The newer versions of the BootP software tool may also appear not to function correctly for many reasons, but the buttons in the software themselves have specifically been proven and admitted as being a direct cause of such malfunctions.
unsaint32 said:
...Thank you so much everybody for educating me.
I do hope that was somewhat further educational.
Regards,
George