Our XP1000's running Tru64 v4.0F have taken to harassing our NIS server with
requests. When I snoop the network traffic on our NIS server, I can see the
alphas flooding the server with the following request (to the point where no
other information can get through). ( .... = random number)
b -> g NIS C DOMAIN xyz
g -> b RPC R (#....) XID=........ Program number mismatch
b -> g PORTMAP C GETPORT prog=100004 (NIS) vers=1 proto=UDP
g -> b PORTMAP R GETPORT port=762
b -> g NIS C DOMAIN xyz
g -> b RPC R (#....) XID=........ Program number mismatch
b -> g PORTMAP C GETPORT prog=100004 (NIS) vers=1 proto=UDP
g -> b PORTMAP R GETPORT port=762
b -> g NIS C DOMAIN xyz
g -> b RPC R (#....) XID=........ Program number mismatch
b -> g PORTMAP C GETPORT prog=100004 (NIS) vers=1 proto=UDP
g -> b PORTMAP R GETPORT port=762
This problem happens just after the system boots up and someone tries to
logon. I have figured out that the problem is the alpha sometime sends NIS
version 1 info to a version 2 server. If I finally get into the workstation
and kill the ypbind process and start it again, it works fine.
I can recreate this type of error by doing a '# ypwhich -V1', which leads me
to believe that it is a versioning problem. (The client will flood the
server when this command is run.)
The current NIS server runs IRIX, but I had a very similar result when I
tried having Solaris as the NIS server.
Has anyone run into something like this before or know how I might get
around this problem? I don't see anything in the startup scripts, that
would make it version 1, off hand.
Thanks for any assistance in advance.
-Peter Clark
prclark_at_its.cse.dnd.ca
Received on Mon Jun 26 2000 - 15:07:21 NZST