Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello Folks! Noobe here! I've upgraded one of my computers to Mint 17.1 and am having issue browsing the network as clicking on my workgroup (mshome) is requiring input of a username and password. I've seen similar questions asked in several forums including this one but there has never been a resolution that has worked for me. The smb.conf has been modified to include the new workgroup name and it can be seen but not opened. At the moment I am transferring files via flash drive but that is a PITA. I have another computer running Mint 17 that works just fine. I even tried to copy the smb.conf file but ran into compatibility problems. I'm sure I'm not the only one with this problem so any help would be much appreciated. Thanks in advance. Oh yeah, one Mint 17.1, one Mint 17 and three Win 7 machines on the network.
Otherwise your looking at permissions issues. On the Windows machine, ensure the user account the Linux machine is connecting to has read write permissions on both the NTFS partition as well as the Microsoft file share. Other possible options would be to create a Windows admin account for the Linux machine to connect to and just connect to the primary hidden share such as \\mycomputer\C$ Another option might be to setup an FTP server. One word of advice, mounting a Windows shared folder on a Linux network drive, you would have to be very careful of exactly what you do on that partition. Linux is powerful enough to do things to Windows that Windows don't like.
Thanks for the reply. I'm not sure that it is permission related but could be. On my Mint 17 machine if I click "Network" in the tree all my shared folders show up but on the Mint 17.1 machine clicking on "Network" brings up "Windows Network" which brings up "MSHOME". Clicking on "MSHOME" should bring up all shared folders on the network but instead it brings up a window asking for a user name and password. Obviously something changed between Mint 17 and 17.1 and that is what I'm trying to figure out. I'm sure folks running 17.1 are able to view their network shares or I'd be able to hear their shouts and screams all the way out here! Thanks again.
Sounds like you need to enter a new configuration to save the username and password since it is a new install? Does the username and password work when you enter it?
Thanks for the reply, Joe. I can log into Mint without issue using my user name and password but nothing seemed to work to log into "MSHOME" I may have resolved my problem or at least part of it. On the Mint 17.1 machine I opened samba and went to preferences and created a user. I can now see the Windows shares as well as the shares on the Mint 17 machine. However, I cannot see the shares on the 17.1 machine from anywhere else on the network nor the 17.1 machine either. At least I can transfer files out of 17.1 now. Thanks for your help!
Ah yes, being able to see them verse being able to access them. I can not give you an exact answer but you will want to look for any options for the "Windows Browser Service" on the samba settings that ties into the Client for Microsoft Networks protocol found on the windows network adapter settings. This is also notorious as your network grows in size, be it linux or windows sometimes you just got to leave a new workstation turned on for a day before it eventually propagates.
Thanks again, Joe. I appreciate your patience with my ignorance. Thanks for your prompt replies! Hopefully I may be able to help you someday but unfortunately my field of expertise is limited - maybe lawnmower repair or mousetrap setting! Thanks, Canie Adams
The netbios name needs to be unique for the 17.1 machine and by default samba uses the computers hostname. At first glance it appears that the netbios name is mshome versus the workgroup name. Make sure you restart samba after making any changes.
You can view all of your computer/shares by using the console command smbtree. Just press the enter key when asked for a password.
Thanks for the reply, Michael. I thought everything was working acceptably until today when I tried to transfer a file out of my 17.1 computer. Back to requiring a password for my workgroup (mshome). My samba user is still intact so I'm at a loss again. I ran the smbtree command and all my shares are there including the linux assigned name of this computer (xxxxx-HP-Compaq-dx2250-Microtower server (Samba,). This has become a real thorn in my butt. If there were an easy way I'd go back to 17. Thanks again to everyone for their help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.