RESOLVED:New User Issues with Amahi Server (in VirtualBox)

[hec1152]

Thanks for the tip. The strange IP address you noted bothered me since I couldn't explain where/why it came from. Upon closer inspection I realized that the Windows host I was using had it's network set up as Bridged vs just normal. I found this by comparing host machine's network setup to another Windows 7 machine. When I noticed the difference I was puzzeled as to why the host was set to bridged. I realized it wasn't because of VirtualBox since the other machine had VB on it as well. So, I reset the host machine's network to not be bridged and made it like the non-host machine. When I did that all seemed to work well. After starting Amahi server VM I turned off the router's DHCP, released and renewed the connection via ipconfig on the host machine and noted that now the host machine and the Amahi VM both had connection to internet which is what I wanted in first place. Now I'm in process of ipconfig release/renew on other machines on network to confirm that they too will pick up IP address from Amahi VM and then be able to see each other (by name and by IP address) on the network. When that's done and all their IP addresses show up on the Amahi dashboard, I will know that everything is working and I can use the VM as my DHCP/DNS server until I can solve the other problem (in Installation section) that's keeping me from being able to get a standalone Amahi server running. When that's solved, I will be able to switch over to the standalone machine and all will be well. I will not post again here if all works as expected. I will instead turn my attention to getting the standalone installation working. Thanks for your help.

[radioz]

Nice! I'm glad you sorted it out. Yes that bridged connection seemed a little strange.

Feel free to post (in a different thread) about your other problems.

[hec1152]

Thanks for the help and encouragement along the way. I think this problem/issue is closed as far as I'm concerned.

Here's the issue I'm working now which relates to getting a standalone machine setup to run Amahi that way instead of relying on VM.

http://forums.amahi.org/viewtopic.php?f=9&t=3605

If I can get help solving above problem I think I'll be on my to relying on Amahi for my fulltime DHCP/DNS.

Thanks again.

[hec1152]

After three years of having a working Amahi Server Guest running under a Windows 7 based Virtualbox installation, the host windows machine crashed. Instead of rebuilding it, I decided to use the opportunity to move my virtualbox HDA guest over to a Ubuntu virtualbox host. Now I'm having trouble getting DHS/DHCP from the Amahi guest to work. After spending weeks on this I am now sufficiently confused as to need help. I apologies if this turns out to be something obvious that I should have caught. And in the interest of completeness in illustrating the problem I offer the following details.

My home network consists of several machines and devices -e.g. kirk.tanbark.intranet (Win7), picard.tanbark.intranet (Win7), slingbox.tanbark.intranet (device), and spocku (Ubuntu 14.04). It has others on it, but these will suffice to describe problem I'm having. SpockU has the Virtualbox installation that hosts the Amahi HDA guest setup witih with a Bridged Network Adapter. The HDA was built using following:
Home Domain tanbark.intranet
Network 192.168.0.*
HDA IP Address 192.168.0.4
Network Gateway 192.168.0.1

The HDA has Static IP addresses loaded for picard, kirk (192.168.0.5), slingbox (192.168.0.7), and spocku (192.168.0.78) as well as other devices on network.

The problem is that DNS and DHCP doen't appear to be working properly to service the network. Here are some indicators

ping from:
HDA to http://www.google.com ok
(Amahi) HDA ok
picard no (response is 192.168.0.4, HDA address)
kirk ok
slingbox ok
spocku ok
picard to http://www.google.com ok
(peer) HDA ok
picard ok
kirk ok
slingbox no (response: “ping request could not find host …”)
spocku ok
spocku to http://www.google.com ok
(Vbox Host) HDA no (response is “unknown host”)
picard no (response is “unknown host”)
kirk no (response is “unknown host”)
slingbox no (response is “unknown host”)
spocku ok
ipconfig from picard:

Windows IP Configuration

Ethernet adapter Network Bridge:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::8c36:30cf:9d3:6f74%25
IPv4 Address. . . . . . . . . . . : 192.168.0.41
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Tunnel adapter isatap.{E9714B91-5A3A-4790-886F-55B95E303AF5}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:341b:33be:3f57:ffd6
Link-local IPv6 Address . . . . . : fe80::341b:33be:3f57:ffd6%28
Default Gateway . . . . . . . . . : ::


ipconfig release/renew from Picard doesn't change it's ip address. Taking spocku on an off network doesn't result in a new ip addr for spocku.

I would think that if DNS/DHCP were working, I could ping by name anything from anywhere on network and it would all work but from indicators above, it doesn't.

What am I missing here? Could someone please help me sort this out because I am at my wit's end and probably am not thinking clearly anymore so I need a nudge.

Thanks in advance.

[hec1152]

Nevermind. I moved over to AmahiExpress, solved a dumb problem (Router DHCP turned off) and am much more pleased with lastest Express. All is ok. Pls disregard. Sorry for the trouble.

[bigfoot65]

Glad to hear this is resolved.

[ Post made via Android ]