Hi, I updated the OS of my Opteron cluster from SuSE9.1 to SuSE9.3 ( not New Installation), the installation went smoothly, however, I found that not all original system configurations were kept: 1. I am not able to use rsh among all nodes in the cluster. 2. The NAT server on the master node is no longer working, I am not able to reach computers outside from client nodes. Here are the original configuration: On the master node (140.110.17.10), I included the following llines in file /etc/init.d/boot.local modprobe ip_tables modprobe ip_nat_ftp modprobe ip_nat_irc modprobe ip_conntrack modprobe ip_conntrack_ftp modprobe ip_conntrack_irc iptables -F; iptables -t nat -F iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to 140.110.17.10 echo 1 > /proc/sys/net/ipv4/ip_forward And defined the gateway to 192.168.3.100 (the internal IP address of the master node) on all client nodes. On SuSE 9.1, this configuartion works normally. 3. In directory /etc/init.d/rc3.d, nfs always executes earlier than ypbind, regardless the assigned numbers, e.g., S01irq_balancer S01random S03dbus S04boot.udev S05network S06syslog S08portmap S08resmgr S08splach_early S09ypbind S10nfs S11nfsboot S12fbset S12kbd S12running-kernel S12splash S13sshd S13sutofs S13cups S13hwscan S13powersaved S13xinetd S14nscd S14pbs_mom S15cron S16hal During the system boot, my intention is to start ypbind before nfs, but SuSE9.3 always execute nfs before ypbind. 4. If install SuSE9.3 as New Installation, I am not able to enable xinetd with YAST2, many network services (e.g. telnet server) are not available. I realize that SuSE9.3 has changed many system default configurations for security reason, but some of these changes caused above problems. Perhaps someone can give me some hints so I can restore my original environment under SuSE9.3? Thanks. Jyh-Shyong Ho, Ph,D, Research Scientist National Center for High Performance Computing Hsinchu, Taiwan, ROC