Opened 15 years ago
Closed 15 years ago
#6532 closed defect (worksforme)
Ubuntu 9.10 x64 & VirtualBox 3.1.6 - Internal Network does not work
Reported by: | Henrik23 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.1.6 |
Keywords: | intnet | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description
I tried to configure an internal Network between a Win2k3 Server guest and a WinXP64 guest. I did it via GUI and via "VBoxManage modifyvm <client> --nic1 intnet" but the vms does not "see" each other.
Attachments (2)
Change History (14)
comment:1 by , 15 years ago
comment:3 by , 15 years ago
In that case, please attach the VBox.log files of both VMs to this ticket.
by , 15 years ago
by , 15 years ago
Attachment: | VBox.2.log added |
---|
comment:5 by , 15 years ago
This configuration looks correct and it should work from what I can say. Are you sure that each VM finds the two network interfaces? I saw that you configured two E1000 network cards for the XP64 session, so you installed the proper guest drivers, right?
comment:6 by , 15 years ago
I installed the drivers and both machines find two network interfaces. And the Server makes DHCP on the IntNet interface.
comment:7 by , 15 years ago
So what happens if you assign static IPs to the intnet interfaces of both VMs?
comment:9 by , 15 years ago
But you are aware that ICMP is blocked by the Windows firewall by default, right?
comment:10 by , 15 years ago
No, I was not aware. It does work. But if VirtualBox acts like a switch, why does DHCP not work???
comment:11 by , 15 years ago
Forget this "Bug". Windows standard firewall settings have made me so much trouble. I have disabled the firewall in both machines at the "IntNet" interface and everything works fine now: DHCP works, ping works and the domain works, too. Thank you for the hint to the windows firewall I have not thought that microsoft is so stupid...
Did you assign a static IP to each VM? Because if you use the internal network, there is no DHCP server by default.