If the PPP link becomes active but few hosts on the remote network are reachable, a network problem could be indicated. The following procedure shows you how to isolate and fix network problems that affect a PPP link.
For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.2 .
noccp novj nopcomp noaccomp default-asyncmap
These options provide the simplest uncompressed PPP that is available. Try to invoke these options as arguments to pppd on the command line. If you can reach the previously unreachable hosts, add the options in either of the following places.
/etc/ppp/peers/peer-name, after the call option
/etc/ppp/options, ensuring that the options apply globally
% pppd debug call peer-name
For example, use the following format in any PPP configuration file:
connect 'chat -v -f /etc/ppp/chatfile'
/etc/ppp/chatfile represents the name of your chat file.
Observe the debugging logs. If you still cannot reach remote hosts, the PPP problem might be network-related.
Some organizations assign internal IP addresses that are known within the local network but cannot be routed to the Internet. If the remote hosts are within your company, you must set up a name-to-address translation (NAT) server or proxy server to reach the Internet. If the remote hosts are not within your company, you should report the problem to the remote organization.
Ensure that the intermediate routers have not been misconfigured. Often the problem can be found in the path back to the peer.
# ndd -set /dev/ip ip_forwarding 1
For more information about ndd, refer to the ndd(1M) man page.
In the Solaris 10 release, you can use routeadm(1M), instead of ndd(1M).
# routeadm -e ipv4-forwarding -u
For complete details about netstat, refer to the netstat(1M) man page.
For more information, refer to Common Network Problems That Affect PPP.
A faulty name service configuration causes applications to fail because IP addresses cannot be resolved.