Getting error: File "... epg123.mxf" does not exist

[IT Troll]

Home routers will often create a default private domain for you which is only used internally on your home network. You can sometimes rename this to something of your choosing.

[Space]

...
IP addressing works because it doesn't rely on broadcast traffic. You should find that using full domain name (FQDN) will work. This will take the form of something like http://mypc.home.net:9009

I'm not sure that a FQDN would work for a home LAN, as usually you only have a FQDN for you public (Internet) IP address(es). But I don't know much about Windows networking. I'm sure you could set up domain names for the computers on your local LAN, but I don't think most people do that and I'm not sure if anything is configured by default.

EDIT: (Missed your post due to it being on the next page...)

Home routers will often create a default private domain for you which is only used internally on your home network. You can sometimes rename this to something of your choosing.

Yes, this may be the case for some routers, not sure how common it is for this to be set up by default though...

EDIT 2:
I just checked my Win10 machine and it seems to use the ".home" domain with the (I think) NetBIOS name, so if you have a PC with a NetBIOS name of "desktop" you can use domain "desktop.home" to reference it (at least from the Win10 machine).

[Gripweed]

Ow! Where to begin? Firstly, I'm not using a HomeGroup (or whatever it is called). I'm setup as a WorkGroup. That's a follow thru from probably Windows 2000 when I first set up my network. HomeGroups started off with Windows 7 if I'm not mistaken.
I never got very far with the NetBIOS idea because when I searched on NetBIOS for Windows 7 on Google, so as to get info on where the settings for it were, more than a few websites said that NetBIOS isn't used anymore even dating back to Win 7. Take a look yourself and don't kill the messenger.
On the other websites that seemed to imply that NetBIOS was alive and well I got the info on where the settings were. It seems that all my Discovery's are on but I'm set to DHCP and it was recommended that I keep it as that and not use WINS. All very confusing for a guy who knows just enough about networks to be dangerous and if I go beyond my knowledge I'm extremely dangerous. It was at this point that I decided not to mess with it.
But that didn't stop me from checking out my router settings. The only thing I found that seemed to have something possibly to do with broadcasting device names was something called RIP. I changed it from disabled to one of the other RIP options and promptly ended the recording of one of my wife's TV shows on WMC. Like I said, dangerous. I didn't anticipate and no prior warning was given that changing that setting would result in the router rebooting. Funny, no reboot when I changed it back to disabled. I was done.
I like my IP addresses very much. I will continue to use them on my network. They've served me well for the past 22 years or so. I don't need NetBIOS, UNC, FQDN or any other acronym from here on out. I don't want to talk about this anymore as it's given me a headache.

[IT Troll]

Sorry to hear you’ve had a bad time of it. NetBIOS is still very much a thing. Isn’t it the case that the only problem is with your Chromebook? I would concentrate on that end of things. Checking the Chromebook will do NetBIOS discovery from within it’s web browser. The other question mark is the Wi-Fi extender. However, it sounds like you’ve had enough of it.

You might want to reserve the IP for your PC on your router so that it remains the same and ensures your bookmarks keep working.

[Space]

Just wanted to add something that is related to this...

I just installed version 1.7.0.6 (my first one that uses the HTTP server) and I noticed that on the status page it lists links at the bottom with URLs like this:

http://htpc:9009/server.log

htpc is the name of my htpc, but my Win10 laptop is not able to connect to that because it does not know how to resolve "htpc".

I don't know if this is the ultimate answer, but I would suggest that this status page should just use relative links instead of hard coding in the name of the WMC machine.

In this way I can go to the status page using the IP address ("http:/192.168.0.100:9009/") and all the links on that page will be relative to the domain/IP address I used to get there (so for example "http:/192.168.0.100:9009/server.log").

Thanks

[garyan2]

Simple enough. Next release.

Question is, why does your laptop not resolve the server hostname? Is network discovery off on either, or the laptop wireless network setup as a Public network rather than a Private network? I haven't had any problems on any of my machines... even wireless to wireless, so either there is something I naturally do when setting things up that allow it to work, or some folks naturally do something else that prevent resolving the hostname.

[IT Troll]

Some of the discovery issues are device/browser dependent. My iPad will not resolve http://htpc:9009 (yep I used that too) in Safari or Chrome. However, I use an app called Infuse on the same iPad which happily discovers my HTPC and other machines by NetBIOS name.

In this case, installing the Apple Bonjour service may help with Safari. But nobody wants that.

[Space]

I'm not sure why my laptop doesn't resolve it but it is probably related to the fact that it belongs to my employer and it is used to connect via VPN to the companies network domain. They probably have any local networking things disabled so that they don't interfere with the work domain, but I really don't know much about Windows networking, so couldn't tell you exactly why...

[glorp]

On platforms which may not use NetBIOS (reliably), the easiest answer is to add an entry to the hosts file. Not a good solution when IPs are assigned dynamically, but then neither is using https://<IP>:<port> in that case. And it's easy enough to reserve the IP with whatever is doing DHCP on a home network.