More, see below...
--- Peter Billson <[EMAIL PROTECTED]> wrote:
> Dana,
> 1) Do you have your workstations listed in your
> /etc/hosts file? On
> the server:
> does a "ping ws001" return the correct IP?
Yes, and I can ping the IP, also.
> 2) Try running tcpdump on the server during client
I didn't notice a hosts file there in your list. It should look
something like this:
192.168.0.102 ws001
192.168.0.103 ws002
Wihtout that the names you are providing in dhcpd.conf will not map to
IP addresses and the NFS mounts will fail. I also agree you should check
your /etc/exports.
Pete
Dana,
The hostname to IP mapping is required for NFS (and other things) to
work.
What is your server's fully qualified domain name (FQDN)? A hostname
-f will tell you if you are not sure.
Say your server's FQDN is server.foobar.com. You client entries should
should look like:
192.168.0.102
Dana,
1) Do you have your workstations listed in your /etc/hosts file? On
the server:
does a "ping ws001" return the correct IP?
2) Try running tcpdump on the server during client boot up to see
if the NFS mount request is coming into the server.
3) Since you got a mystery IP (the
Contents of /etc/hosts is
127.0.0.1 DanaLinux localhost localhost.localdomain
192.168.0.6 DanaLinux
192.168.0.102 ws001
192.168.0.103 ws002
As I understand it, only the IP is necessary and the
rest is so we can use names instead. That's simplistic
but that's a
Thanks, Sudev...
I have no idea where the "101" came from and, on a
reboot of the client, it doesn't show up.?.
I tried removing the quotes, then the client will not
get as far and the card is not properly recognized.
It's interesting that these were placed upon
installation automatically with the
dana,
if you can get to the #ltsp irc channel on irc.freenode.net, I
can help you interactively.
Wednesday i'll be gone most of the morning, but I should be around in
the afternoon. East coast time here.
Jim McQuillan
[EMAIL PROTECTED]
On Tue, 11 May 2004, Dana Persells wrote:
> Folks,
> I
Thanks for your response, Peter...
Correct, no mount message.
/etc/exports is correct with no space.
Both machines have booted successfully in windows and
attached to the server through Samba as late as
yesterday.
This is why it's so frustrating. I know that I can
boot windows and attach to the ser
Dana,
I am assuming you do not see a NFS mount message in the server's logs.
1) Is your /etc/exports file correct? Something a small as a space in
the wrong place can screw things up. A known-good one is available at
http://www.elbnet.com/libsys/libsys/etc/exports Note in particular that
there i
Folks,
I know it's frustrating to hear from me still with the
same problem...
Trying to boot 2 different clients; different CPU's,
RAM, Video, netcard, IP addresses are 192.168.0.102 &
192.168.0.103 with kernel loading and dhclient
running. Both boot through to "mounting root
filesystem: /opt/ltsp/
10 matches
Mail list logo
