Sponsored Content
Full Discussion: Problem Mounting NFS share
Special Forums IP Networking Problem Mounting NFS share Post 302403680 by fcron on Saturday 13th of March 2010 10:19:19 PM
Old 03-13-2010
Problem Mounting NFS share

I have one machine "The server" ip: 192.168.1.1, it runs ubu 8.04(LTS) and - I have a folder (/shareme) that I want to share with other linux machines on my LAN.
- The server runs NFS server and common and portmap and so do the other machines on my LAN.
- The server has the export file with the appropriate entry
/shareme 192.168.1.0/24 (rw,no_subtree_check,sync)

When I issue the following command (can I do it differently?)
sudo mount 192.168.1.1:/shareme /shared I get the following:
mount.nfs: access denied by server while mounting 192.168.1.1:/shareme

It has worked in the past with clients running ubu 9.04
now my clients run 9.10 so I wonder whether something changed in how you mount the shares.

Could anyone please help me, as I have all my "common" files on the /shareme and I need to access it from other stations on my LAN.
 

10 More Discussions You Might Find Interesting

1. SCO

SCO6 NFS Problem mounting Windows resource

Hi, We are testing SCO6 for an upgrade. We currently have a SCO5.0.4 system that mounts a remote directory on a Windows 2000 server. The windows server has 'services for unix' installed to enable the required directory to be mounted on the SCO system. On SCO we run '/etc/mount -v -f NFS... (2 Replies)
Discussion started by: sidnagra
2 Replies

2. Solaris

solaris 8 NFS mounting problem

While mounting nfs file system I get the following error . # mount -F nfs jewelex:/back2 /oback2 nfs mount: jewelex:/back2: Permission denied Following is the permission for oback2 drwxr-xr-x 2 root other 512 Apr 9 18:39 oback2 Directory permission on jewelex server is ... (4 Replies)
Discussion started by: Hitesh Shah
4 Replies

3. Solaris

problem NFS mounting onto Solaris 10

On my Solaris 10 server, I want to share out the directory /export/home/data, so in the /etc/dfs/dfstab file, I have this line: share -F nfs -o rw /export/home/data In the /etc/hosts.equiv file, I have this: + When I do a "ps -ef" command, I see that the "nfsd' daemon is started. ... (2 Replies)
Discussion started by: serendipity1276
2 Replies

4. UNIX for Dummies Questions & Answers

Mounting an NFS share: Kickstart Postinstall

For my kickstart install I use an NFS share on another machine in order to install the packages. For the most part, all configuration required after each time I reimage is set up in the kickstart file, but this one portion is giving me issues. I'm trying to mount an NFS share in the kickstart post... (0 Replies)
Discussion started by: Colton
0 Replies

5. Solaris

NFS Share - chown problem

Hi all, I had share the server Gemini /u10 to the server Centaurus. /etc/dfs/dfstab share -F nfs -o root=centaurus /u10 My problem is: in the server Gemini the the owner for /U10 is oracle:dba but when in the server Centaurus, I am not able to change the owner become oracle:dba, it show... (8 Replies)
Discussion started by: SmartAntz
8 Replies

6. Web Development

NFS Share & Mount problem

Hi, I want to mount an NFS Shared folder on Windows XP to vxWorks. There doesnt seem to be a problem with the sharing. Now, when i try to mount the directory onto vxWorks (it runs on a Tumbleweed card), using a mount script (.sh), the following is the print i see on Tera Term: hostAdd... (0 Replies)
Discussion started by: chinmayzen
0 Replies

7. UNIX for Advanced & Expert Users

NFS : Invalid argument (Remote share mounting issue)

Hi Guru's, I am unable to mount NFS share on unix system (DG/UX) which is nfs client. Error: mount: /nfsshare: Invalid argument mount: giving up on: /mountpoint i tried following command mount -t nfs remotehost:/nfsshare /mountpoint Error: (5 Replies)
Discussion started by: Justin John
5 Replies

8. Red Hat

Problem about NFS to change the share folder at several servers.

All, I re-wrote our scripts to speed-up the compiling time, original time is about 1hrs. now dispatch the sub task to different servers through SSH. Now my question is that: If dispatch these tasks into the current server, there is no errors during compiling process. If dispatch these tasks... (0 Replies)
Discussion started by: fduan001
0 Replies

9. Solaris

Mounting 2012R2 NFS Share on Solaris 10

Hi all, new here. I'm attempting to mount an NFS share I've created on a 2012r2 esx VM on my solaris 10 vm, I'm using the following command: mount 2012box:/sharename /mnt and I get the following result: nfs mount: mount: /mnt: Operation not supported Both vms can ping one... (3 Replies)
Discussion started by: Meshuggener
3 Replies

10. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies
PPTPD.CONF(5)							File Formats Manual						     PPTPD.CONF(5)

