Question about network paths

[heerssimpson 3]

Recordings were working fine, then all the sudden Emby stopped seeing any of my recordings. I can still record. Still has my recording folder set in settings under Live TV. Just not sure what is going on. Only thing I have changed recently was i changed the default save location in MCEBuddy to the subfolder where the recording originated. I have TV files in subfolders and in the Recording folder, so I really doubt that is the problem.

 

 

Attached is my log. Thanks for my help.

log.txt

[Luke 42085]

Have you tried running a library scan?

[Luke 42085]

@@heerssimpson Is your E: folder a network drive? because your system is throwing network errors related to that:

2017-02-20 15:09:31.3867 Error LibraryMonitor: Error in Directory watcher for: E:\TV Shows
    *** Error Report ***
    Version: 3.2.1.0
    Command line: C:\Users\simps_000\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe
    Operating system: Microsoft Windows NT 6.2.9200.0
    64-Bit OS: True
    64-Bit Process: True
    Processor count: 4
    Program data path: C:\Users\simps_000\AppData\Roaming\Emby-Server
    Application directory: C:\Users\simps_000\AppData\Roaming\Emby-Server\System
    System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available
    System.ComponentModel.Win32Exception
    No Stack Trace Available

Fix that and I would guess that Emby will see your content again.

[ebr 16193]

If it is a network drive, use a UNC path instead of a mapped drive.  These are the kinds of problems you will run into with mapped drives.

[heerssimpson 3]

A simple restart of the computer did the trick. I think changing it to a UNC path will fix this. Thanks for the feedback.

[Luke 42085]

Thanks for the update.

[kanipek 230]

A simple restart of the computer did the trick. I think changing it to a UNC path will fix this. Thanks for the feedback.

 

If you are planning to change the drive path to UNC I would suggest you use the IP address for (Optional) Shared Folder Name: \\192.168.x.x\foldername instead of \\servername\foldername.

 

If you are using a mixed environment - Windows - Android etc this will fix any issues with not being able to play media. For me I use windows(7) shares and have a couple of Android and Windows (10) clients. I always used Folder:

\\servername\foldername and (Optional) Shared Folder Name: \\servername\foldername when I set up the library. This worked fairly well (still had random can't play errors) when I only had Windows clients. When I added a couple of Android clients I would have "file no longer found" in library errors. Changing that Optional shared folder name to the ip address fixed it for me.

 

Something to do with cross platform networking. Hope that makes sense to you. Hopefully it helps, I did a lot of head scratching/searching trying to figure it out. A bonus in my case was a 75%+ decrease in time it takes for Kodi to do an intial  library scan - I was at 5 hours now it is about 1 Hour 15 Minutes.

[dcook 299]

Its because Windows clients can see the NETBIOS name and Linux can't

 

You can still use \\name but you would need to add entry to the Linux client's /etc/hosts file.

 

That being said IP Address will always work

 

 

 

 

If you are planning to change the drive path to UNC I would suggest you use the IP address for (Optional) Shared Folder Name: \\192.168.x.x\foldername instead of \\servername\foldername.

 

If you are using a mixed environment - Windows - Android etc this will fix any issues with not being able to play media. For me I use windows(7) shares and have a couple of Android and Windows (10) clients. I always used Folder:

\\servername\foldername and (Optional) Shared Folder Name: \\servername\foldername when I set up the library. This worked fairly well (still had random can't play errors) when I only had Windows clients. When I added a couple of Android clients I would have "file no longer found" in library errors. Changing that Optional shared folder name to the ip address fixed it for me.

 

Something to do with cross platform networking. Hope that makes sense to you. Hopefully it helps, I did a lot of head scratching/searching trying to figure it out. A bonus in my case was a 75%+ decrease in time it takes for Kodi to do an intial  library scan - I was at 5 hours now it is about 1 Hour 15 Minutes.

[kanipek 230]

@@dcook

 

That is good information! Thanks.

 

I don't have write access to do that on my android boxes unfortunately. Not able to root them - at least currently. Maybe someday. But good info none the less.

[mastrmind11 722]

@@dcook

 

That is good information! Thanks.

 

I don't have write access to do that on my android boxes unfortunately. Not able to root them - at least currently. Maybe someday. But good info none the less.

Generally speaking, you'll want to give your server a static IP anyway, so NetBios vs hosts is irrelevant.  I've never used anything but an IP address on my local LAN in a mixed environment, just for this reason.... everything understands IP.

[dcook 299]

However if you ever change ip scheme then you have to reconfigure everything.

 

By using proper names and having DNS records or even hosts files you never have to worry about ips.

 

General rule of thumb in IT Networking is to NOT hard code IPS, use DNS/DHCP instead.

 

 

 

Generally speaking, you'll want to give your server a static IP anyway, so NetBios vs hosts is irrelevant.  I've never used anything but an IP address on my local LAN in a mixed environment, just for this reason.... everything understands IP.

[mastrmind11 722]

However if you ever change ip scheme then you have to reconfigure everything.

 

By using proper names and having DNS records or even hosts files you never have to worry about ips.

 

General rule of thumb in IT Networking is to NOT hard code IPS, use DNS/DHCP instead.

Agreed, but I don't think we're dealing with building out an enterprise network infrastructure in this case.  It's pretty rare for the average home user to have to deal with subnets and masking, on average.