text: <s>[INST] BOOTP issues Summary: BOOTP and 2100-ENET There doesn't seem to be a forum that fits this particular device so sorry about the cross post. I've been having lots of problems with our new pre-packaged Intellicenter MCCs equipped with Ethernet, they use a Ethernet to devicenet module, 2100-ENET. The issue is assigning IP addresses, you have to use BOOTP to do so, sometimes it works OK and sometimes not, doesn't matter what PCs I use, Win7 to XP SP2 and SP3 and different crossover cables. These were all manufactured in 2012. Right now I've got a whole MCC section of six that I can't see with BOOTP (v2.3). I've followed all the online docs with no success. Tech support hasn't been able to give me much assistance on this except to expound on using XP. I do know how to do these and how to configure the PC, etc. Last year did well over 150, had issues but was able to get thru them more or less. This time, nada. I really hate these, could have been finished if they were devicenet or had a reset switch for the IP to put them back into BOOTP mode. Anyone out there have similar experiences and/or suggestions? [/INST] Are you trying to use bootp with a bootp server as permanent method of using Ethernet? Or are you trying to use bootp to permanently configure a static IP address? BootP and Win7 do work. It is criminally lazy that tech support is still pushing XP. Several things to try: Make your network as simple as possible. Like, you, an unmanaged switch, and the 2100-enet. Nothing else to interfere. Make sure, under network settings, the network mask matches what you wish to have in your device. In the same place, make sure there is no gateway set, and that in your computer's ethernet adapter there is no gateway address. Having a gateway address set without having an actual gateway existing will cause problems. \\n </s>