The Solaris group is a forum where peers share technical expertise, solve problems, and discuss issues related to the Solaris operating system, including OS-related malfunctions, security issues, and network performance.

Unable to ping

hi every one
i have x86 system . i installed solaris on vmware in my system ...
my windows xp ip is 192.168.10.20 my solaris ip is 192.168.10.21
I was able to ping to solaris from my windows xp .
But i was unable to ping to windows xp from my solaris ..
can any one please tell me .why i am unable to ping.what all the settings need to be done ..in vmware to ping to the windows server
Thanks in Advance

First you run # ipconfig/all in your windows system & you can find VMware virtual adapater network card details, select VMnet1. (it will take ip by its own)
EX :- 192.168.136.1

But in your solaris system you assign IP as 192.168.136.7.? If you are connecting from Putty then edit # vi /etc/ssh/sshd_config? file?? ( PermitRootLogin yes ) ? then restart the service. # svcadm restart ssh.

above shiva1 my global zone name)
what is the problem with my system why i was unable to communicate between
global and non gloabal zone and from global zone and unable to ping to
windows xp from global zone

Do a traceroute from your Solaris zones to the Windows address, to see how far you're getting. Check whether your interface is up with ifconfig [interface name]. A netstat -nr will show your routing table in Solaris. It's possible you need an explicit route to the subnet the Windows machine is on, if your default router isn't handling the transfer.

Can you post the o/p of ifconfig -a from both the global and non-global zones?
Have you tried to ping the global zone from the global zone and the same for the non-global zone?
Confirm you addresses are correct, it appears you Windows box and the Solaris Zones are on different networks (192.168.21.x & 192.168.10.x) that may be causing a routing problem

Perhaps you should look into the kind of networking method you specified on installing VMware and/or "interaction" problems between VMware and certain NICs. I've had no recent experience with VMware on Windows, but, for example, if you installed VMware workstation, you might examine such VMware KnowledgeBase articles as:

I have done all the process as specified by yhe link you have provided
but when I select Checksum Offloading and selected the drop down disabled
but when I check it again it is selected as previous one as before.

First you run # ipconfig/all in your windows system & you can find VMware
virtual adapater network card details, select VMnet1. (it will take ip by
its own)
EX :- 192.168.136.1

But in your solaris system you assign IP as 192.168.136.7.? If you are
connecting from Putty then edit # vi /etc/ssh/sshd_config? file? (
PermitRootLogin yes ) ? Then restart the service. # svcadm restart ssh.

Try to connect from putty IP 192.168.136.7.?

100% it will work. If not let me know.
//

I have done the process which you said like
Edit -->virtual network Editor-->
here my selected options are.

Finally my problem solved . i have installed a fresh copy of solaris....now
every thing is working fine
I couldn't find the actual problem where it is...
hope may be with gateways..so on...
what i was using was actually a vmware image of solaris...still i want to
know where the problem is before that i will know about the networking
terminology like gateway ,and so on....and again i will be in touch with you
with in 2 days

Thank you very much professionals for your support. .. and patience.....

HI venkatadry mullapudi ,
In your network configuration of VMware choose bridge network instead of
host only...I think this will fix the issue...but I have doubt that you are
able to ping the ip 192.168.10.21 from XP....I thing this IP is some other
IP configured in your XP box...change the IP of solaris box and then again
try to ping the solaris box with XP...I am sure IT will not ping...the issue
is with host only and bridge network only..

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.