Black Hole
May contain traces of nut
Nice explanation, but I don't think that would reveal the DLNA service (which is what UPnP Inspector does).
I beg to differ, I found that XP could take hours (or days sometimes) to recognise a new network resource. Win7 rarely takes more than a few minutes.No worse than Windows 7 in my experience.
Nice explanation, but I don't think that would reveal the DLNA service (which is what UPnP Inspector does).
We differ. However my experience mainly relates to Windows connecting to Linux servers running Samba and which when they boot will attempt to become the workgroup master . My beef with Windows 7 is that it more often rescans the network even when the resource I want has been continuously available.I beg to differ, I found that XP could take hours (or days sometimes) to recognise a new network resource. Win7 rarely takes more than a few minutes.
There have been two two issues going on here (DLNA and Samba), and it still doesn't seem clear whether or not either are working properly.
Ignoring 'Network Places' and Workgroup settings completely, you ought to be able to type the following into the 'Start - Run' box (i.e. click the Windows Start button and select 'Run' or else hold down the Windows 'Start' key and press 'R') and get a result if Samba is working.
\\xxx.xxx.xxx.xxx - where xxx.xxx.xxx.xxx is the Humax IP address. Note the two backslashes, NOT forward slashes.
The VLC app (as opposed to the browser plugin) still supports DLNA playback (in that there is a UPnP entry for it in the playlist window), but I've had no success using it in the latest version, though it certainly used to work.
OK for StDef, but not HiDef as far as I know.Might be better off installing the Windows version of XMBC - that 'just works' with DLNA in my experience.
That's on 2.1.3. It just hangs when searching for available DLNA servers (of which I have two HDRs and a Netgear ReadyNAS)
Older versions of VLC couldn't cope with HiDef - is 2.0 OK?