On Tue, Jan 6, 2009 at 11:30 AM, Paresh <pareshp at gmail.com> wrote: > > > Moinak Ghosh wrote: >> >> On Mon, Jan 5, 2009 at 6:24 PM, Paresh <pareshp at gmail.com> wrote: >> >>> >>> Hi, >>> >>> I am newbie to Belenix/opensolaris. I wanted to test Windows 2003 with >>> EMC Retrospect insatalled. I was able to get running Windows2003 >>> Standard as guest machine under Vitualbox on top of Belenix. >>> >>> I have configured my guest OS (Windows 2003) to use host interface in >>> Virtualbox. Guest OS acquire its TCP/IP setting from my local DHCP >>> server. I am able to ping all the systems in my local network from guest >>> server & vice versa. I have disabled firewall on guest OS. Everything >>> seems to work fine, but when I try to add Retrospect client to >>> Retrospect database it comes up with an error. However all the clients >>> are visible when Retrospect does a multicast to find clients listening >>> on port 497. I think Retrospect uses UDP port for multicast & TCP port >>> 497 for actually adding the client to its database. >>> >>> Is Belenix (host OS) not allowing Retrospect server to communicate with >>> its clents on port 497? >>> How can I open above port in Belenix? >>> >>> Thanks in advance. >>> >>> >> >> Is the client running inside the guest OS ? Which version of VirtualBox >> are you using ? What you are trying to do requires Virtual NIC support >> which is available in the latest versions of VirtualBox. >> >> Regards, >> Moinak. >> > > No the clients are Windows based desktops & laptops. Only the Retrospect 7.6 > server is running on the guest OS (Windows 2003). I have VirtualBox 2.1.0 > installed on Belenix(build 93 64 bit). From the VirtualBox documentation, in > order to have host interface type of NIC for the guest OS, the host OS > (Belenix in my case) needs to support bridging of NIC. Does the Belenix > (build 93 64 bit) support bridging?
B93 does not support bridging. BeleniX B101 and later has Crossbow which support Virtual nics which will provide the functionality you need. Virtual nics allow slicing a single physical NIC into multiple separate ones each with it's own datalink and TCP/IP stack. So there is no need for bridging in that case. Virtualbox can use VNICs. You can safely upgrade you BeleniX installation to B101 via the following instructions: # Install the new package manager pkgadd -d http://www.belenix.org/binfiles/SFEaxel.pkg pkgadd -d http://www.belenix.org/binfiles/SFEspkg.pkg # Update the catalog spkg updatecatalog # Upgrade (This will download packages) spkg upgrade base belenix_0.7.1b_crossbow The upgrade process will create a new boot environment and upgrade that and a new GRUB boot entry will be created. Your current boot environment will be left untouched and you can fallback to that should there be a problem. After this you can refer to Crossbow documentation on using Vnics: http://www.opensolaris.org/os/project/crossbow/Docs/ -- ================================ http://www.belenix.org/ http://moinakg.wordpress.com/
