Novell LINUX ENTERPRISE DESKTOP 10 SP2 - DEPLOYMENT GUIDE 08-05-2008 Deployment Manual page 842

Once you have identified 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 findings so they can reconfigure the services or repair the
necessary systems.
46.5.1 NetworkManager Problems
If you have a problem with network connectivity, narrow it down as described in
(page 822). If NetworkManager seems to be the culprit, proceed as follows to get logs
providing hints on why NetworkManager fails:
1 Open a shell and log in as root.
2 Restart the NetworkManager:
3 Open a web page, for example,
4 Collect any information about the state of NetworkManager in /var/log/
826 Deployment Guide
Use the command ifconfig network_device (executed as root)
to check whether this device was properly configured. Make sure that both
inet address and Mask are configured correctly. An error in the IP
address or a missing bit in your network mask would render your network
configuration unusable. If necessary, perform this check on the server as
well.
4d If the name service and network hardware are properly configured and run-
ning, but some external network connections still get long time-outs or fail
entirely, use traceroute fully_qualified_domain_name (exe-
cuted as root) to track the network route these requests are taking. This
command lists any gateway (hop) 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.
rcnetwork restart -o nm
user to see, if you can connect.
NetworkManager.
http://www.opensuse.org
as normal