![]() The LMHOSTS file on the windows PC has an entry for the Linux server. Here are some further details concerning the configuration: This action causes the shares to behave correctly (reads and writes are generally done at 10 MB/sec or better) until I reboot the PC again, at which time the aberrant behavior resurfaces. The one odd aspect to the problem is that I can make it go away by changing the Windows 10 PC's work group name to something other than usual value (WORKGROUP), changing the work group name back to WORKGROUP and rebooting the PC. I even went so far as to purchase a new NIC for the Windows 10 PC, but the behavior has not changed. I have tested the Windows 7 PCs on the same network port where my Windows 10 PC is located. All other PCs (running Windows 7) work just fine. I have done extensive troubleshooting of the problem and found that this problem is specific the the one Windows 10 PC that I have. I also notice that the Linux server does not show up when browsing the network on the WIndows 10 PC, but it does show up when browsing the network from the Windows 7 PCs. The problem is aggravated with larger file sizes. ![]() The problem manifests with data writes that are exceedingly slow and generally time out before they complete. My problem is with writing data to those shares from my Windows 10 Home PC. Since the entire problem is a client side windows problem, I prefer doing it this way.I have a Linux server with file shares on my local network. ![]() The reason this works, is because windows needs to think it is connecting to different servers.Īrguably, you could also set up your own home DNS server, but I prefer faking a bunch of entries in the hosts file (which gets evaluated before your windows machine asks the DNS for help). Navigate to the following path: Computer Configuration > Windows Settings. Whatever you put into the hosts file will need to mach what you call the server when you map the network drive. Open Run box, type gpedit.msc and hit Enter to open the Local Group Policy Editor. Note that the names above are totally up to you. Once you close and save you can "Map a network drive" like so: \\tomsdocs\docs as user tom ![]() Now add the following lines to the hosts file: 192.168.0.100 tomsdocs tomsdocs you want to connect as tom to docs, as fred to stuff and as jon to pics 3 samba shares on your samba server (i.e. (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. Over Samba? There shouldn't be any problems as long as the username & password are correct both connections should happen correctly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |