Question about folder permissions

[clarkss12 299]

It appears that Emby has stopped recording my scheduled TV shows............  The last recoded shows was June 8, so it has missed a lot of recordings.  Threes company is scheduled to record today at 4pm, but I doubt it will record.  See attached photos.

[clarkss12 299]

As expected, nothing recorded.........

What can I try???

[Carlo 4552]

Hi, have you looked at the server log to see why it didn't record?
Feel free to upload it here and we can look at it for you.

[clarkss12 299]

I reset my router, I have some more recording scheduled in a few minutes........ It is a network issue.

[clarkss12 299]

It is working again, but something is not correct with my Network.  Here is the server log.

embyserver.txt

[Carlo 4552]

This looks like a permission problem trying to write to 192.168.10.191

The user name or password is incorrect. : '\\192.168.10.191\E\Emby Series Recordings\Three's Company (1977)\Season 3'

[clarkss12 299]

You are probably correct, I did go into the miniPC that has the 3 external drives, and RE_DID the sharing.............  As I recall that PC did do an update a couple of days ago.........  I hate Windows.  I probably should run Linux on that miniPC, and avoid all this Windows crap....   

Thanks for your help, as usual.

[Carlo 4552]

This should be too hard to reset.  If you can't figure it out, shoot me a PM and I can remote in and give you hand with it.

Edited June 12, 2021 by cayars

[clarkss12 299]

10 hours ago, cayars said:

This should be too hard to reset.  If you can't figure it out, shoot me a PM and I can remote in and give you hand with it.

Thanks for the offer, but it is half-as*ed working right now.  

[clarkss12 299]

I am still having network path issues.  I am now thinking it is an Emby issue, by not accepting the network path.

I connected a different external hard drive and a different Windows 10, miniPC, and still have the same issue. I can map the external hard drive, and it shows the IP address, but Emby can't use that address. That external drive even shows up using Windows explorer on a different Windows machine.

I have an Android powered file server with two internal drives, and it do not have that issue.

So, different Windows PC, with different external hard drive, and Emby can't "see" the network path.

see photos

[Carlo 4552]

Above all you gave it was a server address but no share name.

Try \\192.168.1.101\ShareName

[clarkss12 299]

1 hour ago, cayars said:

Above all you gave it was a server address but no share name.

Try \\192.168.1.101\ShareName

Tried that also, still no workeee...........

[Carlo 4552]

What shows up in File Manager when you browse the 192.168.10.83 link?

Does the user running Emby Server have permissions to the share?

[clarkss12 299]

3 minutes ago, cayars said:

What shows up in File Manager when you browse the 192.168.10.83 link?

Does the user running Emby Server have permissions to the share?

Here is a photo of what the Windows file manager shows.... the BeelinkL55 is the 192.168.10.83.  The "D" folder is the attached external hard drive.

I have set permissions for everyone to have read/write capabilities..

 

[Carlo 4552]

That's showing a different name.  What happens when you view 192.168.10.83?

You could of course try using \\BEELINKL55\d as the UNC in Emby to see if it can access it that way.

[clarkss12 299]

Here is the windows explorer showing another miniPC with 3 different hard drives attached......... the BeelinkJ45 is 192.168.10.191.  Emby can't "see" those IP addresses on two different machines....  I am at my desktop computer taking screenshots of the Windows file manager, so those drives are accessible to my networked devices, EXCEPT Emby......

Everything worked as it should until about a week or two ago.......

 

[clarkss12 299]

4 minutes ago, cayars said:

That's showing a different name.  What happens when you view 192.168.10.83?

You could of course try using \\BEELINKL55\d as the UNC in Emby to see if it can access it that way.

\\BEELINKL55\d  worked.......

[clarkss12 299]

6 minutes ago, cayars said:

That's showing a different name.  What happens when you view 192.168.10.83?

You could of course try using \\BEELINKL55\d as the UNC in Emby to see if it can access it that way.

Entering the IP address numbers does not work, but it used to.

 

[Carlo 4552]

You are using "D" in one spot and "d" in another spot. Try using \\191.168.10.83\d since that is what the share name shows as.

 

[clarkss12 299]

8 minutes ago, cayars said:

You are using "D" in one spot and "d" in another spot. Try using \\191.168.10.83\d since that is what the share name shows as.

 

Little d did not work either, however, I did have a circle going round and round......

 

EDIT, disregard, I use the wrong IP....  BUT, with the correct IP it still does not work

Edited June 14, 2021 by clarkss12

[clarkss12 299]

I also have a file server running on an Android Box that has 2 internal hard drives.  When I input the IP address "192.168.10.185" and click the magnifying glass, it shows me the folders in that server.........

This device works as it should, only the Windows is not working correctly under Emby.

[Carlo 4552]

I don't think it's a 191 address as that would be a public IP not local.

What IP do you get if you ping BEELINKL55 ?

[clarkss12 299]

7 minutes ago, cayars said:

I don't think it's a 191 address as that would be a public IP not local.

What IP do you get if you ping BEELINKL55 ?

 The 191 came from you....... haha..... I copied and pasted your information.  I later saw that 191 and changed to 192.  Anyway, here is what ping shows.

[Carlo 4552]

32 minutes ago, clarkss12 said:

 The 191 came from you....... haha..... I copied and pasted your information.  I later saw that 191 and changed to 192.  Anyway, here is what ping shows.

Oh that's funny.  Sorry about that.

Try ping -4 BEELINKL55 which will force it to return an IP4 address.

[clarkss12 299]

9 minutes ago, cayars said:

Oh that's funny.  Sorry about that.

Try ping -4 BEELINKL55 which will force it to return an IP4 address.