Windows 10 login information for accessing samba share protected directory located on Ubuntu 18.04
up vote
1
down vote
favorite
Can someone give an example of login information (username and password) on Windows 10 for the samba protected directory which is located on Ubuntu 18.04?
I have created a user in Ubuntu and added smbpasswd for him, but I don't know how the username should look to be able to get into the protected directory.
Accessing a public directory from Windows is working without a problem.
18.04 login samba windows-10
asked Nov 15 at 20:10
SP.
84
|
show 4 more comments
up vote
1
down vote
favorite
Can someone give an example of login information (username and password) on Windows 10 for the samba protected directory which is located on Ubuntu 18.04?
I have created a user in Ubuntu and added smbpasswd for him, but I don't know how the username should look to be able to get into the protected directory.
Accessing a public directory from Windows is working without a problem.
18.04 login samba windows-10
asked Nov 15 at 20:10
SP.
84
Since the answer seems to be too obvious I'm assuming you get an error when you enter the username and smbpasswd password you created in Ubuntu. What is the path to the "Protected" folder on the Ubuntu machine.
– Morbius1
Nov 16 at 12:55
Ubuntu path for that directory is/samba/Protected. I made it like this setup here.
– SP.
Nov 16 at 20:05
Does the new user you created on the ubuntu machine have the same username as the one on the Windows client?
– Morbius1
Nov 16 at 20:11
No, it doesn't have the same name. Now I have created ubuntu user with the same name as windows user but still can get to the protected directory.
– SP.
Nov 16 at 20:24
Same password as the Windows user's login password?
– Morbius1
Nov 16 at 20:31
|
show 4 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Can someone give an example of login information (username and password) on Windows 10 for the samba protected directory which is located on Ubuntu 18.04?
I have created a user in Ubuntu and added smbpasswd for him, but I don't know how the username should look to be able to get into the protected directory.
Accessing a public directory from Windows is working without a problem.
18.04 login samba windows-10
asked Nov 15 at 20:10
SP.
84
Can someone give an example of login information (username and password) on Windows 10 for the samba protected directory which is located on Ubuntu 18.04?
I have created a user in Ubuntu and added smbpasswd for him, but I don't know how the username should look to be able to get into the protected directory.
Accessing a public directory from Windows is working without a problem.
18.04 login samba windows-10
18.04 login samba windows-10
asked Nov 15 at 20:10
SP.
84
asked Nov 15 at 20:10
SP.
84
edited Nov 16 at 14:57
asked Nov 15 at 20:10
SP.
84
asked Nov 15 at 20:10
SP.
84
asked Nov 15 at 20:10
SP.
84
84
Since the answer seems to be too obvious I'm assuming you get an error when you enter the username and smbpasswd password you created in Ubuntu. What is the path to the "Protected" folder on the Ubuntu machine.
– Morbius1
Nov 16 at 12:55
Ubuntu path for that directory is/samba/Protected. I made it like this setup here.
– SP.
Nov 16 at 20:05
Does the new user you created on the ubuntu machine have the same username as the one on the Windows client?
– Morbius1
Nov 16 at 20:11
No, it doesn't have the same name. Now I have created ubuntu user with the same name as windows user but still can get to the protected directory.
– SP.
Nov 16 at 20:24
Same password as the Windows user's login password?
– Morbius1
Nov 16 at 20:31
|
show 4 more comments
Since the answer seems to be too obvious I'm assuming you get an error when you enter the username and smbpasswd password you created in Ubuntu. What is the path to the "Protected" folder on the Ubuntu machine.
– Morbius1
Nov 16 at 12:55
Ubuntu path for that directory is/samba/Protected. I made it like this setup here.
– SP.
Nov 16 at 20:05
Does the new user you created on the ubuntu machine have the same username as the one on the Windows client?
– Morbius1
Nov 16 at 20:11
No, it doesn't have the same name. Now I have created ubuntu user with the same name as windows user but still can get to the protected directory.
– SP.
Nov 16 at 20:24
Same password as the Windows user's login password?
– Morbius1
Nov 16 at 20:31
Since the answer seems to be too obvious I'm assuming you get an error when you enter the username and smbpasswd password you created in Ubuntu. What is the path to the "Protected" folder on the Ubuntu machine.
– Morbius1
Nov 16 at 12:55
Since the answer seems to be too obvious I'm assuming you get an error when you enter the username and smbpasswd password you created in Ubuntu. What is the path to the "Protected" folder on the Ubuntu machine.
– Morbius1
Nov 16 at 12:55
Ubuntu path for that directory is
/samba/Protected. I made it like this setup here.– SP.
Nov 16 at 20:05
Ubuntu path for that directory is
/samba/Protected. I made it like this setup here.– SP.
Nov 16 at 20:05
Does the new user you created on the ubuntu machine have the same username as the one on the Windows client?
– Morbius1
Nov 16 at 20:11
Does the new user you created on the ubuntu machine have the same username as the one on the Windows client?
– Morbius1
Nov 16 at 20:11
No, it doesn't have the same name. Now I have created ubuntu user with the same name as windows user but still can get to the protected directory.
– SP.
Nov 16 at 20:24
No, it doesn't have the same name. Now I have created ubuntu user with the same name as windows user but still can get to the protected directory.
– SP.
Nov 16 at 20:24
Same password as the Windows user's login password?
– Morbius1
Nov 16 at 20:31
Same password as the Windows user's login password?
– Morbius1
Nov 16 at 20:31
|
show 4 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
As for this specific error message:
Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all
previous connections to the server or shared resource and try again.
The problem here is that when a user on Windows first makes contact with a server it automatically passes that users local login user name. If you have a public share it remembers that it took that user name successfully. When you try to connect to a Private share and don't pass the exact same username and password it thinks you are trying to access by another name. Microsoft never understood the use case for why you would want to do this on the fly.
Some workarounds:
[1] Create a username map of the Windows user to the local Linux user - this is useful for Win10 users who log into their systems with a Microsoft Account name.
** Create a file at /etc/samba/smbusers
** Map the local Linux user to the Windows user by adding the conversion to the file. For example:
luci = blzebub@hades.com
iwish = "Scarlett Johansson"
** Then add a reference to the map in /etc/samba/smb.conf in the [global] section:
username map = /etc/samba/smbusers
** And restart smbd:
sudo service smbd restart
[2] Make another connection to the Linux server.
Windows can address a Linux server 2 ( 3 in Win10 ) different ways. By hostname, by ip address, and for Win10 by mDNS name:
\ubuntuProtected
\192.168.0.100Protected
\ubuntu.localProtected
Even through all of these point to the same machine Windows sees them a three separate hosts.
[3] Map the "network drive".
When you map a drive you are given the opportunity to select the "connect using different credentials" option.
answered Nov 19 at 14:16
Morbius1
1,21627
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created withsudo adduser zombiein Ubuntu and password generated for that user withsudo smbpasswd -a zombie.
– SP.
Nov 19 at 19:06
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
As for this specific error message:
Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all
previous connections to the server or shared resource and try again.
The problem here is that when a user on Windows first makes contact with a server it automatically passes that users local login user name. If you have a public share it remembers that it took that user name successfully. When you try to connect to a Private share and don't pass the exact same username and password it thinks you are trying to access by another name. Microsoft never understood the use case for why you would want to do this on the fly.
Some workarounds:
[1] Create a username map of the Windows user to the local Linux user - this is useful for Win10 users who log into their systems with a Microsoft Account name.
** Create a file at /etc/samba/smbusers
** Map the local Linux user to the Windows user by adding the conversion to the file. For example:
luci = blzebub@hades.com
iwish = "Scarlett Johansson"
** Then add a reference to the map in /etc/samba/smb.conf in the [global] section:
username map = /etc/samba/smbusers
** And restart smbd:
sudo service smbd restart
[2] Make another connection to the Linux server.
Windows can address a Linux server 2 ( 3 in Win10 ) different ways. By hostname, by ip address, and for Win10 by mDNS name:
\ubuntuProtected
\192.168.0.100Protected
\ubuntu.localProtected
Even through all of these point to the same machine Windows sees them a three separate hosts.
[3] Map the "network drive".
When you map a drive you are given the opportunity to select the "connect using different credentials" option.
answered Nov 19 at 14:16
Morbius1
1,21627
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created withsudo adduser zombiein Ubuntu and password generated for that user withsudo smbpasswd -a zombie.
– SP.
Nov 19 at 19:06
add a comment |
up vote
0
down vote
accepted
As for this specific error message:
Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all
previous connections to the server or shared resource and try again.
The problem here is that when a user on Windows first makes contact with a server it automatically passes that users local login user name. If you have a public share it remembers that it took that user name successfully. When you try to connect to a Private share and don't pass the exact same username and password it thinks you are trying to access by another name. Microsoft never understood the use case for why you would want to do this on the fly.
Some workarounds:
[1] Create a username map of the Windows user to the local Linux user - this is useful for Win10 users who log into their systems with a Microsoft Account name.
** Create a file at /etc/samba/smbusers
** Map the local Linux user to the Windows user by adding the conversion to the file. For example:
luci = blzebub@hades.com
iwish = "Scarlett Johansson"
** Then add a reference to the map in /etc/samba/smb.conf in the [global] section:
username map = /etc/samba/smbusers
** And restart smbd:
sudo service smbd restart
[2] Make another connection to the Linux server.
Windows can address a Linux server 2 ( 3 in Win10 ) different ways. By hostname, by ip address, and for Win10 by mDNS name:
\ubuntuProtected
\192.168.0.100Protected
\ubuntu.localProtected
Even through all of these point to the same machine Windows sees them a three separate hosts.
[3] Map the "network drive".
When you map a drive you are given the opportunity to select the "connect using different credentials" option.
answered Nov 19 at 14:16
Morbius1
1,21627
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created withsudo adduser zombiein Ubuntu and password generated for that user withsudo smbpasswd -a zombie.
– SP.
Nov 19 at 19:06
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
As for this specific error message:
Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all
previous connections to the server or shared resource and try again.
The problem here is that when a user on Windows first makes contact with a server it automatically passes that users local login user name. If you have a public share it remembers that it took that user name successfully. When you try to connect to a Private share and don't pass the exact same username and password it thinks you are trying to access by another name. Microsoft never understood the use case for why you would want to do this on the fly.
Some workarounds:
[1] Create a username map of the Windows user to the local Linux user - this is useful for Win10 users who log into their systems with a Microsoft Account name.
** Create a file at /etc/samba/smbusers
** Map the local Linux user to the Windows user by adding the conversion to the file. For example:
luci = blzebub@hades.com
iwish = "Scarlett Johansson"
** Then add a reference to the map in /etc/samba/smb.conf in the [global] section:
username map = /etc/samba/smbusers
** And restart smbd:
sudo service smbd restart
[2] Make another connection to the Linux server.
Windows can address a Linux server 2 ( 3 in Win10 ) different ways. By hostname, by ip address, and for Win10 by mDNS name:
\ubuntuProtected
\192.168.0.100Protected
\ubuntu.localProtected
Even through all of these point to the same machine Windows sees them a three separate hosts.
[3] Map the "network drive".
When you map a drive you are given the opportunity to select the "connect using different credentials" option.
answered Nov 19 at 14:16
Morbius1
1,21627
As for this specific error message:
Multiple connections to a server or shared resource by the same user,
using more than one user name, are not allowed. Disconnect all
previous connections to the server or shared resource and try again.
The problem here is that when a user on Windows first makes contact with a server it automatically passes that users local login user name. If you have a public share it remembers that it took that user name successfully. When you try to connect to a Private share and don't pass the exact same username and password it thinks you are trying to access by another name. Microsoft never understood the use case for why you would want to do this on the fly.
Some workarounds:
[1] Create a username map of the Windows user to the local Linux user - this is useful for Win10 users who log into their systems with a Microsoft Account name.
** Create a file at /etc/samba/smbusers
** Map the local Linux user to the Windows user by adding the conversion to the file. For example:
luci = blzebub@hades.com
iwish = "Scarlett Johansson"
** Then add a reference to the map in /etc/samba/smb.conf in the [global] section:
username map = /etc/samba/smbusers
** And restart smbd:
sudo service smbd restart
[2] Make another connection to the Linux server.
Windows can address a Linux server 2 ( 3 in Win10 ) different ways. By hostname, by ip address, and for Win10 by mDNS name:
\ubuntuProtected
\192.168.0.100Protected
\ubuntu.localProtected
Even through all of these point to the same machine Windows sees them a three separate hosts.
[3] Map the "network drive".
When you map a drive you are given the opportunity to select the "connect using different credentials" option.
answered Nov 19 at 14:16
Morbius1
1,21627
edited Nov 19 at 15:09
answered Nov 19 at 14:16
Morbius1
1,21627
answered Nov 19 at 14:16
Morbius1
1,21627
answered Nov 19 at 14:16
Morbius1
1,21627
1,21627
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created withsudo adduser zombiein Ubuntu and password generated for that user withsudo smbpasswd -a zombie.
– SP.
Nov 19 at 19:06
add a comment |
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created withsudo adduser zombiein Ubuntu and password generated for that user withsudo smbpasswd -a zombie.
– SP.
Nov 19 at 19:06
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created with
sudo adduser zombie in Ubuntu and password generated for that user with sudo smbpasswd -a zombie.– SP.
Nov 19 at 19:06
Solved. True, on the first contact, it passes users local login user name. I tried with approach [2] and [3]. Both approaches are working. For credentials I used username of user that I created with
sudo adduser zombie in Ubuntu and password generated for that user with sudo smbpasswd -a zombie.– SP.
Nov 19 at 19:06
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093290%2fwindows-10-login-information-for-accessing-samba-share-protected-directory-locat%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Since the answer seems to be too obvious I'm assuming you get an error when you enter the username and smbpasswd password you created in Ubuntu. What is the path to the "Protected" folder on the Ubuntu machine.
– Morbius1
Nov 16 at 12:55
Ubuntu path for that directory is
/samba/Protected. I made it like this setup here.– SP.
Nov 16 at 20:05
Does the new user you created on the ubuntu machine have the same username as the one on the Windows client?
– Morbius1
Nov 16 at 20:11
No, it doesn't have the same name. Now I have created ubuntu user with the same name as windows user but still can get to the protected directory.
– SP.
Nov 16 at 20:24
Same password as the Windows user's login password?
– Morbius1
Nov 16 at 20:31