On Wed, 22 Nov 2000, Tony Nugent wrote:
> I suspect that the server's mountd daemon isn't able to resolve
> the client's IP address to a name... check the syslogs on the
> server.
Nov 22 12:54:31 kirin rpc.mountd: authenticated mount request from testbox:611 for /kickstart (/kickstart)
Nov 22 12:54:32 kirin rpc.mountd: authenticated mount request from testbox:615 for /local/tmp (/local/tmp)
this is the log from the server. So it sounds like the client mounts the
necessary directories just fine (BTW, under /local/tmp is RedHat/ directory)
> Quick kludge (if this is in fact the problem) is to create an
> entry for the client in it's /etc/hosts file, or put an entry
> into it's dns server's database (which should restrict 192.168/16
> for internal uses, but you already know that:)
>
> Or /etc/hosts.{allow,deny} could be denying portmapper access
> (that's happened to me before too :)
Reverse lookup succeeded. I tried this on two different network and
on the first one the reverse lookup failed - in that case alt+F3 got stuck
at
getting ready to spawn a shell now
but on the second network where the reverse lookup succeeded, it goes past
the "getting ready to spawn a shell now" message and prints out bus probing
messages, module inserting messages and such... But alt+F2 does not show
bash prompt, so I guess spawning a shell has failed?
At this point alt+F4 shows the same message regarding nfs server not
responding. (If it helps, it also says task 37 can't get a request slot).
Any more ideas? :(
If all is to fail, how hard or feasible is it for me to look into
kickstart via ftp?
Thanks
Andrew Park
________________________________________________________________________
CDFlab Systems Administrator www.cdf.utoronto.ca |
GnuPG Signature www.cdf.utoronto.ca/~apark/public_key.txt |
------------------------------------------------------------------------
