04-08-2011
Windows vista unable to ping to Solaris 10 on VM
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???????
6 More Discussions You Might Find Interesting
1. Solaris
Dear All,
I have installed Sun Solaris 10 on VMWare 6.5 completely and i have configured IP address already. Solaris's IP Address (on VMWare) is 192.168.10.241 and Windows xp that contain VMWare IP address is 192.168.10.125, but when i ping from solaris to my windows it didn't response at all.... (3 Replies)
Discussion started by: veasnabee
3 Replies
2. Solaris
Hi All,
I am using Vmware Workstation 6.0.3 build-80004.
Guest OS: Solaris 10
Host OS : Win XP
I am getting request time out when i am trying to ping from XP ( cmd line) to Solaris VM
- I have assigned IP 192.168.50.5 in Solaris VM ( Hostname: Tower1) and it is in UP status.
... (4 Replies)
Discussion started by: saurabh84g
4 Replies
3. Solaris
I have partitioned and installed Windows Vista, OpenSUSE and Solaris 11 Express on a LapTop hardDrive. However I am not able to boot OpenSUSE 11.3 although I have it in menu.lst which I put in a Solaris partition directory /rpool/boot/grub. Could someone tell me how to go about it. See what I did... (2 Replies)
Discussion started by: Tenyhwa
2 Replies
4. Windows & DOS: Issues & Discussions
Hello All,
I have searched and searched, but I am not finding any answers. Any help would be very welcome.
I have a home LAN centered around an Untangle gateway (up to date).
I have a Windows 7 PC and a Snow Leopard Mac
I also have two virtualized instances of windows (xp and 7) running... (1 Reply)
Discussion started by: toadtilley
1 Replies
5. Solaris
Hello,
Am unable to ping the Windows Box, from my Solaris Box.
They both are in same LAN, have the same IP Segments.
Windows IP :: 10.141.14.120
Solaris IP :: 10.141.14.11
Unable to get why isnt working out.... When using the command 'ping 10.141.14.120', it gives the error as 'ping:... (4 Replies)
Discussion started by: jayanto
4 Replies
6. Solaris
Hi All,
I am new to solaris environment and we are using Solaris 9
The problem is am unable to ping a particular server from from one of the solaris server
The traceroute also shows only * * * for all the 30 hops
I tried to check all the settings like
1) /etc/hosts -> contains the... (17 Replies)
Discussion started by: Sanjay255
17 Replies
LEARN ABOUT DEBIAN
bup-margin
bup-margin(1) General Commands Manual bup-margin(1)
NAME
bup-margin - figure out your deduplication safety margin
SYNOPSIS
bup margin [options...]
DESCRIPTION
bup margin iterates through all objects in your bup repository, calculating the largest number of prefix bits shared between any two
entries. This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.
For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45. That means a 46-bit
hash would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
its first 46 bits.
The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects. Since SHA-1 hashes have 160 bits,
that leaves 115 bits of margin. Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
with far fewer objects.
If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see if
you're getting dangerously close to 160 bits.
OPTIONS
--predict
Guess the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
from the guess. This is potentially useful for tuning an interpolation search algorithm.
--ignore-midx
don't use .midx files, use only .idx files. This is only really useful when used with --predict.
EXAMPLE
$ bup margin
Reading indexes: 100.00% (1612581/1612581), done.
40
40 matching prefix bits
1.94 bits per doubling
120 bits (61.86 doublings) remaining
4.19338e+18 times larger is possible
Everyone on earth could have 625878182 data sets
like yours, all in one repository, and we would
expect 1 object collision.
$ bup margin --predict
PackIdxList: using 1 index.
Reading indexes: 100.00% (1612581/1612581), done.
915 of 1612581 (0.057%)
SEE ALSO
bup-midx(1), bup-save(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-margin(1)