Ako Ni writes: > thanks for the prompt reply mike. appreciate. > > indeed, tried that one but nothing changes. still can not access the other > server on my network. > > the scenario was, after changing the IP range of my servers thats when the > problem occur. > serverA is my dummy server. so that i can connect either of serverB or > serverC, need to login first on my dummer server. > > before i can connect to serverB, i need to login to serverA. now the > situation, i could no longer connect to serverB after changing the IP range > of both server. I know i got it right in change since all are live server.the > only way to connect to serverB is firts connect to serverA-then-connect to > serverC, before I can connect to serverB.
There are two unrelated issues here that need to be detangled. One is name resolution -- how a name such as "serverB" gets converted into a numeric IP address -- and the other is IP packet delivery -- how packets get from one system to another. You need to know *which* problem you have in order to fix it. Can you ping serverB? Try using "ping -n" and serverB's numeric IP address. If you can do that, then the problem is likely to be name resolution rather than IP operation. Check that you don't have stale entries in /etc/inet/ipnodes. Check that you're actually resolving entries via files rather than through a name service (such as DNS) by examining /etc/nsswitch.conf and the output of "getent". Check that the interface configuration is correct on _all_ of the machines you're using. A common reason for the sort of problem you're describing is that you have one or several systems connected to the network that have an incorrectly configured subnet mask. It's most effective to specify the subnet mask in the /etc/hostname.* file (with either "/n" or "netmask n.n.n.n" notation). If these servers are on different subnets, then make sure that the routers between are correctly configured and that all of the hosts themselves have properly-configured routes, or are running routing protocols. Finally, Solaris 9 isn't OpenSolaris. You should be going through your local Sun support organization or one of the many Solaris-related mailing lists or help sites (such as Sun's "bigadmin") instead of coming here. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
