How to get IP from virtuabox for HFM ?

[Markfw]

OK, I have had a horrible week. 2 GTX 460's went down due to fans, and now my 3930k locked up. After messing with it for 2 days, I have it runnig at 4 ghz, but I now can't get the virtuabox to show in HFM. It worked before, but after the reboot, the IP changed. ifconfig showed no 192 IP addresses. And I tried my old method of connecting to any unknown 192 IP address under 40. No luck

 

[Ken g6]

It may help to configure your VM's network adapter (in VirtualBox settings) to a "Bridged Adapter", instead of NAT. Networking's faster that way, too.

 

[GLeeM]

Same thing happened to me awhile back.

Can't remember what I did.

I'll give this a bump - someone knows.

 

[Markfw]

It may help to configure your VM's network adapter (in VirtualBox settings) to a "Bridged Adapter", instead of NAT. Networking's faster that way, too.

OK, the only settings I think I could make is to allow all for "promiscuous mode" (if I types that right.

Can you be more specific ?

 

[biodoc]

I haven't actually done this for HFM.net access but I do have virtualbox running on a couple of machines. The virtualbox machines do not show up on my router connection list as "192" ip addresses. After googling this it looks like you either type ifconfig or info at the command line and hit return.

ifconfig gives me this for the ethernet connection (eth0).

eth0 Link encap:Ethernet HWaddr 08:00:27:63:FE:91
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe63:fe91/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:39 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1322 (1.2 Kb) TX bytes:7223 (7.0 Kb)

According to what's on the web for HFM.net, you would type your virtual machine IP address (see above for mine in bold) in a format like this:

\\10.0.2.15\fah

 

[somethingsketchy]

As Ken had alluded to, it sounds like the F@H clients are on NAT (usually a 10.*.*.* address). That'll work for each client to get their own Internet connection, however when you try to access them externally, a la HFM.net, they won't be able to connect.

If you set the network connection to Bridged, this will allow HFM to connect to each VM.

 

[Markfw]

ok, this is really bad. I just finished a 427k point unit. It has no IP address, its 169. I tried ifconfig to manually reset it, and it says "host name lookup failure"/

I tried this:
ifconfig eth0 192.168.1.12 netmask 255.255.255.0 broadcast 192.168.1.255

also, probably a mistake, but it kept prompting me to upgrade my vitualbox, so I did. This problem has been there ever since that upgrade.

EDIT:
I shut off the network device, then re-enabled it. Then I restarted the vm. I may have lost the 427 points, as I saw file IO error, but it was able to get a new units, and now shows as my old IP of 192.168.1.12.

Between Oracle and F@H, I don't know why I don't just quit.....5 days folding for nothing, just because Oracle wanted me to upgrade to a new version.

 

[somethingsketchy]

You should be able to launch VMs with an older client. Granted you will always get prompted to upgrade the next time you launch VirtualBox, but you should still have launch capabilities.

 

[Markfw]

You should be able to launch VMs with an older client. Granted you will always get prompted to upgrade the next time you launch VirtualBox, but you should still have launch capabilities.

Oracle puts a popup in your face every few hours, its very annoying, so I upgraded to get rid of the box.... Never again

Problem solved for now, just very annoying that I lost all that work.

 

[Markfw]

Update, the new unit finished, but then had the same problem. Deleted all the VM's, downloaded a new VDI, and rebuilt a new VM. Problem solved (again)