eho@reason.princeton.edu (Eric Ho) (03/10/89)
Does anyone has problems in using a 4.0 ypbind with a 3.3 ypserv ? I've a Sun-4 under 4.0 configured as a standalone and using YP (as a YP client). My machine is physically hooked to a net of Sun-3's -- the server (homogeneous) being a 3/180 under 3.3 (hence a 3.3 ypserv). On the surface, my 4.0 ypbind seems to work ok -- ypwhich was fine and so as ping, rusers, rcp, ..etc.. and I can telnet/ftp to other machines outside the immediate local net -- i.e. able to go to other depts' machines, ..etc.. However, when I do NFS mount, it just hang there (i.e. I type in mount by hand and it just hang there without even giving any error messages back -- i.e. no prompt back). The 3/180 server seems to be picking up the packets (I can see it in etherfind) but somehow it is not responding. If I kill my 4.0 ypbind on my Sun-4 and add the 3/180 server's internet address into the /etc/hosts file on my Sun-4 then I can do NFS mounts from my Sun-4 without a hitch (basically, I want to do NFS mount from my Sun-4 because all my home directory stuff is on the 3/180 server). I just got my Sun-4 recently (about 10 months ago) -- it was running SYS4-3.2 (also as a standalone & YP client) and was working fine before -- I only moved to 4.0 this week. The 3.3 ypserv on the 3/180 is working fine with other Sun-3 YP clients (a mix of 50's, 75's and a 280). The 3/180 server & other Sun-3's were here for more than 3 years so I don't think that it is a problem with the Sun-3's (there is only one YP server on the net and it is on the 3/180 -- i.e. the rest of the net are YP clients). Does anyone encountered similiar problems before ? Any pointers will be much appreciated. regards. -eric-
pvo1478@oce.orst.edu (Paul V. O'Neill) (03/30/89)
> Does anyone has problems in using a 4.0 ypbind with a 3.3 ypserv ?
We have a 4.0 4/110 and a 4.0 386i getting ypservice from a 3.5 3/280.
This may not be your problem, but it is some light on the situation. (The
following applies to 3.4 ypserv also.)
ypbind kills the portmapper on the 4.0 system. Restarting the portmapper
and doing a ypset in rc.local immmediately after the ypbind works for us.
NFS wouldn't work w/o the portmapper, but I'd expect an RPC timeout
message if this were your problem. (Did you wait 75 seconds?)
For some reason a second ypbind call is needed in the 386i's rc.local
before YP works.
Paul O'Neill pvo@oce.orst.edu
Coastal Imaging Lab
OSU--Oceanography
Corvallis, OR 97331 503-754-3251zjat02@uunet.uu.net (Jon A. Tankersley) (03/31/89)
YES!!!!!!!!!!!!!!!!! (sorry, but I thought we were the only ones.....) We are having identical problems on 3 subnets. There are some patches from Sun to ypbind, portmap, etc.... Call you support people or the local office. The patches have fixed one subnet, don't seem to work on another, and are not installed at all on the third. I've been losing hair over this one. One workaround if you have source is to try to recompile mount without -O. Sun doesn't know yet what is happening to cause it, my core dump of mount is currently being analyzed. Are you running with subnetting or with named perchance? -tank-
zjat02@uunet.uu.net (Jon A. Tankersley) (04/26/89)
There is potential for problems whenever you use a lower release OS for your ypserver. Reverse it and things should be better off. I had a Sun4 under 4.0 for a while that was master to 3 other slave servers under 3.5. No real problems. Now that they are at 4.0...... Other problems. One thing to look out for, named/ypbind/ypserv does have some problems and needs patches that are available from Sun. -tank- #include <std/disclaimer.h> /* nobody knows the trouble I .... */