Failed Migration to Linux

Mike Flannigan mikeflan at att.net
Sat Aug 11 12:35:19 UTC 2012



On 8/11/2012 5:29 AM, users-request at lists.fedoraproject.org wrote:
> This still isn't terribly clear...
> do you mean that WINDOWS machines on the network can't see  Fedora
> as a member of the WINDOWS network? and vice-versa?

Yes sir.  All the other machines are Windows machines.


> If so, I suggest you probably need to:
> 1. make sure samba is installed. on my  F17 machine it's samba-2:3.6.6-92.fc17.1. I think it is a placeholder that brings in all the other necessary packages.
> But in case I'm wrong, you'd also need samba-client-2:3.6.6-92.fc17.1 and
> samba-common-2:3.6.6-fc17.1.
> 2. we used to use system-config-services to make sure samba server starts
> at boot, but I think in F17 that tool doesn't exist anymore. looks like
> we need to use "systemctl enable samba" followed by either "systemctl
> daemon-reload" or a reboot.
> 3. use the firewall configuration tool (system-config-firewall) to make
> sure the necessary ports in the firewall are open. (make sure there is a
> checkmark in the box for both "Samba" and "Samba  Client".)
>
> if you've already got the samba stuff installed, it may be that you
> only need to do #3 above. the default firewall is fairly closed, and
> it does not let samba stuff thru without tweaking.
>
> It's been a while since I've done this, so this is all from memory. I think
> it's at least near-correct, though, if not perfect.
>
> Good luck!

Thanks so much.  I am storing this information away
for the next time, which will probably be in a couple
weeks.  I just downloaded and installed VMWare on this
new Windows machine.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20120811/a41aef39/attachment.html>


More information about the users mailing list