UNIX for Dummies Questions & Answers

Hi all,

I have a VM on Solaris 10 setup on a windows vista host machine.

1) Vista host i configure
VMnet 1: 10.1.1.10
Mask : 255.255.255.0
Subnet : 10.1.1.2
DNS : 10.1.1.100

2) Solaris on VM
Network device is on Custom(VMNET1)
IP : 10.1.1.4
Mask : 255.255.255.0

However, i am unable to ping
1) From windows to Solaris
or
2) From Solaris 10 to VM

I have similar setup for Windows 2008 (10.1.1.3) and RHL (10.1.1.11) also on Custom (VMNet1) they are able to work but not Solaris.

Any help on this issue?

---------- Post updated 09-04-11 at 12:09 AM ---------- Previous update was 08-04-11 at 03:51 PM ----------

any help????

---------- Post updated at 12:10 AM ---------- Previous update was at 12:09 AM ----------

any help???????

Emergencies go in another queue!

I am a bit confused, as you change your host references: Vista host (on VMnet), Solaris on VM, windows, Soalris 10, VM, Windows 2008, RHL sounds like 7 hosts.

If host a can ping host b but not vice versa, there is no IP problem. It might be a firewall filter against OCMP protocol or OCMP echo/response, which is ping. Try traceroute. Is there any other problem but ping?

I mean my host PC is a windows vista.......

I config the IP address VMnet 1: 10.1.1.10


Solaris on VM is configured with
Network device is on Custom(VMNET1)
IP : 10.1.1.4
Mask : 255.255.255.0

but i cannot ping........

As for Windows 2008 and RHL i used similar configuration( Different IP address of course) it works perfectly..

Not sure why my sollaries cannot work

cannot ping solaris from vista, or cannot ping vista from solaris, and what about traceroute, other tests?

Can Windows 2008 ping Vista and vice-versa?

How to do a trace route on solaries and vista?


my vista (host) can ping to w2k8 (VM) and RHL(VM) vice versa ........

The spelling changes a bit, and for Solaris traceroute might be in /usr/sbin, in windows, trcroute or tracert; I forget, as I have Google. You can accept the defaults or send tcp or udp starting at your choice of port. traceroute sends packets with time to live TTL set low - 1, 2, 3 . . . , so they die on route and the Ip stack there sends an ICMP back saying your packet ran out of gas here, on ports N, N+1, N+2 . . . for identification. For Vista, there are many nice free tools to do all net things in gui, too. Probably for solaris, too, but I never looked for the X version!

Sorry, but i am confuse ..........

Any help?