chuck@wooglin.scc.com (Charles Williams) (04/25/89)
I am in the process of upgrading my Sun's to SunOs4.0. Diskless clients do not want to boot over our network. The network has both sun and non-sun machines. below is the text that appears on the client screen as it tries to boot: b le(0,0,0) Using Internet Number 192.5.220.3 = C005D03 Booting from tftp server 192.5.220.100 Downloaded 126056 bytes via tftp Using Internet Number 192.5.220.3 le: missed packet le: missed packet le: missed packet le: missed packet No bootparam server responding; still trying... The missed packet messages and bootparam server message repeat forever. I can watch ethernet traffic to and from the client and I see the rpc call that it supposed to ask for the bootparam server, bootparamd is ready and waiting on the server, but does not respond to the rpc call from the client. In fact there are several bootparam servers on the net and nobody responds to the rpc call. However, I can get responses when I manually send the rpc broadcast message. Does anybody have a clue as to what I have to do to get this client to boot?? Please send response directly to chuck@wooglin.scc.com Thanks in advance. Chuck Williams Contel Federal Systems
wolf@ssyx.ucsc.edu (Mike Wolf) (05/07/89)
>I am in the process of upgrading my Sun's to SunOs4.0. Diskless clients do >not want to boot over our network. The network has both sun and non-sun >machines. below is the text that appears on the client screen as it tries >to boot: > >b le(0,0,0) >Using Internet Number 192.5.220.3 = C005D03 >Booting from tftp server 192.5.220.100 >Downloaded 126056 bytes via tftp > >Using Internet Number 192.5.220.3 >le: missed packet >le: missed packet >No bootparam server responding; still trying... We're having a similar problem here with a Sun 3/50 not booting. I think I've nailed down the cause of the problem. We're a class B network, but we're using a class C subnet mask. When the client boots, the boot code is supposed to send out an ICMP Information Request message, which should get the appropriate netmask. I don't see any such ICMP message being sent when I use etherfind to watch the boot process. So, the client assumes a class B netmask, broadcasts to that instead of the proper class C netmask, and all the machines on the network ignore the wrong broadcast address, so the portmapper never sees the request for the bootparamd. I've called sun technical support about this, but I've had no response as yet. Please let me know if you think your problem is different from what I've discribed, or if you find a fix. - Michael Wolf wolf@ssyx.ucsc.edu ...!ucbvax!ucscc!ssyx!wolf
keyles@rubbs.fidonet.org (Michael Keyles) (05/17/89)
> >Using Internet Number 192.5.220.3 = C005D03 > >Booting from tftp server 192.5.220.100 > >Downloaded 126056 bytes via tftp > > > >Using Internet Number 192.5.220.3 > >le: missed packet > >le: missed packet > >No bootparam server responding; still trying... I've had the same thing happen to me. The cause was an entry in /etc/hosts with multiple aliases for the client, with the primary name of the client not appearing first. Example for a client named hamlet: 129.14.43.10 gretel hamlet zeus I received the same exact messages as you did. When I switched the entry to: 129.14.43.10 hamlet gretel zeus it booted fine. Hope this helps. Mike Michael Keyles - via FidoNet node 1:107/520 UUCP: ...!rutgers!rubbs!keyles ARPA: keyles@rubbs.FIDONET.ORG