Sponsored Content
Operating Systems AIX AIX NFS Server and NFS Client Post 302960129 by jim mcnamara on Tuesday 10th of November 2015 09:05:31 PM
Old 11-10-2015
On AIX can you not enable search in /etc/resolv.conf (or equivalent), declaring search files first and then add any short names plus the IP's you need to get something to connect?

This approach works fine on Solaris, for example.
 

9 More Discussions You Might Find Interesting

1. Linux

NFS Server FC7 Solaris client problems!

Hi, my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client. I always got the messages no permission. Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Discussion started by: joerg
3 Replies

2. UNIX for Advanced & Expert Users

Determining IP address of NFS server on client

Hi. We use an Isilon cluster system to provide our NAS. The Isilon uses a round-robin DNS setup to spread mount requests across the many nodes of the cluster. When a node needs work, the filesystems that are mounted to it need to be moved to other nodes prior to shutting the node down. I... (2 Replies)
Discussion started by: rascalrick
2 Replies

3. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

4. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

5. Red Hat

Memory problems in NFS client server

Hi all, i have some doubts in a situation that i fail to get an answer in Google. I have a solaris 10 nfs server and 5 centos 6.0 nfs clients. The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies

6. Solaris

Can't access NFS Share on Solaris Server from a Linux Client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. & then ran the following On the client machine, while running the mount command, I am... (0 Replies)
Discussion started by: SunilB2011
0 Replies

7. AIX

AIX NFS Client Logging

My AIX NFS client failed to mount a Windows server NFS service today. Is NFS client logging enabled by default on AIX? If not, is there a way to enable NFS client logging on AIX6.1. Thanks. (0 Replies)
Discussion started by: famasutika
0 Replies

8. 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

9. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies
PPPCONFIG(8)						      System Manager's Manual						      PPPCONFIG(8)

NAME
pppconfig - configure pppd to connect to the Internet SYNOPSIS
pppconfig [--version] | [--help] | [[--dialog] | [--whiptail] | [--gdialog] [--noname] | [providername]] DESCRIPTION
pppconfig is a dialog based interactive, menu driven utility to help automate setting up a dial out ppp connection. It provides extensive explanations at each step. pppconfig supports PAP, CHAP, and chat methods of authentication. It uses the standard ppp configuration files and sets ppp up so that the standard pon and poff commands can be used to control ppp. Some features supported by pppconfig are: - Multiple ISP's with separate nameservers. - Modem detection. - Dynamic DNS. - Dial on demand. - Allow non-root users to run ppp. - Uses the gdialog GUI dialog replacement if possible. Before running pppconfig you should know what sort of authentication your isp requires, the username and password that they want you to use, and the phone number. If they require you to use chat authentication, you will also need to know the login and password prompts and any other prompts and responses required for login. If you can't get this information from your isp you could try dialing in with minicom and working through the procedure until you get the garbage that indicates that ppp has started on the other end. pppconfig allows you to configure connections to multiple providers. For example, you might call your isp 'provider', your employer 'the- office' and your university 'theschool'. Then you can connect to your isp with 'pon', your office with 'pon theoffice', and your univer- sity with 'pon theschool'. It can determine which serial port your modem is on, but the serial port must already be configured. This is normally done when installing Linux. It can help you set your nameservers, or, if your ISP uses 'dynamic DNS', it can set up ppp to use that. It can configure ppp for demand dialing, so that your ppp connection will come up automatically. It will not, however, start pppd for you. You must still start pppd yourself ('pon' will do it). Pppd will then wait in the background for you to attempt to access the Net and bring up the link. If you select "Static" in the "Configure Nameservers" screen pppconfig will create a file in the /etc/ppp/resolv directory named after the provider you are configuring and containing "nameserver" lines for each of the IP numbers you gave. This file will be substituted for /etc/resolv.conf when the connection comes up. The provider name is passed in the ipparam variable so that 0dns-up knows which file to use. The original resolv.conf will be put back when the connection goes down. You can edit this file if you wish and add such things as "search" or "domain" directives or additional nameservers. Be sure and read the resolv.conf man page first, though. The "search" and "domain" directives probably do not do what you think they do. If you select "dynamic" in the "Configure Nameservers" screen pppconfig will configure pppd for 'dynamic DNS' and create a file in the /etc/ppp/resolv directory named after the provider you are configuring but containing nothing. When the connection comes up the name- servers supplied by your ISP will be added and the file substituted for /etc/resolv.conf. You can edit this file if you wish and add such things as "search" or "domain" directives or additional nameservers. If you select "None" in the "Configure Nameservers" screen pppconfig will create no file in /etc/ppp/resolv and will leave /etc/resolv.conf alone. ipparam is not set to the provider name and so is free for the administrator to use. FILES
/etc/ppp/peers/provider is the standard pppd options file for the default service provider. /etc/ppp/peers/<name> is the pppd options file for the provider that you have named <name>. /etc/ppp/peers/provider.bak is a backup copy of /etc/ppp/peers/provider. /etc/chatscripts/provider is the standard chat script for the default service provider. /etc/chatscripts/<name> is the chat script for the provider that you have named <name>. /etc/chatscripts/provider.bak is a backup copy of /etc/chatscripts/provider. /etc/ppp/resolv is a directory where resolv.conf files for each provider are stored. /etc/ppp/ip-up.d/0dns-up is a script that arranges for the correct resolv.conf file to be copied into place when a connection comes up. /etc/ppp/ip-down.d/0dns-down is a script that arranges for the original resolv.conf file to be copied into place when a connection goes down. /etc/init.d/dns-clean is a script that runs 0dns-down at bootup to clean up any mess left by a crash. /var/run/pppconfig is a directory where temporary files created by 0dns-up are stored. /var/run/pppconfig/resolv.conf.bak.<provider> is a backup copy of the original resolv.conf file. 0dns-down restores /etc/resolv.conf from it. /var/run/pppconfig/0dns.<provider> is a backup copy of the resolv.conf file for <provider>. 0dns-down uses it to determine if /etc/resolv.conf has been overwritten by another process. /etc/ppp/pap-secrets and /etc/ppp/chap-secrets are described in the pppd documentation. pppconfig may add lines to these files and will change lines that it previously added. NOTES
pppconfig requires pppd 2.3.7 or higher. TO DO
Add full support for MSCHAP. BUGS
Don't tell pppconfig to find your modem while pppd is running. SEE ALSO
chat(8), gpppon(1), plog(1), poff(1), pon(1), pppd(8), and whiptail(1). AUTHOR
pppconfig was written by John Hasler <jhasler@debian.org>. COPYRIGHT
This man page may be treated as if it were in the public domain. I waive all rights. Debian GNU/Linux Version 2.3.16 PPPCONFIG(8)
All times are GMT -4. The time now is 01:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy