[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Raq4 - Kernel 2.4 Upgrade Woes
- Subject: Re: [cobalt-users] Raq4 - Kernel 2.4 Upgrade Woes
- From: Duncan Laurie <duncan@xxxxxxxxxxxx>
- Date: Thu Apr 10 11:06:01 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Josh Trutwin wrote:
Ok, I think I'm close, but you may have to help me a little with DHCP
(sorry for some reason it's something I always have trouble with).
Here is my entire /etc/dhcpd.conf on 192.168.0.4:
option subnet-mask 255.255.255.224; # 255.255.255.0???
you can probably delete this line; it may not matter since it
should be overridden by the subnet block below, but either way
its a conflicting value..
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.0.0 netmast 255.255.255.0 {
range dynamic-bootp 192.168.0.200 192.168.0.210;
option routers 192.168.0.4;
option broadcast-address 192.168.0.255;
}
<snip>
Partition check:
hdc: [PTBL] [1027/255/63] hdc1 hdc2 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 >
autodetecting RAID arrays
autorun ...
... autorun DONE.
Looking up port of RPC 100003/2 on 192.168.0.1
For some reason it is trying to use 192.168.0.1 as the server
instead of 192.168.0.4... Try adding
server-name="192.168.0.4";
to the subnet block in your dhcpd.conf. If you still get nfs/portmap
errors then here is a few things to check:
_ is the server using NFS v2 or v3? (don't use TCP either)
_ what does /etc/exports look like?
_ what does the output of "rpcinfo -p" show?
_ is tcpwrappers running on the server? if yes then you need
an entry in /etc/hosts.allow:
portmap: 192.168.0.
-duncan