Re: Serious Problems with diskless clients

[Marco Schwarz <marco.schwarz@gmx.net>]

> On 26 September 2002 08:26, Marco Schwarz wrote:
> > Hi all,
> >
> > my diskless clients have some severe problems on one of my servers.
> > Sometimes (right now most of the time) everything just hangs at the same
> > place when starting up the kernel. Here are the last messages I get
> (right
> > before this IP-Config is running and looks OK):
> >
> > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0
> > ds: no socket drivers loaded !
> > Looking up port of RPC 100003/2 on 192.168.0.235
> > portmap: server 192.168.0.235 mot responding, timed out !
> 
> Hook another box to the same network segment and run
> ping or mtr to 192.168.0.235 and to the booting box.
> Maybe your net drops packets or otherwise misbehaves.
> 
> BTW, 2.4.10 is way too old. 
> I don't see "mot responding, timed out !" in 2.4.19
> source, rather "not responding, timed out".
> --
> vda
> 

"mot responding" is just a typo, I had to type all the messages from screen
;-)

I already tried pinging, works in both directions. On the server I start
portmap now with 'portmap -v' and I am able to see the requests from the client:


'connect from 192.168.0.87 to getport(nsf)'
'connect from 192.168.0.87 to getport(mountd)'

I also see some messages from Portmap which look like this:

'connect from 192.168.0.87 to dump()'

I also have to note that I have 2 NICs in this server, one with adress
153.95.240.x and one with 192.168.0.x.

Problems seem to occur only on the 192.168.0.x network (I already
interchanged adresses between cards, no effect).

BTW: Is there a newer version of portmap than 5.1 ? I wonder if this is
maybe related to portmap ...

Regards,
Marco