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


LVL 3
Mike R.Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ahoffmannCommented:
what is the NIS domain now?
TheDomain or domaincontroller
0
Mike R.Author Commented:
"TheDomain" is the domain name.  domaincontroller is the name of the server running as the domaincontroller.  Does that makes sense?
0
ahoffmannCommented:
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)
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Mike R.Author Commented:
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
0
Mike R.Author Commented:
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...?
0
wesly_chenCommented:
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
0
Mike R.Author Commented:
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
0
wesly_chenCommented:
>  domainserver and the domain client are on different subnets
It should be ok since they can ping each other.
The only thing will affect is the broadcast. But it is between the NIS master server and slave server.

Two more things to check:
1. netmask on server1
2. any firewall or packet filter or VLAN setting between server1 and nis server?

Wesly
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mike R.Author Commented:
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.
0
wesly_chenCommented:
Hi,

   Does it have NIS server in /etc/hosts of server1?
   Besides, please check /var/yp/binding/<TheDoman>/ypservers to see if your NIS server in this file.

Wesly
0
ahoffmannCommented:
>  domainserver and the domain client are on different subnets
is there a firewall inbetween?
if so, did you allow rpc traffic?
0
Mike R.Author Commented:
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
0
wesly_chenCommented:
> created a slave NIS server on the same subnet as the non-working client
In the server 1 "/usr/lib/netsvc/yp/ypstart" script, if you have "-broadcast" option for the ypbind, then server1 will use
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>/ypservers to see if your NIS server in this file.
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
0
Mike R.Author Commented:
< Does it have NIS server in /etc/hosts of server1?
It does.

< Besides, please check /var/yp/binding/<TheDoman>/ypservers to see if your NIS server in this file.
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
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.