It might help--and you may get a quicker response--if you give a detailed description of your issues here, especially any that don't have anything to do the the LAN if there are any. You mentioned date/time/configuration. So turn it on, set the date/time and set it up in a way you'll recognize--say all 4 channels on a 1V/div and 50ns/div or whatever. Then shut it down, give it 10 seconds and disconnect the power for a minute. Power it back up and see what you have. If you lose the date/time/configuration when you do that, then I don't think there's any firmware or the like that is going to help.
I was trying not to get into the gory details since I don't want to come off as bad-mouthing the scope. This is my first Siglent product and just wanted to know if they're known for issues like this. I'm really trying to like this scope but, it feels like I just bought a brand new car with an engine that makes a terrible ticking sound...
Be assured, there is nothing wrong with the LAN (famous last words but, please trust me on this). The issue has been replicated on two (actually three) totally different LAN environments.
1) Only Static IP addresses and LAN configs work. DCHP is a no-go with intermittent 50 to 100% packet loss.
2) The timezone keeps resetting to UTC if the unit is powered-off via menu or warm-switch.
3) The LXI LAN Reset option does not do a HW reset on the phy port (never drops carrier) as I would expect; instead, it set the flags in the LAN configuration for "Auto DHCP" back to enabled status.
4) After saving a configuration (timebase, some channel configs etc) then, doing a power-down followed by restoring the configuration, some of the screen characteristics are not restored. e.g. Beep-sounds, menu auto-hide and some channels that were enabled are no longer enabled.
5) Also (this is probably not a bug/issue) the Ethernet port only negotiates to 100Mbps. I know of no product since the early 2000's that came with 100bT.
Simple signals from a generator looked OK but, when basic, ground-zero stuff was not working, I held-off on going any deeper.
(I did firmware development for both medical devices and high-speed networking equipment for the 1st couple decades of my career. The first 15 minutes with this scope was like a flashback to Windows 3.0).
Ray