Mike R.
asked on
NIS client and "no such map in server's domain"
Hey Folks,
I have installed a new server and set it up to be an NIS client. Everything appeared to go normally, however when I try to use the client, it fails. If I do a "ypcat -k hosts" (for example) it comes back with the error "no such map in server's domain". Basic steps are as follows ...
1. Server1 received from SUN with Sol9 pre-installed.
2. Connected server1 to subnet A (I.E. 100.100.100.26). Machine "domaincontroller" lives on subnet B (200.200.200.37).
3. Configured server1's routing tables to point to the 200.200.200.0 subnet.
3.a. server1 CAN ping, telnet and rlogin into machine "domaincontroller" ( 200.200.200.37).
3.b. Machine "domaincontroller" CAN ping, telnet and rlogin into server1.
4. on server1 domainname "TheDomain"
5. on server1 domainname > /etc/defaultdomain
5.a. "echo /etc/defaultdomain" returns correct.
6. On server1, command "ypinit -c".
6.a. enter "domaincontroller" as only server.
6.b. everything seems to go as normal.
7. cp -p nsswitch.conf nsswitch.conf.orig
8. cp -p nsswitch.nis nsswitch.conf
9. reboot
10. After reboot, NIS starts.
10.a. command "ypwhich" returns correctly with "domaincontroller"
-HOWEVER, all commands such as "ypcat -k hosts", "ypcat -d TheDomain -t hosts.byname" return error, "no such map in server's domain"
-Command "su - domainuser" fails with "su: Unknown id: domainuser"
-the "/var/yp" dir appears correct (when compared to working machines) including a correct "/var/yp/TheDomain" dir, and the "aliases" and "nicknames" files.
Any ideas?
Thanks!
M
I have installed a new server and set it up to be an NIS client. Everything appeared to go normally, however when I try to use the client, it fails. If I do a "ypcat -k hosts" (for example) it comes back with the error "no such map in server's domain". Basic steps are as follows ...
1. Server1 received from SUN with Sol9 pre-installed.
2. Connected server1 to subnet A (I.E. 100.100.100.26). Machine "domaincontroller" lives on subnet B (200.200.200.37).
3. Configured server1's routing tables to point to the 200.200.200.0 subnet.
3.a. server1 CAN ping, telnet and rlogin into machine "domaincontroller" ( 200.200.200.37).
3.b. Machine "domaincontroller" CAN ping, telnet and rlogin into server1.
4. on server1 domainname "TheDomain"
5. on server1 domainname > /etc/defaultdomain
5.a. "echo /etc/defaultdomain" returns correct.
6. On server1, command "ypinit -c".
6.a. enter "domaincontroller" as only server.
6.b. everything seems to go as normal.
7. cp -p nsswitch.conf nsswitch.conf.orig
8. cp -p nsswitch.nis nsswitch.conf
9. reboot
10. After reboot, NIS starts.
10.a. command "ypwhich" returns correctly with "domaincontroller"
-HOWEVER, all commands such as "ypcat -k hosts", "ypcat -d TheDomain -t hosts.byname" return error, "no such map in server's domain"
-Command "su - domainuser" fails with "su: Unknown id: domainuser"
-the "/var/yp" dir appears correct (when compared to working machines) including a correct "/var/yp/TheDomain" dir, and the "aliases" and "nicknames" files.
Any ideas?
Thanks!
M
ASKER
"TheDomain" is the domain name. domaincontroller is the name of the server running as the domaincontroller. Does that makes sense?
names are just names ...
but for NIS they must agree on the NIS-domain, means both: server and client, must report the same name for
ypwhich
(which is what you have written to /etc/defaultdomain, usually)
but for NIS they must agree on the NIS-domain, means both: server and client, must report the same name for
ypwhich
(which is what you have written to /etc/defaultdomain, usually)
ASKER
OK...I understand what you are asking. They all appear to report correctly. Here is the output...
on machine domainserver (200.200.200.37)
#domainname
TheDomain
#ypwhich
domainserver
#ypcat -k hosts
(lots of hosts)
#su - domainuser
(succesfull su to user named domainuser)
on server1 (100.100.100.26)
#domainname
TheDomain
#ypwhich
domainserver
#ypcat -k hosts
no such map in server's domain
#su - domainuser
su: Unknown id: domainuser
on server2 (a different working domain client IP 200.200.200.190)
#domainname
TheDomain
#ypwhich
domainserver
#ypcat -k hosts
(lots of hosts)
#su - domainuser
(succesfull su to user named domainuser)
Does that clarify better?
Thanks again!
M
on machine domainserver (200.200.200.37)
#domainname
TheDomain
#ypwhich
domainserver
#ypcat -k hosts
(lots of hosts)
#su - domainuser
(succesfull su to user named domainuser)
on server1 (100.100.100.26)
#domainname
TheDomain
#ypwhich
domainserver
#ypcat -k hosts
no such map in server's domain
#su - domainuser
su: Unknown id: domainuser
on server2 (a different working domain client IP 200.200.200.190)
#domainname
TheDomain
#ypwhich
domainserver
#ypcat -k hosts
(lots of hosts)
#su - domainuser
(succesfull su to user named domainuser)
Does that clarify better?
Thanks again!
M
ASKER
P.S. I am wondering if the issue lises inthe fact that the domainserver and the domain client are on different subnets...even though the are successfully routed to each other...?
Hi,
Check the /var/yp/nicknames file. If you don't have it or there is not "hosts hosts.byname" or "passwd passwd.byname",
then copy from server2.
Regards,
Wesly
Check the /var/yp/nicknames file. If you don't have it or there is not "hosts hosts.byname" or "passwd passwd.byname",
then copy from server2.
Regards,
Wesly
ASKER
Thanks for the input Wesley. Actually, I do have both the aliases file and the nicknames file setup, and they look correct.
What else might I check?
Thanks!
M
What else might I check?
Thanks!
M
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I believe the netmask is correct (I have verified this against other machines on the net), however I believe it is going through a VLAN. There is no firewall, and should be no packet filter happenning, however.
Hi,
Does it have NIS server in /etc/hosts of server1?
Besides, please check /var/yp/binding/<TheDoman>
Wesly
Does it have NIS server in /etc/hosts of server1?
Besides, please check /var/yp/binding/<TheDoman>
Wesly
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey Guys,
Well...I knida cheated for expediency. The servers were on different subnets and, although I was assured there should be no packet filtering and rpc traffic should be allowed, I created a slave NIS server on the same subnet as the non-working client (using a multihomed machine between bth subnets) and the client started working.
I don't know why the client was not working across the subnet, and will probably have to revisit it again in the future...but for now, working is working.
I will divide up the points. Wesly gets the king's portion, since he is the one who first go me looking at the vlan...but I appreciate everyone's help!
M
Well...I knida cheated for expediency. The servers were on different subnets and, although I was assured there should be no packet filtering and rpc traffic should be allowed, I created a slave NIS server on the same subnet as the non-working client (using a multihomed machine between bth subnets) and the client started working.
I don't know why the client was not working across the subnet, and will probably have to revisit it again in the future...but for now, working is working.
I will divide up the points. Wesly gets the king's portion, since he is the one who first go me looking at the vlan...but I appreciate everyone's help!
M
> created a slave NIS server on the same subnet as the non-working client
In the server 1 "/usr/lib/netsvc/yp/ypstar
broadcast to find the NIS server. In this case, different subnet will cause problem becasue the broadcast packets can not
pass the subnet boundary (or VLAN).
So I ask you 2 questions on the last post:
< Does it have NIS server in /etc/hosts of server1?
< Besides, please check /var/yp/binding/<TheDoman>
This should allow server1 to locate the NIS server without using broadcast.
Anyway, setup NIS slave on each subnet is good way since the "-broadcast" is default option for ypbind in ypstart script.
Regards,
Wesly
In the server 1 "/usr/lib/netsvc/yp/ypstar
broadcast to find the NIS server. In this case, different subnet will cause problem becasue the broadcast packets can not
pass the subnet boundary (or VLAN).
So I ask you 2 questions on the last post:
< Does it have NIS server in /etc/hosts of server1?
< Besides, please check /var/yp/binding/<TheDoman>
This should allow server1 to locate the NIS server without using broadcast.
Anyway, setup NIS slave on each subnet is good way since the "-broadcast" is default option for ypbind in ypstart script.
Regards,
Wesly
ASKER
< Does it have NIS server in /etc/hosts of server1?
It does.
< Besides, please check /var/yp/binding/<TheDoman>
The NIS server is in the ypservers.
Basically, everytyhing appears to be setup correctly to allow the client to see the server across the subnets...but it isn't. i suspect, since I don't have direct control over the subnets, that there is some packet filtering turned on, even though I have been assured it is not.
Thanks for the continued help though :-)
M
It does.
< Besides, please check /var/yp/binding/<TheDoman>
The NIS server is in the ypservers.
Basically, everytyhing appears to be setup correctly to allow the client to see the server across the subnets...but it isn't. i suspect, since I don't have direct control over the subnets, that there is some packet filtering turned on, even though I have been assured it is not.
Thanks for the continued help though :-)
M
TheDomain or domaincontroller