I figured it out.  In the config files the server was set as 192.168.0.254, 
but the network card was configured as 192.168.0.1.  I fixed that and it 
worked fine.  I knew it had to be something dopey!

Thanks guys!
Cindy


On Tuesday 17 December 2002 12:43 pm, [EMAIL PROTECTED] wrote:
> Cindy,
>
> Try checking iptables and/or ipchains
>
>   iptables -L
>
> or
>
>   ipchains -L
>
>
> Make sure you don't have some firewall rules that are getting in
> the way.
>
> you could then try:
>
>    service iptables stop
>
> to disable it.
> Although, you may want the firewall rules for other reasons,
> in which case, we'll need to figure out how to allow NFS to
> your workstations, but noone else.
>
>
> Jim McQuillan
> [EMAIL PROTECTED]
>
> On Tue, 17 Dec 2002, c.murdock wrote:
> > Here's the output of 'ps -e |grep nfs', 'ps -e |grep mountd':
> >
> > [root@backup etc]# ps -e |grep nfs
> >  1241 ?        00:00:00 nfsd
> >  1242 ?        00:00:00 nfsd
> >  1245 ?        00:00:00 nfsd
> >  1246 ?        00:00:00 nfsd
> >  1248 ?        00:00:00 nfsd
> >  1249 ?        00:00:00 nfsd
> >  1250 ?        00:00:00 nfsd
> >  1251 ?        00:00:00 nfsd
> > [root@backup etc]# ps -e |grep mountd
> >  1220 ?        00:00:00 rpc.mountd
> >
> > I stopped and restarted nfs, with the same problem happening.  I copied
> > /etc/hosts and /etc/dhcpd.conf from my other ltsp server, as this one is
> > going to be a duplicate of that one to be used as a backup.  Here's my
> > /etc/hosts (the test-tc client is the one in question):
> >
> > 127.0.0.1       localhost.localdomain   localhost
> > 192.168.1.216   tapeserver.lib  tapeserver
> > 192.168.0.8     test-tc
> > 192.168.0.1     m1
> > 192.168.0.2     m2
> > 192.168.0.3     m3
> > 192.168.0.4     m4
> > 192.168.0.5     m5
> > 192.168.0.6     pw1
> > 192.168.0.7     pw2
> >
> > Here's /etc/dhcpd.conf:
> >
> > # Sample configuration file for ISCD dhcpd
> > #
> > # Don't forget to set run_dhcpd=1 in /etc/init.d/dhcpd
> > # once you adjusted this file and copied it to /etc/dhcpd.conf.
> > #
> >
> > ddns-update-style             none;
> > default-lease-time            21600;
> > max-lease-time                21600;
> >
> > option subnet-mask            255.255.255.0;
> > option broadcast-address      192.168.0.255;
> > option routers                192.168.0.254;
> > option domain-name-servers    192.168.0.254;
> > option domain-name            "inside.lib";
> > option root-path              "192.168.0.254:/opt/ltsp/i386";
> >
> > option option-128 code 128 = string;
> > option option-129 code 129 = text;
> >
> > shared-network WORKSTATIONS {
> >     subnet 192.168.0.0 netmask 255.255.255.0 {
> >     }
> > }
> >
> > group   {
> >     use-host-decl-names       on;
> >     option log-servers        192.168.0.254;
> >
> >     host test-tc {
> >         hardware ethernet       00:a0:cc:e4:69:91;
> >         fixed-address           192.168.0.8;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host m1 {
> >         hardware ethernet       00:20:78:18:44:54;
> >         fixed-address           192.168.0.1;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host m2 {
> >         hardware ethernet       00:20:78:18:44:65;
> >         fixed-address           192.168.0.2;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host m3 {
> >         hardware ethernet       00:20:78:18:44:4B;
> >         fixed-address           192.168.0.3;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host m4 {
> >         hardware ethernet       00:20:78:03:AB:AF;
> >         fixed-address           192.168.0.4;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host m5 {
> >         hardware ethernet       00:20:78:03:AB:B2;
> >         fixed-address           192.168.0.5;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host pw1 {
> >         hardware ethernet       00:20:78:04:D3:8A;
> >         fixed-address           192.168.0.6;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> >     host pw2 {
> >         hardware ethernet       00:20:78:03:AB:C5;
> >         fixed-address           192.168.0.7;
> >         filename                "/lts/vmlinuz-2.4.19-ltsp-1";
> >     }
> >
> > #    host ws001 {
> > #        hardware ethernet     00:E0:06:E8:00:84;
> > #        fixed-address         192.168.0.1;
> > #        filename              "/lts/vmlinuz-2.4.9-ltsp-6";
> > ##        option option-128     e4:45:74:68:00:00;
> > ##        option option-129     "NIC=eepro100";
> > #    }
> > #    host ws002 {
> > #        hardware ethernet     00:D0:09:30:6A:1C;
> > #        fixed-address         192.168.0.2;
> > #        filename              "/lts/vmlinuz-2.4.9-ltsp-6";
> > ##        option option-128     e4:45:74:68:00:00;
> > ##        option option-129     "NIC=tulip";
> > #    }
> >
> > }
> >
> > And here's /etc/exports:
> >
> > #
> > ## LTS-begin ##
> >
> > #
> > # The lines between the 'LTS-begin' and the 'LTS-end' were added
> > # on: Mon Dec  2 16:09:07 EST 2002 by the ltsp installation script.
> > # For more information, visit the ltsp homepage
> > # at http://www.ltsp.org
> > #
> >
> > /opt/ltsp/i386                 
> > 192.168.0.0/255.255.255.0(ro,no_root_squash) /var/opt/ltsp/swapfiles     
> >    192.168.0.0/255.255.255.0(rw,no_root_squash)
> >
> > #
> > # The following entries need to be uncommented if you want
> > # Local App support in ltsp
> > #
> > #/home                  192.168.0.0/255.255.255.0(rw,no_root_squash)
> >
> > On Tuesday 17 December 2002 11:56 am, rob apodaca wrote:
> > > > > ...
> > > > >
> > > > > > I've installed the LTSP on a system running Mandrake 8.2, and my
> > > > > > client boots, but it can't get past "Mounting root filesystem:
> > > > > > /opt/ltsp/i386 from 192.168.0.254".  Nfs seems to be running,
> > > > > > and everything in /etc/hosts, /etc/exports and /etc/dhcpd.conf
> > > > > > appears to be in order.  I'd look in the mailing list archives
> > > > > > for a solution, but they're down.  What am I missing?
> > > > >
> > > > >...
> > > > > Hi Cindy,
> > > > > Check your /etc/hosts.allow file. Post if you need help with it.
> > > > >
> > > > > Cheers,
> > > > > -rob
> > > >
> > > > It looks okay to me.  It's exactly the same as I have on another
> > > > (working) ltsp server.  It's below.
> > > >
> > > > Cindy
> > > >
> > > > bootpd:    0.0.0.0
> > > > in.tftpd:  192.168.0.
> > > > portmap:   192.168.0.
> > > >
> > > > ## LTS-end ##
> > >
> > > Are nfsd and mountd running on the server?
> > > $ ps -e | grep nfs
> > > $ ps -e | grep mountd
> > >
> > > If not, restart them:
> > > $ /etc/rc.d/init.d/nfs stop
> > > $ /etc/rc.d/init.d/nfs start
> > >
> > > If this doesn't solve the problem, you might have overlooked a
> > > configuration error. Perhaps you can post your /etc/dhcpd.conf,
> > > /etc/hosts, and /etc/exports files?
> > >
> > > -rob

-- 
Cindy Murdock
Network Administrator
Meadville Public Library/Crawford County Federated Library System
http://meadvillelibrary.org & http://ccfls.org


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to