Are there plans to make SAMBA work with, hate to say it, a Windows environment by default? I've been very successful using it between Linux machines, but I've never been able to get a Windows machine to access a Linux share. I have been successful to get a Windows machine to at least see the Linux share, just not access it.
-
-
Re: SAMBA
I'm running Kubuntu 7.10 x64 and I have never had a problem with SAMBA. Windows connects up to my Kubuntu box with no problems. All I did was install the SAMBA packages from the repos and share the folders. Never tried to write to the Kubuntu share though so I don't know if that would work. -
Re: SAMBA
Mine is a 32bit system and SAMBA has always been the default install from Kubuntu. I did make a few changes to include Workgroup and such, but nothing further. As I said, the Windows systems see the share just fine, just can't log into the share. Windows XP always has the shaded Guest account as username, so I don't know how to get around that. I tried mapping it directly, but agian, WINXP wants to use the Guest account although I specify the correct user Account. Windows 2000 doesn't give the shaded Guest account but refuses to connect. I get no other errors other than the UN/Password error. Just thought I'd put this here to get more feed back, most other peoples posts didn't have anything to do with what I just described, so I never really got any further. Thanks for responding.Comment
-
Re: SAMBA
I'd love it if Samba could solve my networking issues. I have not been able to share files over my local network at all. I run a desktop and a laptop, and both of them are 100% Kubuntu machines.
I haven't tried Samba because I thought that was only for sharing between Windows and Linux machines.
Am I mistaken?
MatthewComment
-
Re: SAMBA
As far as I know it is used between Linux machines as well. Could be wrong but I don't think I am. I wasn't able to share between Linux until I did do the Mods to SAMBA as I mentioned above.Comment
-
Re: SAMBA
Hmmm... I've never had a problem doing it, but there is one caveat I've learned from experience that should be kept in mind. Make sure you try to open the main shared directory from the Windows machine first, not a subdirectory.Originally posted by MoonRise
For example: On your Linux server, say you share out \\servername\data. Now, if you try to access, from a Windows box, '\\servername\data\homemovies' it will fail (even though that directory exists). You *have* to access '\\servername\data' first to get authentication to work, because the other UNC path doesn't equate to an actual drive mapping.
-JSpecs: Intel Core 2 Quad Q6600 (@3Ghz), G.SKILL 4GB DDR2 1066, ASUS Striker II Formula MB, Asus EN9800GTX+ Dark Knight, ABS Tagan BZ800 PS, Antec 900 Case.Comment
-
Re: SAMBA
I have to say, wireless configuration seems to be the last great unknown territory for me in Linux. I just can't get it to work.
Can someone help me understand what the difference is between setting up a Samba, NFS, or Zeroconf, network folder?
All I want to do is be able to access a certain folder from my laptop, and print from my laptop, via a wireless connection.
MatthewComment
-
Re: SAMBA
Moonrise, Have you set a username and password for SAMBA? I know the first time I connected from Windows I needed a username/password and it doesn't work to use your Kubuntu logon, you must use the SAMBA user/password. Also it is more for Windows to Linux sharing, not so much Linux to Linux. Don't get me wrong it can be used but NFS is better in my book.
MatthewSchenker, I haven't used used Zeroconf but with SAMBA and NFS you have to first install the packages then set the shares (this can be done in the properties of the folders). You should be able to check to share the folder in NFS, SAMBA, both or none. With SAMBA you will need to setup a username and password (not sure of the exact command offhand) then you should be able to connect from Windows but it will ask you for the username and password. SAMBA's .conf file is pretty easy to edit manually if you hit a snag. To connect to a Windows share from Linux though you will need a program like SMB4K or pyNeighborhood. I use pyNeighborhood and it works great. As for NFS I have only set it up on my FreeNAS box so I'm not sure how the setup goes on Kubuntu really but you should be able the set the shares through the folder's properties. To connect to them you mount them. I am not at my Kubuntu box right now so I may be slightly off. I hope this helps out though.Comment
-
Re: SAMBA
Yes it's the Windows to Linux. I do have a UN/PW set and that works the way it should Linux to Linux. The real problem I have is on the Windows machine. It is XP Professional in a Domain, but the UN section always comes defaulted as a greyed out Guest account. Simple Sharing is off on the XP machine and the local security policy is set accordingly as well but yet that guest account stays.Comment
-
Re: SAMBA
Is the SAMBA .conf set to the domain? I have connected to SAMBA using a laptop that is set use a domain but never had SAMBA try to be part of the domain. You may want to try turning Simple Sharing on and see if that makes a difference. I know SAMBA can get sketchy at times and restarting the SAMBA service after changes and even rebooting the XP machine at times helps.Comment
-
Re: SAMBA
I've tracked down some of the issues. First the one with XP's insistence on using Guest, but lets forget about this for the moment and move on to WIN2000 which doesn't limit a user to Guest. A Win2000 machine actually lets me enter the UN, but won't connect either. So I've looked at the SAMBA conf file and took out the "valid users = xxxxxxxxx" entry. All windows machines can then enter the share, but without asking for a PW. I won't it to use the UN/PW. So, if a WIN2000 machine can access this way when putting the "valid users = xxxxxxxx" back in, why does it not seem to authenticate? What am I missing there? I get that solved, I can then get the XP issue solved.Comment
-
Re: SAMBA
I would try to recreate the UN/PW using "sudo smbpasswd -a <username>" then restart the SAMBA server "sudo /etc/init.d/samba restart" then try to access it from Win2k and see if you can authenticate. If not then I'm not sure but I did see a post in Ubuntu Forums with someone having the same problem so your not alone. Unfortunately though there was no solution there.Comment
-
Re: SAMBA
so your not alone.
Sorry, just couldn't help myself on that.
Anyway, I'll definitely give that a try. Thanks!
Comment
-
Re: SAMBA
That didn't work. Thanks, though. I appreciate some of the information you gave me. That helped me some.Comment
-
Re: SAMBA
Well, I take that back. Tried it one more time. Same changes as you mentioned and it now works!!! I never thought I'd get that, but it worked!!!! Yea!!!! Thanks!
I restarted SAMBA, but it must of taken a little while to "take"??Comment
Comment