Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!hao!ames!hc!hi!cyrus From: cyrus@hi.UUCP (Tait Cyrus) Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip Subject: Re: SUN 3.4 problems Message-ID: <14304@hi.UUCP> Date: Sat, 29-Aug-87 13:39:31 EDT Article-I.D.: hi.14304 Posted: Sat Aug 29 13:39:31 1987 Date-Received: Sun, 30-Aug-87 09:14:20 EDT References: <1615@briar.Philips.Com> Reply-To: cyrus@hc.dspo.gov (Tait Cyrus) Organization: U. of New Mexico, Albuquerque Lines: 39 Xref: mnetor comp.dcom.lans:788 comp.protocols.tcp-ip:1013 In article <1615@briar.Philips.Com> jmr@philabs.Philips.Com (Joanne Mannarino) writes: > > >In trying to upgrade our SUN 3/180 fileserver (named condor) to SUN UNIX >version 3.4 along with 11 diskless clients, I ran into some problems. The > ... >Ethernet). The problem began when the booting process got to the point for: > > starting rpc and net services: portmap router biod > >The boot process then halts with the following error messages: > > server not responding > RPC: program not registered > mount retrying Something that ?might? be causing some problems is that when a SUN client boots, it determines its netmask from an ICMP (rfc 950) 'netmask request'. At one point, here at the University of New Mexico, one of our SUN's was configured with the WRONG netmask. When we tried to boot our diskless clients, they got the wrong netmask and were unable to talk with the server. Rebooting the server did not fix the problem because it got the netmask from the partially booted clients. We ended up halting ALL of our SUN's, booting the servers with the correct netmask, and THEN booting our clients. I don't know if this is your problem or not, but you might look into it. -- @__________@ W. Tait Cyrus (505) 277-0806 /| /| University of New Mexico / | / | Dept of EECE - Hypercube Project @__|_______@ | Albuquerque, New Mexico 87131 | | | | | | hc | | e-mail: | @.......|..@ cyrus@hc.dspo.gov or | / | / seismo!unmvax!hi!cyrus @/_________@/