How do I make samba share available as Windows 7 Homegroup?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How do I make samba share available as Windows 7 Homegroup?
I have recently installed Windows 7. I'm running samba 3.0.37 on gentoo. I'd like to be able to access a samba share as part of a Homegroup in Win7. Is such a thing possible or are Homegroups not compatible with samba?
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1
This is a copy of what Micor$oft says about Homegroup.
HomeGroup takes the headache out of sharing files and printers on a home network. Connect two or more PCs running Windows 7, and HomeGroup makes it easy to automatically start sharing your music, picture, video, and document libraries with other people in your home.
Looks like it is W-7 to W-7 only.
There is no reason you can not share files and directories on a linux machine with a Win-7 system though. To me it looks like a 'wizard' to make things easier for the technically challenged. I don't think there is any reason W-7 can not share out files to a linux system, assuming the correct software is installed and configured correctly.
u need not be in the same home group to share your samba share with windows if it is in the same network or u r able to ping through routing protocols. u need to search for the samba server through windows search computer options or through network sharing wizard
I cannot find a way to share through the Win 7 Homegroup, but I have achieved the same result by using the following steps in Win 7:
1. To be able to login via your network to Win 7, follow these steps:
a. Click on "Start"
b. In the "Search programs and files" box type "gpedit.msc"
c. When the "Local Group Policy Editor" (LGPE) box opens go to:
Windows Settings / Security Settings / Local Policies / Security Options / and locate "Network Security: LAN Manager authentication level" in the right pane.
d. Double click on "Network Security: LAN Manager authentication level" and a properties dialog box will appear
e. In the drop-down menu select "Send LM & NTLM - use NTLMv2 session security if negotiated," apply the changes and quit the LGPE.
2. Check if Windows Live ID Sign In Assistant is installed on your Win 7 Box, if it is uninstall it.
3. Right click on Win 7 folders you want to share, select properties and click on the Share Tab and enable sharing - NOTE: you may need to click on "advanced sharing" and select "Share This Folder."
Thanks, but it seems that gpedit.msc is not provided with Home Premium. It would be good if I could acquire it separately (without breaking the license of course). Seriously anti-competitive to make it so difficult to share files.
I've made the registry changes recommended on the Samba site, but my W-7 box still does not see anything but itself.
Thanks, but I must be doing something wrong somewhere...
I made the changes to the registry, and updated samba to 3.4.8, but Windows 7 Home Premium still does not see the linux box. I've heard that for an extra $90 or so I can upgrade Windows to include a 'policy editor' or some such which could help, but it's not worth it.
I have a wireless access point with 4 ports for wired connections. Windows is wireless and linux is wired. Is this relevant?
Win7 has no problems accessing samba shares on a *nix box if you have samba set up correctly, you have samba running on the linux box, you have your smb.conf set up.
If nothing else map a network drive to the linux server on the win7 box. You can't be part of a win7 homegroup but you can be part of a workgroup. If you have folder perms on win7 to allow it your linux box can access the shares on the win7 box.
Post your smb.conf
That's where it is on this FreeBSD box. I don't know where gentoo keeps it. Look for it.
You should have as a minimum of something like
workgroup = MYHOME
netbios name = dell123
server string = samba server
security = share
path = /usr/home/username/share
guest ok = yes
read only = no
Read the options for your smb.conf. Then make sure you have something shared.
Post the output of
ps -ax | grep smb
samba has to be running.
Can you ping the linux box? Can you use ssh into it? If you can then you don't have samba set up right. If you can't ping it or log into it remotely, fix that.
Thank you, danny_kurniawan!! Your solution worked perfectly for me. One of my clients insists on ordering computer equipment contrary to my recommendations. So they got Windows 7 Home Premium instead of Professional. I couldn't get to to connect to their Samba server, but danny_kurniawan's tip did the trick instantly. It's too bad their stubbornness will cost my customer $200 in fees to me (I've spent 2 hours on this).