So that we can quash this issue once and for all, what do you need for me to prove what NetBIOS names and AD domain membership exists? Being able to ping each other shows you have network connection, but AD relies on DNS and your standalone server probably isn't in the windows DNS. When I said can you browse via IP, I meant from Windows. NetBIOS domain names (what you call a workgroup) are not just for workgroups, they are also used in AD domains.
How should I try to connect to the remote server (Windows DC)? File and folder sharing is currently on for certain users, and am able to access with other Windows computers.
Neither system recognized each other's share, but each are able to ping each other, and are on the same network (aside from a private IPv6 address). I tried connecting via Windows Explorer, Pi's Nautilus, and through smbclient. Workgroup names are for hosts not in a domain.įor accessing the remote host via IP (I assume with smbclient?), but I am not able to authenticate. There is an initial contact followed by a "protocol negotiation" where the two systems agree upon the highest level of the smb dialect they can both use.Īnd you don't have to "discover" the server ( so you don't have to enable SMB1 on the Win10 client ) if you don't want to do so.In Windows Server, it lists "" as the domain name, even under the computer properties. You should see the Win10 machine accessing your share using SMB3_11. It is connecting to it with SMB3:Ĭonnect to the samba share from Win10. It has no choice since it is the only way it can do it without implementing WS-Discovery on the Server.īut it is not connecting to the Samba server with SMB1. It is "discovering" the Samba server via NetBIOS under SMB1.
#RASPBERRY PI SAMBA WINDOWS 7 HOW TO#
I don't know how to get windows to pop up the box that win7 did andĪsk me for the login id and password for the share setup in samba which was in no way related to the login id of the windows computer. It seems to me all these fixes make it work on smb1 which is not secure, and would force me to make the ubuntu box have the same loginĬredentials as the windows box which i don't think is secure either. Username and password as credentials and does not asking me to enter anything which fails. Pop a box up where i could put in the user name and password setup with samba and all was fine, windows10 seem to only send its own So if windows is has a login of USERNAME:PASSWORD and ubuntu samba has a login of OTHERUSER:OTHERPASSWORD under win7 it would Shares in ubuntu is not the same as windows, and i don't want it to be the same. When connecting the the shares without asking me to enter anything, which fails of course because the username and password for the It seems windows sends the windows10 username and password to ubuntu I can see the shares, i cannot connect to them. I saw and read hundreds of these links I initially could not see the shares at all and did turn smb1 on to see them, but that is not my issueĪt this point.
#RASPBERRY PI SAMBA WINDOWS 7 WINDOWS 10#
Same login and password i can see all ubuntu and raspberry pi shares in the network sectionĪs uneducated as I am (in most things but not all) it seems to me that you are describing a Windows 10 problem. I access them just like it did under windows 7.Īs it stands now i can only access win10 shares between windows10 computers that have the Have to stay the same and want windows 10 to ASK ME FOR THOSE credentials the first time I don't want to create a user in samba that matches the windows box i want the user i already Without making the share public in ubuntu I want it to be password protected. The share under network instead of just failing saying it cannot access or find the share location How do i get it to ASK ME FOR CREDENTIALS when i click How the hell do i access a samba share on ubuntu WITH A USER ID AND PASSWORD that is not Give me a popup window to put in the login information. This is driving me crazy i have exisiting samba shares on this server that worked fine under windows 7īut under win10 i can see them after turning on smb1 but i cannot access them and they do not
0 kommentar(er)
