similar to: NFS problem

Hi Folks, I'm using VMWare on a Linux Host (CentOS) with a Linux-Guest Sidux). And I'd like to use NFS. Furthermore I'd like to use the Firewall in CentOS with this little GUI. If I activate this firewall then my Guest says "no route to host" on mounting nfs. Firewall disabled -> no problem occurs. Is there a solution to use firewall _and_ nfs ? Please, no iptables

Hello everyone, I am setting up a new system for use as a testing/demo/trial-and-error system. I have installed CentOS 4.4 on it. There is not an X-environment, so I will need to fix this from the command line (via ssh access). I am trying to do an nfs export from this box to another on my internal home network. I have figured out that it is a firewall issue on the CentOS box (I turn off the

An embedded message was scrubbed... From: Niki Kovacs <contact at kikinovak.net> Subject: Re: [CentOS] Getting started with NFS Date: Sat, 04 Jul 2009 10:33:31 +0200 Size: 1377 URL: <http://lists.centos.org/pipermail/centos/attachments/20090704/b8ff2d37/attachment-0003.eml>

Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root at saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to

Below is my firewall rules for iptables. everything is working fine except for NFS I cannot mount my drive. If I turn off iptables I can mount. Looking at this : http://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-nfs.html Important In order for NFS to work with a default installation of Red Hat Enterprise Linux with a firewall enabled, IPTables with the default TCP port 2049

Hi all, I have setup a CentOS6.3 x86_64 host to act as a nfs server. According to RHEL6 docs, portmap is not needed when you use NFSv4, but in my host I need to start rpcbind service to make NFSv4 works. My /etc/sysconfig/nfs # # Define which protocol versions mountd # will advertise. The values are "no" or "yes" # with yes being the default MOUNTD_NFS_V2="no"

Hi all, 1) My NFS3 clients don't display or obey existing non-POSIX ACLs on files of NFS3-mounted exports. 2) setfacl on the client throws error and fails : # setfacl -m u:stowler:rw testfile.text setfacl: testfile.text: Operation not supported 3) at time of client mount the server's /var/log/messages shows "kernel: svc: unknown version (3)". Any thoughts greatly

After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message: [root at sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted As nearest as I can tell, I was

Hi, I'm trying to setup a firewalled NFS server. I've configured my server (CentOS 5) using the following parameters /etc/sysconfig/nfs MOUNTD_NFS_V1="no" MOUNTD_NFS_V2="no" RQUOTAD_PORT=875 LOCKD_TCPPORT=32803 LOCKD_UDPPORT=32769 RPCNFSDCOUNT=64 MOUNTD_PORT=892 STATD_PORT=662 STATD_OUTGOING_PORT=2020 SECURE_NFS="yes" modprobe.conf: options lockd

I've got a newly installed Centos 5.0 box, planned to replace an ageing server (solaris box). I've set up the nfs shares, but the other solaris boxes won't mount them, unless I turn of iptables on the Centos box. If I do that, they mount, and all operations tested to date work fine. Iptables is allowing the 2049 tcp and udp ports already. What else needs to be opened up in

I have changed /etc/sysconfig/nfs to specify port numbers for NFS daemons. Somehow statd is still starting up at random port number. Other damons are starting at properly at specified port numbers Any clues on what might be wrong? Any other location/setting that takes precedence over sysconfig/nfs ? It's CentOS 5.5 64bit with nfs-utils 1.0.9-44.el5. -- Thanks, CS

Hi, What is the magic juju that I have to put in /etc/sysconfig/autofs to get autofs to default to using NFSv4, rather than NFSv3, for mounting file systems? I don't want to place these flags into the automount maps themselves because we have a varied network with Sun, CentOS, RedHat and Macintosh systems, and the flags that have to get added to automount maps (which we distribute centrally

Dear CentOS community, I have install centos via CD, DVD and Directly off the net via http and FTP. Now I want to do a NFS install from a local server and a client. Both, client and server are in the same vlan 10.14.10.0/255.255.255.0. The server has a static 10.14.10.15 address and the client gets its own address via DHCP. I download the DVD image from one of the mirrors and placed it under

On Fri, Nov 20, 2020 at 12:18 PM Frank Cox <theatre at sasktel.net> wrote: > > On Fri, 20 Nov 2020 12:07:40 -0500 > Michael B Allen wrote: > > > So TCP src 760 to 41285. What's that? > > Apparently "that" is what you need to allow in order for your desktop to work. > > What it is actually doing, I'm not sure. Google tells me that port 760 has

Hi, I'm using the generic system-config-securitylevel-tui program on a remote server to configure my firewall. So far it's been fairly decent, allowing me to open up ports and whatnot. But I want to start blocking a couple of outgoing ports on my machine. I want to lock it down so the only traffic going in our out of my machine is stuff that I specify. Is there a way to do this

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files

Hi, I'm using the preconfigured firewall that comes with CentOS 5. I configure it with system-config-securitylevel-tui, close all ports except SSH, and then open only the ones I need. Right now, on one of my desktops, I've installed AMSN, which requires opening a series of ports. I've configured the app to use ports 7000 to 7010 (TCP and UDP). When running

In following up on the rsh "problem" I was having earlier, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere

hey list! I am attempting to shore up some centos machines (ranging from centos 5 to centos 5.4) for pci compliance by changing the port that nlockdmgr listens on to function under a privileged port. So what I did was try to hardcode the port by editing /etc/sysconfig/nfs # TCP port rpc.lockd should listen on. LOCKD_TCPPORT=1011 # UDP port rpc.lockd should listen on. LOCKD_UDPPORT=1011 #

Hi, With the release of 5.2 "yum update" seems to be upgrading our computers from CentOS 5.1 to CentOS 5.2. I note from release notes for 5.2 that you are only supposed to get 5.2 if you type in "yum upgrade". On two seperate machines entering "yum update" has resulted in yum geting repo information for packages with versions that only exist in the base