NIS issue for solaris 10
 

I have nis server ultra10 which manages another test10/solaris10 and test01/FC5.
I can cd into /net/test10 and see all its export resources.
But I can not cd into /net/test01 but via its IP of test01.

-bash-3.00# ypwhich
test10
-bash-3.00# ypcat hosts | grep test01
192.168.11.11 test01

-bash-3.00# cd /net/test01
-bash: cd: /net/test01: No such file or directory

-bash-3.00# cd /net/192.168.11.11
-bash-3.00# pwd
/net/192.168.11.11


Any idea?

Is nis set for hostname resolution in /etc/nsswitch.conf ?

-bash-3.00# ypcat hosts
192.168.11.11 test1
127.0.0.1 localhost
192.168.11.7 ultra10 loghost
192.168.11.10 test10

-bash-3.00# cat /etc/nsswitch.conf | grep hosts
# "hosts:" and "services:" in this file are used only if the
hosts: dns nis [NOTFOUND=return] files
# before searching the hosts databases.

For /net, I think the entry to set in nsswitch.conf is automount, not hosts.

-bash-3.00# cat /etc/nsswitch.conf | grep automount
automount: nis files

My OS is solaris 10. I tried to restart nis server and autofs service via svcadm. But problem persistent.

Perhaps does the host name need to be fully qualified (nis domain appended) ?

In test01/FC5

# ypwhich
test10

# domainname
home.org

In test10/Solari10
# domainname
home.org

"/net/test01.home.org/" neither works ?

-bash-3.00# more /etc/resolv.conf
search domain home.org
nameserver 192.168.11.1

I also tried cd /net/test01.home.org, problem persistent.

In my test10/Soalris OS.
-bash-3.00# ping test01
test01 is alive

Perhaps a typo somewhere (you once wrote test1 vs test01), or some protocol issue on the FC5 box.

What shows "showmount -e test01" ?

# showmount -e test01
Export list for test01:
/share *
/project *

Can you mount the filesystem manually ?

Yeah, I think the RPC bind failure is the hell, But how should i fix the problem?


-bash-3.00# pwd
/tmp
-bash-3.00# mkdir mnt
-bash-3.00# mount test01:/share /tmp/mnt/
nfs mount: test01: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: retrying: /tmp/mnt
nfs mount: test01: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: test01: : RPC: Rpcbind failure - RPC: Unable to receive
^C

-bash-3.00# mount test01.homelinux.org:/share /tmp/mnt/
nfs mount: test01.homelinux.org: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: retrying: /tmp/mnt
nfs mount: test01.homelinux.org: : RPC: Rpcbind failure - RPC: Unable to receive
nfs mount: test01.homelinux.org: : RPC: Rpcbind failure - RPC: Unable to receive

-bash-3.00# mount 192.168.11.11:/share /tmp/mnt/
==> use Ip and it works fine.


And rpcinfo for nfs is as follows.
-bash-3.00# rpcinfo -p | grep nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 2 udp 2049 nfs_acl
100227 3 udp 2049 nfs_acl
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100227 2 tcp 2049 nfs_acl
100227 3 tcp 2049 nfs_acl

Can you post your /etc/dfs/dtstab and your auto_master and auto_direct maps for test01 ?

Is there another resolution for test01 in the DNS ?

What tells "nslookup test01" ?