NAME
pptpd.conf - PPTP VPN daemon configuration DESCRIPTION
pptpd(8) reads options from this file, usually /etc/pptpd.conf. Most options can be overridden by the command line. The local and remote IP addresses for clients must come from the configuration file or from pppd(8) configuration files. OPTIONS
option option-file the name of an option file to be passed to pppd(8) in place of the default /etc/ppp/options so that PPTP specific options can be given. Equivalent to the command line --option option. stimeout seconds number of seconds to wait for a PPTP packet before forking the pptpctrl(8) program to handle the client. The default is 10 seconds. This is a denial of service protection feature. Equivalent to the command line --stimeout option. debug turns on debugging mode, sending debugging information to syslog(3). Has no effect on pppd(8) debugging. Equivalent to the command line --debug option. bcrelay internal-interface turns on broadcast relay mode, sending all broadcasts received on the server's internal interface to the clients. Equivalent to the command line --bcrelay option. connections n limits the number of client connections that may be accepted. If pptpd is allocating IP addresses (e.g. delegate is not used) then the number of connections is also limited by the remoteip option. The default is 100. delegate delegates the allocation of client IP addresses to pppd(8). Without this option, which is the default, pptpd manages the list of IP addresses for clients and passes the next free address to pppd. With this option, pptpd does not pass an address, and so pppd may use radius or chap-secrets to allocate an address. localip ip-specification one or many IP addresses to be used at the local end of the tunnelled PPP links between the server and the client. If one address only is given, this address is used for all clients. Otherwise, one address per client must be given, and if there are no free addresses then any new clients will be refused. localip will be ignored if the delegate option is used. remoteip ip-specification a list of IP addresses to assign to remote PPTP clients. Each connected client must have a different address, so there must be at least as many addresses as you have simultaneous clients, and preferably some spare, since you cannot change this list without restarting pptpd. A warning will be sent to syslog(3) when the IP address pool is exhausted. remoteip will be ignored if the dele- gate option is used. noipparam by default, the original client IP address is given to ip-up scripts using the pppd(8) option ipparam. The noipparam option pre- vents this. Equivalent to the command line --noipparam option. listen ip-address the local interface IP address to listen on for incoming PPTP connections (TCP port 1723). Equivalent to the command line --listen option. pidfile pid-file specifies an alternate location to store the process ID file (default /var/run/pptpd.pid). Equivalent to the command line --pidfile option. speed speed specifies a speed (in bits per second) to pass to the PPP daemon as the interface speed for the tty/pty pair. This is ignored by some PPP daemons, such as Linux's pppd(8). The default is 115200 bytes per second, which some implementations interpret as meaning "no limit". Equivalent to the command line --speed option. NOTES
An ip-specification above (for the localip and remoteip tags) may be a list of IP addresses (for example 192.168.0.2,192.168.0.3), a range (for example 192.168.0.1-254 or 192.168.0-255.2) or some combination (for example 192.168.0.2,192.168.0.5-8). For some valid pairs might be (depending on use of the VPN): localip 192.168.0.1 remoteip 192.168.0.2-254 or localip 192.168.1.2-254 remoteip 192.168.0.2-254 ROUTING CHECKLIST - PROXYARP Allocate a section of your LAN addresses for use by clients. In /etc/ppp/options.pptpd. set the proxyarp option. In pptpd.conf do not set localip option, but set remoteip to the allocated address range. Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). The server will advertise the clients to the LAN using ARP, providing it's own ethernet address. bcrelay(8) should not be required. ROUTING CHECKLIST - FORWARDING Allocate a subnet for the clients that is routable from your LAN, but is not part of your LAN. In pptpd.conf set localip to a single address or range in the allocated subnet, set remoteip to a range in the allocated subnet. Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). The LAN must have a route to the clients using the server as gateway. The server will forward the packets unchanged between the clients and the LAN. bcrelay(8) will be required to support broadcast protocols such as NETBIOS. ROUTING CHECKLIST - MASQUERADE Allocate a subnet for the clients that is not routable from your LAN, and not otherwise routable from the server (e.g. 10.0.0.0/24). Set localip to a single address in the subnet (e.g. 10.0.0.1), set remoteip to a range for the rest of the subnet, (e.g. 10.0.0.2-200). Enable kernel forwarding of packets, (e.g. using /proc/sys/net/ipv4/ip_forward ). Enable masquerading on eth0 (e.g. iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE ). The server will translate the packets between the clients and the LAN. The clients will appear to the LAN as having the address corre- sponding to the server. The LAN need not have an explicit route to the clients. bcrelay(8) will be required to support broadcast proto- cols such as NETBIOS. FIREWALL RULES
pptpd(8) accepts control connections on TCP port 1723, and then uses GRE (protocol 47) to exchange data packets. Add these rules to your iptables(8) configuration, or use them as the basis for your own rules: iptables --append INPUT --protocol 47 --jump ACCEPT iptables --append INPUT --protocol tcp --match tcp --destination-port 1723 --jump ACCEPT SEE ALSO
pppd(8), pptpd(8), pptpd.conf(5). 29 December 2005 PPTPD.CONF(5)
All times are GMT -4. The time now is 04:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy