Please login or register to participate.
zbricker Dec 09, 2009 05:38 AM
So, I'm supposed to do evaluating of the installation procedures of different collaboration/cms software for the university I attend and work at. Someone said they had seen something called "sign in"(Found it, obviously) and that I should check it out. I'm literate but not experienced, but I decided to try my hand at getting setup locally and giving it a test run. I don't have a spare PC for a server using the CE Appliance so I installed VirtualBox, told it I was running Ubuntu, mounted the .iso on a virtual drive and installed the software as per the tutorial. It boots and I'm greeted with the linux command prompt and can sign in as root, however trying to access the web interface nets me nothing. I'm not sure where the problem lies, whether it's win7 and virtualbox or something I messed up with the installation. Any pointers to the right direction would be great.

Replies (5)
viraf Dec 09, 2009 06:43 AM
login in to your in the virtualbox and check whether your VM has an IP Address...
dhiraj Dec 14, 2009 10:48 PM
Hmm... probable/possible screwup areas:

1. In Virtual Box, change your network settings from the default of NAT networking to use Bridged networking. This is usually the first thing that is done wrong, changing this usually gets you the correct IP address (especially if you have a working DHCP server allocating IP addresses somewhere in your LAN).

2. Once your virtual box image has booted, login as root on the console that comes up, and see what IP address the ifconfig command is reporting for your network card. If ifconfig reports only a "lo" interface, the server is not finding your virtual network card - did you answer yes to any/all the driver installation prompts that came up during Virtual Box installation? If you can't figure out what the output from the ifconfig command means, paste it in reply (or upload a screenshot if copy-paste is difficult).

3. We've not really had a chance to check out Virtual box running on Windows 7, yet. Are you running the 32 bit one, or the 64 bit edition? Try installing a normal Ubuntu or Debian from the CD download of either distros on to a new Virtual machine, and see if that is getting networking and otherwise working properly - this could help you identify what exactly is going wrong. If you identify your problem to be with Virtual Box itself, you could try and have a go with some alternate Virtualization tech - like Windows 2008 Server (HyperV) or VMWare Server/Workstation products.
domderrien Mar 31, 2010 09:57 PM
Just to confirm that the switch from the NAT to Bridged worked for me, with the only glitch that I've to access the Cynapse page from another computer... It seems the Bridged settings block my accesses to the local network?
dhiraj Apr 01, 2010 11:56 PM
No it shouldn't block your same machine access!? We use this setup quite frequently for our own appliance testing, so that's not it, something else is wrong. A DNS / domain cache problem, perhaps? Try a different browser on your own machine.

What's the exact error you're getting in your browser?
anandh Jul 07, 2010 04:07 PM
Changing network from NAT to Bridge solved my issue. Thank you.
VM Name > Settings > Network > Attached to: Bridge Adapter