I've updated the config tool to be a nicer GUI: http://synack.net/~bbraun/wnce2001config1.1.hqx
After joining a network, the WNCE2001 will not change its network settings to allow the client to continue talking to it. When you're ready to adopt the new network settings, there are two choices:
1) Have the WNCE2001 request a new DHCP address, which will just reconfigure the WNCE2001's IP address, leaving your IP address alone.
2) Reboot the WNCE2001, which will cause it to both DHCP a new address and remove link from the LAN port. On most modern systems, removing and reestablishing link triggers a DHCP update. OpenTransport (at least versions <2) don't do this. They'll keep the same DHCP address regardless of link state.
So, once the WNCE2001 adopts the changes, the config tool can no longer talk to it until your IP configuration is updated too, which isn't automatic. You need OpenTransport to refresh its DHCP information (or just reboot), or reconfigure your IP address manually.
After joining a network, the WNCE2001 will not change its network settings to allow the client to continue talking to it. When you're ready to adopt the new network settings, there are two choices:
1) Have the WNCE2001 request a new DHCP address, which will just reconfigure the WNCE2001's IP address, leaving your IP address alone.
2) Reboot the WNCE2001, which will cause it to both DHCP a new address and remove link from the LAN port. On most modern systems, removing and reestablishing link triggers a DHCP update. OpenTransport (at least versions <2) don't do this. They'll keep the same DHCP address regardless of link state.
So, once the WNCE2001 adopts the changes, the config tool can no longer talk to it until your IP configuration is updated too, which isn't automatic. You need OpenTransport to refresh its DHCP information (or just reboot), or reconfigure your IP address manually.