1. Problem: "NFS Server xxx.xxx.xxx.xxx not responding, still trying"
Hello everybody,
I have seen similar postings rporting some problems with the NFS
subsystem.
My system: 486DX4/100, 32 MB, 1GB SCSI HDD, running RedHat 4.0
(Colgate), called host.mydomain.here, with one X terminal, called
terminal.mydomain.here. Everything operates through thin ethernet
with a C-class net of the form 192.168.1.xxx. Netmasks, broadcast
addresses etc. work.
My problem: NFS refuses to offer its service to machine on the
network despite correct /etc/hosts and /etc/exports. One path is to
be exported, /tftpboot/terminal, and all classical diagnostics
(route, ifconfig, rpcinfo -p, showmount [-e], tcpdump, statnet,
netstat, ping and telnet) seem to indicate perfect harmony. the
name resolving system works fine, I can use the variants
[commandname] host
[commandname] host.mydomain.here
[commandname] 192.168.1.xxx
(where "commandname" is any of the command accepting host names as an
argument) without any discrimination.
The network (ethernet) is up and running. An X-terminal booting from
"terminal" gets attention by bootpd, and tcpdump shows appropriate
amounts of traffic for loading the boot kernel. The "terminal" machine
reports loading the kernel and starts executing (booting) it. So far,
so good, but even before the kernel tries to grab its root in the
exported file system ("host:/tftpboot/terminal/") the NFS server of
"host" stops cooperating and puts "connection refused" messages
into /var/log/messages.
A local mount test like "mount -t nfs host:/tftpboot/terminal /mnt"
works perfectly. showmount shows one exported file system (exactly
the one I'd like to see exported), and /etc/exports contains all
these funky flags like (no_root_squash,insecure). I even made a
global export of my /tftpboot hierarchy and changed everything of
concern into chmod 777, to be darned sure that everything is world
accessible. (No, I wont't tell you the IP number of my machine ...
;-) )
Any clues?
I've been working for more than a week on this problem, and my
colleague sits impatiently next to me asking when he can start
working using the X terminal.
Thank you for your answers!
Sincerely yours,
Oliver.
--
c/o Wuertz Wielandstr. 20 telephone: ++ 49 - 30 - 852 93 75
12159 Berlin GERMANY
2. connecting Unix to Novell
3. NIS: Serveur not responding for domain "xxx"; still trying.
4. PCI bridge disconnects and retries
5. NIS: server not responding for domain "noname"; still trying.
6. Using DIP to SLIP out ??????
7. These "ICMP redirect from xxx.xxx.xxx.xxx" errors
8. Copying 3rd FreeBSD CD
9. Installation freezing at "Add default route xxx.xxx.xxx.xxx" with NE2000 card
10. RFH: SunOS NIS users can't "automount" their home directory from NIS+ Server
11. "NFS Server volume manangement (/vol) not responding still trying.."
12. NIS Setup Help: "Can't bind to server which serves this domain"
13. Xlib: extension "RENDER" missing on display "ymserver.mydomain.de:1.0"
by