Sorry for the very lengthy post but... Thanks to D*'s free 72 swap program, this Monday I was upgraded(?) from my trusty old series 2 TiVos (SD-DVRx0s, may they R.I.P.) to four shiny, new HR23-700 DVRs. I have much love for my recently obsoleted TiVo hardware, but I will beat that horse in another thread. So to start let me state that by day I setup and troubleshoot networking installations and know the intricacies of twisted pair ethernet and ipv4 well enough that I feel comfortable ruling out the obvious. All the networkable hardware in my home (excluding a couple portable devices) is connected to a 24 port 10/100 switch via dedicated cat5 pulls. At this point I set out to build a dedicated Ubuntu machine to run a uPNP server. However, in my impatience to test drive the MediaShare functionality I loaded up TVersity on one of my (cringe) windows machines. This was Monday evening. It worked as well as could be expected, even transcoded xvids played well. If shuttle commands (ff / rw) were implemented in the DVRs renderer I'd hardly remember why I loved my TiVos so much. At this point I've statically addressed two of the DVRs, and everything seems to be peachy. Moving on. The electric utility cut power to our home in the early hours on both Tuesday and Wednesday for scheduled upgrades. I don't know if this is related to my problem or not, just mentioning it. In the mean time I did not test or even think about MediaShare until Tuesday afternoon when I'd finished compiling MediaTomb and all it's dependencies and had some test media loaded up on what will eventually (hopefully?) replace my old media server. Unfortunately my DVRs aren't cooperating. After pulling my hair out for a few hours recompililing MediaTomb, I decided it a good idea to make sure that the DVRs were still seeing the TVersity server that had worked 24 hours earlier. No luck. They're not even responding to pings. After some research it appears the ICMP issue is a given, probably the result of thoughtful firewalling on the DVRs. But I have no idea why MediaShare is no longer seeing my TVersity server. So after much searching, reading and digesting everything I can on this and a couple other forums, I've decided to post here in hopes of finding some ideas. Here's where I'm at: statically addressed dvr IP: 192.168.24.20 NM: 255.255.255.0 GW: 192.168.24.1 (router running base openwrt with iptables, dnsmasq, dhcp, upnpd) DNS: 192.168.24.1 Nothing else on the LAN has changed, and everything else still works as it has for the past 18 months or so. Experimenting last night, I found that if I reboot the boxes with the ethernet unplugged and then connect them to the lan while running a ping on my router I see replies for a short time until the DVR's firewall is presumably enabled. The flashing leds on the DVR's ethernet ports indicates there is some network traffic occurring, though it must be local traffic because nothing shows up from the DVR IPs in my router's ip_conntrack. The last thing I tried yesterday evening was to reset the DVRs to default settings on the network screen. This gets even better - now they won't even get a dhcp lease. This was also working Monday afternoon. Also, I'm relatively sure they were able to connect to the internet at some point, because the On Demand option has appeared in the menu - something I'm almost positive was not there Monday afternoon. So, any ideas what is up? I've become quite familiar with the whole 'connect now' screen - everything comes back with 'OK' status except for the dreaded error 22. What's even more puzzling is that if I watch ip_conntrack on my router during the 'Connect Now' process, it doesn't even appear that the DVR is trying to connect to anything outside of my LAN (i.e. the internet). I'm thinking the next thing to try is doing a 'Reset Everything' which I assume reformats the DVR hard disk and starts from scratch. Any thoughts, comments, ridicule? Is it possible that D* disabled MediaShare because I'm a lowly SD only subscriber?