Novell LINUX ENTERPRISE SERVER 10 SP2 - INSTALLATION AND ADMINISTRATION Installation Manual page 952

2 If using a wireless connection, check whether the wireless link can be established
3 Once you have checked your basic network connectivity, try to find out which
934 Installation and Administration
by other machines. If this is not the case, contact the wireless network's adminis-
trator.
service is not responding. Gather the address information of all network servers
needed in your setup. Either look them up in the appropriate YaST module or
ask your system administrator. The following list gives some of the typical net-
work servers involved in a setup together with the symptoms of an outage.
DNS (Name Service)
A broken or malfunctioning name service affects the network's functioning
in many ways. If the local machine relies on any network servers for authen-
tication and these servers cannot be found due to name resolution issues,
users would not even be able to log in. Machines in the network managed
by a broken name server would not be able to "see" each other and commu-
nicate.
NTP (Time Service)
A malfunctioning or completely broken NTP service could affect Kerberos
authentication and X server functionality.
NFS (File Service)
If any application needed data stored in an NFS mounted directory, it would
not be able to start or function properly if this service was down or miscon-
figured. In a worst case scenario, a user's personal desktop configuration
would not come up if his home directory containing the .gconf or .kde
subdirectories could not be found due to an outage of the NFS server.
Samba (File Service)
If any application needed data stored in a directory on a Samba server, it
would not be able to start or function properly if this service was down.
NIS (User Management)
If your SUSE Linux Enterprise system relied on a NIS server to provide the
user data, users would not be able to log in to this machine if the NIS service
was down.