Quick Start Guide

6 After the desktop has started successfully, copy the user's own congurations
back into place:
cp -a KDEDIR /share .kde/share
Replace KDEDIR with the directory from Step 3 (page 144).
IMPORTANT
If the user's own adjustments caused the login to fail and continue to do
so, repeat the procedure as described above, but do not copy the .kde/
share directory.
9.5 Network Problems
Many problems of your system may be network-related, even though they do not
seem to be at rst. For example, the reason for a system not allowing users to log
in may be a network problem of some kind. This section introduces a simple check
list you can apply to identify the cause of any network problem encountered.
Procedure 9.6 How to Identify Network Problems
When checking the network connection of your machine, proceed as follows:
1 If you use an ethernet connection, check the hardware rst. Make sure that
your network cable is properly plugged into your computer and router (or hub,
etc.). The control lights next to your ethernet connector are normally both be
active.
If the connection fails, check whether your network cable works with another
machine. If it does, your network card causes the failure. If hubs or switches
are included in your network setup, they may be faulty, as well.
2 If using a wireless connection, check whether the wireless link can be estab-
lished by other machines. If not, contact the wireless network's administrator.
3 Once you have checked your basic network connectivity, try to nd out which
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
network servers involved in a setup together with the symptoms of an outage.
DNS (Name Service)
A broken or malfunctioning name service aects the network's functional-
ity in many ways. If the local machine relies on any network servers for
authentication 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 communicate.
Common Problems and Their Solutions 145