[CodeVisio]

Hello everyone,

I'd like to configure eMule under VirtualBox.
Up to now, I'm only able to connect to eD2K but not to Kad.

Host OS: Windows 10
WM: the last VirtualBox
Guest OS: Windows 7, where eMule is installed on.

Is that possible? what should I do then?

Thanks

[Zangune]

Hello, yes it is possible.
If you have a high ID you have to do nothing but downloading something to "bootstrap" Kad, otherwise you have to setup at least VirtualBox and your router.
The easy way is to set the VirtualBox network in bridge mode and forward eMule ports in your router normally, otherwise you have to forward eMule ports in VirtualBox, too. From a network point of view it is like you have to setup a double port forwarding, more or less, at least.
Here you can read about double port forwarding, here you can read about the bridge mode and here you can read how to setup port forwarding in VirtualBox.
The correct procedure to setup your router depends on the router itself, if you will search this forum it is full of examples.
Sometimes, but not always, you have to setup the Windows firewall, in this case both for Windows 10 and Windows 7.
Just to let you know: eMule works under Windows 10 and it will not "taint" your system.

[userofemule]

Hi, this post is about connecting to eMule servers from a VirtualBox virtual machine, running Windows 10. It is not about opening ports and configuring High ID, I’ve achieved that already. My problem is eMule will not connect to any server.
I also want to say I’ve read all the posts I’ve found in this forum about eMule and VirtualBox before asking in this post. Maybe I’ve skipped something (I’m not very knowledgeable on the subject), but all posts I’ve found are about opening ports on your VM. I have my VM running on “Bridged” mode. I’ve assigned a fixed IP for the VM and I’ve opened the eMule ports for the VM on the router. When I go to “Test ports” from eMule it says both TCP and UDP ports are open.
I’ve downloaded a server.met file and loaded them onto eMule. But it will not connect. On the “Log” tab it says server appears to be dead, and skips to the next server. I have the same setting on my host PC and it connects just fine. I’ve also tried connecting from my host and the trying to connect to the same server (in case some servers on the list were down) but it failed. I really don’t know what to do. Everything I’ve found, both on this forum and on the internet is about opening ports. The thing that perplexes me the most is that usually people say after just installing eMule on a VM they can connect with no problems, they just get a low ID. But I can’t connect at all.
I appreciate your time just for reading this post. If you have some tip or idea, please share it, even if you are not sure. Thank you very much.

[fox88]

userofemule, on 02 May 2020 - 02:41 PM, said:

I’ve downloaded a server.met file and loaded them onto eMule.

Older server.met might have all servers dead.
For example, I forwarded ports in NAT adapter of my Virtualbox VM.
TCP test passed. Though UDP test failed, I still was able to conenct to Peerbooter server with high ID.

[userofemule]

fox88, on 02 May 2020 - 02:21 PM, said:

userofemule, on 02 May 2020 - 02:41 PM, said:

I’ve downloaded a server.met file and loaded them onto eMule.

Older server.met might have all servers dead.
For example, I forwarded ports in NAT adapter of my Virtualbox VM.
TCP test passed. Though UDP test failed, I still was able to conenct to Peerbooter server with high ID.

Hi. Thanks for your response. I went to the website yesterday and loaded the server list from there. I don't think it'll be an old list. And I can connect to the same servers on my host computer. I just can't connect to any server.

[fox88]

userofemule, on 02 May 2020 - 05:40 PM, said:

I can connect to the same servers on my host computer.

Fine. The list is up to date then.

Thing looked less good in futher investigations.

Virtualbox 6.1.6, Windows 8.1 64-bit host, Windows 10 1909 guest.
Both host's and VM's firewalls were turned off for the tests, but it did not help.
With a public IP, no forwarding is needed except for the NAT adapter.

The bridged adapter with the default settings just would not connects to the internet.
A few reports on this issue could be found in the net.

What is your configuration and settings?

NAT adapter also behaved erratically.
Servers often appeared to be full or give low ID, though sometimes high ID was possible.
UDP test always fails, hence KAD is firewalled.

[userofemule]

Hi Fox88. Again, thanks for your time. I've tried disabling both firewalls on the host and on the physical machine, but still nothing. I tried NAT instead of bridging, but still not connection.
Do you have any tip I could try?
Thank you very much.

[fox88]

eMule in VM gets the same public IP as in the host system.
What is the point of these efforts?

[userofemule]

You are totally right. The point is to allow my father to use emule from a VM, when he doesn't have access to the physical machine. In this way he can use eMule autonomously, without having to ask me every time he wants to download something, which is less than desirable

[fox88]

If there is connection to internet, eMule usually is able to connect to servers with low ID at least.
You could try logging packets in firewall to see what is sent and received.

Maybe it would be simpler to provide multiple RDS connections to the host instead.
Or run second instance of eMule and manage it using Web Interface.

This post has been edited by fox88: 05 May 2020 - 09:27 PM