F5F Stay Refreshed Power Users Networks Samba cannot be used on Windows platform.

Samba cannot be used on Windows platform.

Samba cannot be used on Windows platform.

G
GeorgePlaysFTW
Senior Member
261
07-09-2016, 07:00 PM
#1
You're trying to connect your Ubuntu Jellyfin server from Windows, but the shared drive isn't working as expected. After restarting the server (using the command you found), it still doesn’t respond when you try to log in. It seems like the issue might be related to network settings or permissions. Have you checked if the share is properly recognized on your Windows machine? Also, ensure that the correct username and password are being used. If you're using a remote desktop or file explorer, verify that the firewall isn't blocking the connection.
G
GeorgePlaysFTW
07-09-2016, 07:00 PM #1

You're trying to connect your Ubuntu Jellyfin server from Windows, but the shared drive isn't working as expected. After restarting the server (using the command you found), it still doesn’t respond when you try to log in. It seems like the issue might be related to network settings or permissions. Have you checked if the share is properly recognized on your Windows machine? Also, ensure that the correct username and password are being used. If you're using a remote desktop or file explorer, verify that the firewall isn't blocking the connection.

T
Thomas_EC
Junior Member
6
07-11-2016, 09:50 PM
#2
No, I'm not trying to connect to your Samba server via IP or hostname/NetBIOS.
T
Thomas_EC
07-11-2016, 09:50 PM #2

No, I'm not trying to connect to your Samba server via IP or hostname/NetBIOS.

C
Challlenger
Member
67
07-14-2016, 06:33 PM
#3
The issue seems related to permission settings, possibly restored by OCASAOS. If true, I recommend reinstalling Ubuntu and continuing with the approach that previously succeeded.
C
Challlenger
07-14-2016, 06:33 PM #3

The issue seems related to permission settings, possibly restored by OCASAOS. If true, I recommend reinstalling Ubuntu and continuing with the approach that previously succeeded.

R
rosie2435
Senior Member
475
07-18-2016, 12:59 PM
#4
I omitted that detail earlier. I refreshed Ubuntu before setting up Casa OS, but I hadn’t used it before. I just reinstalled Ubuntu today and installed Casa OS again, and now the problem is happening once more. The hard drives are still mounted at /media, just like before.
R
rosie2435
07-18-2016, 12:59 PM #4

I omitted that detail earlier. I refreshed Ubuntu before setting up Casa OS, but I hadn’t used it before. I just reinstalled Ubuntu today and installed Casa OS again, and now the problem is happening once more. The hard drives are still mounted at /media, just like before.

N
NecrosPT
Junior Member
10
08-02-2016, 02:32 PM
#5
I'm entering the IPv4 address of the Ubuntu machine. The path is "Music" and I've turned on the local file share. Update: it shows up with the login prompt, yet it won't connect even with the right password. It seems it's linking to another service.
N
NecrosPT
08-02-2016, 02:32 PM #5

I'm entering the IPv4 address of the Ubuntu machine. The path is "Music" and I've turned on the local file share. Update: it shows up with the login prompt, yet it won't connect even with the right password. It seems it's linking to another service.

Q
Questiero
Member
215
08-02-2016, 02:47 PM
#6
Wish I understood how Windows handles debugging connections better. I only remembered the -vvvv command for that. Can you verify these settings? Are the folder permissions correct for the intended users? Check Samba status with "systemctl status samba". Last time I checked, ping those IP addresses and see if they respond properly. If possible, have a Linux client attempt to connect to the Samba server and run -vvvvv.
Q
Questiero
08-02-2016, 02:47 PM #6

Wish I understood how Windows handles debugging connections better. I only remembered the -vvvv command for that. Can you verify these settings? Are the folder permissions correct for the intended users? Check Samba status with "systemctl status samba". Last time I checked, ping those IP addresses and see if they respond properly. If possible, have a Linux client attempt to connect to the Samba server and run -vvvvv.

P
pvpprobro
Member
141
08-02-2016, 11:46 PM
#7
I realized it was quite awkward. I didn’t have an SMB user set up. I resolved it by running sudo smbpasswd -a with the username and setting a new password. It’s now working perfectly. Thank you for your assistance.
P
pvpprobro
08-02-2016, 11:46 PM #7

I realized it was quite awkward. I didn’t have an SMB user set up. I resolved it by running sudo smbpasswd -a with the username and setting a new password. It’s now working perfectly. Thank you for your assistance.