muzicman0 84 Posted April 28, 2025 Posted April 28, 2025 Let me preface this by saying that I have been running a Windows server for quite a while with no issues (same file paths). Although, now that I think of it, I didn't use the optional network path on the Windows server. I recently (yesterday) converted my Emby server over to Linux. I have a SMB server that I use for my media. My TV library has 2 different folders: local mounts are /media/TV and /media/TV2 Optional Network mount points are: \\10.3.0.140\TV\TV and \\10.3.0.140\TV2 (as mentioned above, I didn't need this when I was running Windows) No matter what I did the network mount points for TV2 were being created as \\10.3.0.140\TV\TV2. Which doesn't exist, so I couldn't watch the episodes when the network path was required. I did fix it by changing TV2 to /media/alt_tv and \\10.3.0.140\alt_tv (obviously I changed my SMB server mount points as well). But I thought I should report it just in case it wasn't just a glitch in my system, but maybe a bug. 1
Luke 42077 Posted April 28, 2025 Posted April 28, 2025 Hi, thanks for reporting. We'll take a look at it.
muzicman0 84 Posted June 8, 2025 Author Posted June 8, 2025 (edited) Out of curiosity, was this something that has been fixed, or was it related somehow to just my system? Edited June 8, 2025 by muzicman0
Luke 42077 Posted June 8, 2025 Posted June 8, 2025 HI, we'd probably have to look at a specific example to be sure, but I think I recall a change related to this made on the beta channel. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now