Hello everybody i hope some one could help me regarding samba.. i am running a FC13 acting as a samba server & an IP of 192.168.0.3.. I have already installed samba from the fedora core repo.. I can see my samba server on my winxp client.. but everytime i tried to access the samba share a windows message appears
I've successfully shared some family photos on my server (Fedora 17) using Samba. This share works perfectly provided SeLinux is set to permissive. My wife can access the whole photos directory tree from her XP computer. However, the minute I set SeLinux to enforcing her access disappears.
am using fedora 17 with ubuntu and windows machines for educational purposes
i installed samba, disable SElinux, configure firewall to work with samba and i can access fedora samba shares but my fedora can't access other computer's samba shares with the graphic file manager only on terminal using this commands:
smbclient //192.168.1.4/Downloads
Enter itami's password:
smb: \>
its gr
I have a few conditions to meet with a new samba setup.I want to migrate a windows based share to a linux samba share. However this time the share is in the regular corporate LAN and I do not have the rights to add this samba server to the corporate windows domain.
Assalam o Alaikum!
After configuring and starting service of samba, when I access shared folder from windows XP it gives this error " Network Route was not found".
My server IP 192.168.1.252, client is on same network.
selinux is disabled
smb,conf:
Code:
workgroup = WORKGROUP
server string = Samba Server Version %v
; netbios name = MYSERVER
interfaces = eth0 192.168.1.252/24
hos
I have to set SELinux setenforce Permissive in order to give access to my samba share. I wonder if there is proper way to configure SELinux policy for fedora 17 as good admins do.
I have to set SELinux setenforce Permissive in order to give access to my samba share. I have also enabled null password in smb.conf for user admission as it was a simple way. I wonder if there is proper way to configure SELinux policy for fedora 17 as good admins do.
I am trying to setup a home server from Samba 3.2, however, on the client end (running Windows Vista) the mapped network drive is viewable and I can also open any files within the main shared folder. The issue is that I cannot create any files from Vista, nor copy anything into there.
I've recently upgraded a Fedora 11 install being used as a Samba server on a small network to Fedora 12 via preupgrade. Upon reboot, I was not able to connect to the server. I found that shutting down SELinux and recreating the (only) user for the server allowed connection to the shares.