My file/web server is configured and running properly. I have no issues sharing directories via NFS until my firewall becomes part of the equation. But it's not as simple as it sounds...
I understand that I posted on this topic earlier Firewall Problem with Samba - openSUSE Forums, but I'm having problems when setting up Samba. When I disable the firewall, I am able to browse all the windows shares on my network. I have opened the ports as outlined in the link above.
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.
dear mr and mrs.. i need your help please.
I did Configuration samba at FC 17, i need make folder and subfolder share can access some samba users, but have error "//ip samba server/folder_share is not accessible. You might not not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions....
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 network that at the moment is isolated from the internet. We are going to connect it to an existing adsl line that has a firewall,but we want to add another firewall behind it as we do not have total control over the existing firewall. The only thing we want to allow is smtp access for one computer.
Running Fedora 17 x86_64. I have opened a few ports using system-config-firewall. After saving and appling the changes, the ports still are blocked. If I stop and start the firewall, things appear to be working. When the machine boots up, the ports appear to be blocked. If I stop and start the firewall, things work as expected.
Anyone see this type of behavior?
I used to be able to RDP to my work PC (Windows 7 Enterprise) whether it was on or off the domain.
Since the installation of Symantec Endpoint Protection (which turns on the firewall when the PC is off the domain), inbound RDP connections are being blocked when it's not on the domain.
However, I checked and there is a universal Allow rule for RDP in Windows firewall.
Obviously something
So what to do, I added port 139 like this site suggested.
http://empegbbs.com/ubbthreads.php/t..._printer_shari
with windows 7 firewall off, I can connect to server on another subnet, as this shows.
My ubuntu pc is on 192.168.1.103 and the windows 7 oc is at another router at 192.168.200.30
Attached Images
Screenshot from 2012-12-11 21:50: