Hi,
I have a 2 windows 2008 R2 guest on windows 7 host (virtualbox 4.1.8 ). (both 64bit). The first one has two network adapters set, one for the internet and one for internal network, both adapters works fine. The other one has the same configuration but the internal network adapter shows unidentified network and can't connect to the other guest. I've tried different settings for the internal adapter but nothing helps. Any ideas?
Thanks,
Network card - unidentified network
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Network card - unidentified network
I am surprised that they do not both behave like the second one. That is the standard behavior for W2008 with the standard security settings. Unidentified networks are made public by default and this can only be changed in the security settings.
Does the internal network work correctly if you disable the Internet-connected NICs? If so VirtualBox networking is OK. The problems with unidentified networks in 2008 is a general Windows problem and happens on physical networks as well. It is widely discussed in Windows server networking forums.
Does the internal network work correctly if you disable the Internet-connected NICs? If so VirtualBox networking is OK. The problems with unidentified networks in 2008 is a general Windows problem and happens on physical networks as well. It is widely discussed in Windows server networking forums.
Bill
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Network card - unidentified network
See if this helps.
viewtopic.php?f=9&t=27924
viewtopic.php?f=9&t=27924
Re: Network card - unidentified network
Perryg, thanks for that link. The network card is now showing enabled instead of unidentified, but it can't connect to dhcp (the ip is 169.254....). When I set the ip manually to something within the subnet of the other vm both of them can't ping one another.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Network card - unidentified network
Internal are treated as a network switch device, in other words no router. Host-only is designed to allow guest - host communication when no actual network is available.
It will not be able to connect to the LAN dhcp server as they are designed to isolate the guests from the Internet.
If you want to use the LAN on the guests you would use Bridged mode.
Perhaps if you explain what you want to achieve we could figure out the best approach for you.
It will not be able to connect to the LAN dhcp server as they are designed to isolate the guests from the Internet.
If you want to use the LAN on the guests you would use Bridged mode.
Perhaps if you explain what you want to achieve we could figure out the best approach for you.
Re: Network card - unidentified network
Peryyg, again, thanks for your answer. I'm trying to create a LAN between my two guests. I prefer that both of them will be able to access the internet but it is not a must.
Thanks,
Thanks,
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Network card - unidentified network
First I would start with a single adapter on each set to internal and makes sure that they both have the same intnet name.
After that is working you can then add a second adapter to each set to NAT and they should at that point be able to get to the Internet, or you can setup an additional guest to do the routing for you and not have additional adapters in the guests. This is preferred if you are trying to use/test/learn domains in the guests.
See Setup Windows Domain in VirtualBox
After that is working you can then add a second adapter to each set to NAT and they should at that point be able to get to the Internet, or you can setup an additional guest to do the routing for you and not have additional adapters in the guests. This is preferred if you are trying to use/test/learn domains in the guests.
See Setup Windows Domain in VirtualBox