9/4/2023 0 Comments Windows 10 samba server![]() ![]() (you have to right click and say 'run as Administrator')įind : c:\WINDOWS\system32\drivers\etc\hosts (you will need to show all files not only. Open Notepad (or any text editor) as Administrator ![]() This is a solution for Windows 7 (although it might work for other versions as well) (Use \\ServerName\sharename when connecting as the first user, but use \\ServerAlias1\sharename when connecting as the second user, \\ServerAlias2\sharename when connecting as the third user, etc.) (Use \\ServerName\sharename when connecting as the first user, but use \\X.X.X.X\sharename when connecting as the second user.)Ĭreate one or more DNS alias(es) for the server to use when you connect with the second (, third, fourth.) username. Use the IP address of the server when you connect with the second username. The general idea is, make Windows think it's connecting to a different server by using a different name. Update 3: The MS document linked above offers these two workarounds to enable connecting to the server as separate users. ![]() This works well if you have some shares that you want everyone to have read-write access to, and others that you want to be read-only for all but a select few users. Personally, I'd stick with individual users for each person, and consider using groups to control access to the shares. You'll have to reconsider your share strategy, and reconfigure Samba to follow that strategy. Update 2: If the users are already connecting to the server with one user, you won't be able to let them connect with a second user. Use the net use /delete command from Windows' command shell (Start -> Run -> cmd at the prompt type the command you may need to specify a share name). Reconnect to the server and make sure you give the proper username and password. Two ways I know of to do that:ĭisconnect any reconnect-at-logon network drives from that server. You need to disconnect the first connection before you can reconnect. (See Microsoft documentation at KB938120.) This means the Windows machine has already connected as a different user, and so your attempts to connect again, as the correct user, are failing. This is a client-side error - Windows only allows you to connect to a server as one user at a time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |