The dns entry is vital. It tells Linux to use an external name server.
Normally, these entries are automatically managed by YaST, but
it would be prudent to check.
If all the relevant entries on the host are correct, let your system
administrator check the DNS server conguration for the correct
zone information. For detailed information about DNS, refer to
Chapter 11, The Domain Name System (↑Reference). If you have
made sure that the DNS conguration of your host and the DNS
server are correct, proceed with checking the conguration of
your network and network device.
4c If your system cannot establish a connection to a network server and
you have excluded name service problems from the list of possible
culprits, check the conguration of your network card.
Use the command ifconfig
network_device
(executed as root) to
check whether this device was properly congured. Make sure that
both inet address and Mask are congured correctly. An error in the
IP address or a missing bit in your network mask would render your
network conguration unusable. If necessary, perform this check on
the server as well.
4d If the name service and network hardware are properly congured
and running, but some external network connections still get long
time-outs or fail entirely, use traceroute
fully_qualified_domain_name
(executed as root) to track the network
route these requests are taking. This command lists any gateway
(hop) that a request from your machine passes on its way to its
destination. It lists the response time of each hop and whether this
hop is reachable at all. Use a combination of traceroute and ping to
track down the culprit and let the administrators know.
Once you have identied the cause of your network trouble, you can resolve it
yourself (if the problem is located on your machine) or let the system administrators
of your network know about your ndings so they can recongure the services or
repair the necessary systems.
A.2.5.1 NetworkManager Problems
If you have a problem with network connectivity, narrow it down as described in
Procedure A.6, “How to Identify Network Problems” (page 255). If NetworkManager
seems to be the culprit, proceed as follows to get logs providing hints on why Net-
workManager fails:
1
Open a shell and log in as root.
2 Restart the NetworkManager:
rcnetwork restart -o nm
258 Start-Up
