DVB:
The 'new' TED5000 you just received has undoubtedly been sitting in a warehouse somewhere for a while and the firmware is whatever was in production at the time the unit was manufactured. This Beta firmware addresses problems, offers new features, etc. So if you want/need improvements offered by the upgrade...
The description of the problem you just mentioned sounds more like a browser issue. If you are using IE or Chrome, try Firefox. Firefox is nicer for troubleshooting because it will alert you when there are wierd issues with your communications but IE will just quietly not give you what you want.
If you are still having problem and want to determine if the DHCP lease time is a potential problem for your installation, you could try the following...
as long as you have access to your routers DHCP lease table:
1) unplug TED ethernet connection
2) reboot TED (power reset by unplugging for 15 seconds)
3) reboot router (mostly to clear out the DHCP lease table so you are starting clean)
4) log into router - open DHCP lease table - at this point, hopefully only lease outstanding is the PC you logged into the router with.
5) connect TED ethernet connection
6) monitor the DHCP lease table (refresh might be required depending on your router interface software - mine has a <Refresh> button)
7) IF the lease for TED5000 has a one minute lease period, you may be experiencing the DHCP lease timeout problem.
Monitor the DHCP lease table for a few minutes to see if TED requests another lease and to see what (new) address is assigned.
9) After a few minutes, activity from TED should settle down. At this point, try to connect to TED using the last DHCP address assigned to TED (whether it is expired or not) .
10) Assuming you are having the lease timeout issue, once you gain access to TED, set the IP address to STATIC. Assign an address in a range that your routers DHCP service will not assign. My router is configured to give out addresses in the 192.168.1.100 - 192.168.1.150 range. All other addresses in the 192.168.1.x range can be statically assigned (other than .0, .1, and maybe .254 .255 depending on your router).
I say 'may be experiencing the problem' because as long as your network isn't active (no new devices attaching), even if the lease times out, TED will continue to answer to the last address it was assigned... And if TED requests a new address as long as the network isn't active, the router will probably assign the same address again. A duplicate address problem can occur if TED continues to use the last (expired) address and a new device is assigned the expired address TED is using.
When TED was behaving badly during my earlier testing, it would ask for an address about once a minute for a while. When my network was active, I saw TED start at address .101 and within a day or so, get to .127. Another setting that may aggrevate the problem is time sync - i turned that off at Supports suggestion. TED apparently resyncs time about every 20 minutes if it is enabled.
The 'solution' to the DHCP lease issue is to assign a static IP to TED. But you need to be able to access TED's 'System Settings Wizard' which means you need to get further than the footprints outline. Not sure any of this helps.
