virtualbox win7主机debx64来宾网络问题

时间：2012-06-14 04:54:09

标签： windows-7 virtualbox

首先，我有一个稳定的VM工作正常，然后升级到最新的虚拟机版本，事情变得糟糕。首先我的.vdi崩溃了，无法重新导入，所以我降级到4.1.4，工作正常。我从deb amd64名片iso复制了以前的版本。

随着guest虚拟机从Web获取所有必需的依赖项，找不到问题。但是在重启时我遇到了网络问题。

最初我可以ssh到192.168.56.112，但apt-get返回的网络无法访问。我无法进入其他IP。  所以我做了一点挖掘并删除了70-persistent-net.rules，重新启动，现在又有了不同的排列。

我现在可以通过适配器3（192.168.20.104）上的dhcp地址ssh，DNS似乎与apt-get抓取工作正常。  我可以在ssh请求时立即启动适配器4上的会话登录它会终止连接并且不会重新启用。  本地IP的192.168.56.x拒绝连接。

经过3天多次重新安装后，我仍然无法通过以前的工作来完成基本配置，感谢任何帮助， 谢谢 领域

我的设置如下：

adapter 1 => host-only (intel pro/1000 T server (82543GC)
Adapter 2 => NAT                  (intel pro/1000 T server (82543GC)
Adapter 3 =>  bridged            (intel pro/1000 T server (82543GC) //bridged to :  [Ethernet adapter Local Area Connection:]
Adapter 4 =>  bridged            (intel pro/1000 T server (82543GC) // bridged to : [Ethernet adapter Local Area Connection:]

70持久-net.rules 

 # PCI device 0x8086:0x100f (e1000)
 SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:a7:b9:b2", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

 # PCI device 0x8086:0x100f (e1000)
 SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:ae:b0:9b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1af4:0x1000 (virtio_net)
 SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:1b:16:b4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

 # PCI device 0x8086:0x100f (e1000)
 SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:38:85:3a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"[/code]

接口      ＃环回网络接口      汽车      iface lo inet loopback 

 # The primary network interface
 allow-hotplug eth0
 iface eth0 inet static
 address 192.168.56.112
 netmask 255.255.255.0
 broadcast 192.168.56.255

 allow-hotplug eth1
 iface eth1 inet dhcp

 allow-hotplug eth2
 iface eth2 inet dhcp

 allow-hotplug eth3
 iface eth3 inet static
 address 192.168.20.112
 netmask 255.255.255.0
 broadcast 192.168.20.255

ifconfig -a 

 eth0      Link encap:Ethernet  HWaddr 08:00:27:ae:b0:9b
      inet addr:192.168.56.112  Bcast:192.168.56.255  Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:feae:b09b/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)
      Interrupt:9 Base address:0xd240

 eth1      Link encap:Ethernet  HWaddr 08:00:27:1b:16:b4
      inet addr:192.168.56.101  Bcast:192.168.56.255  Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe1b:16b4/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:6 errors:0 dropped:0 overruns:0 frame:0
      TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:1699 (1.6 KiB)  TX bytes:1152 (1.1 KiB)

 eth2      Link encap:Ethernet  HWaddr 08:00:27:a7:b9:b2
      inet addr:192.168.20.104  Bcast:192.168.20.255  Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fea7:b9b2/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:23 errors:0 dropped:0 overruns:0 frame:0
      TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:3284 (3.2 KiB)  TX bytes:1138 (1.1 KiB)

 eth3      Link encap:Ethernet  HWaddr 08:00:27:38:85:3a
      inet addr:192.168.20.112  Bcast:192.168.20.255  Mask:255.255.255.0
      inet6 addr: fe80::a00:27ff:fe38:853a/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:87 errors:0 dropped:0 overruns:0 frame:0
      TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:10846 (10.5 KiB)  TX bytes:11466 (11.1 KiB)

 lo        Link encap:Local Loopback
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:16436  Metric:1
      RX packets:8 errors:0 dropped:0 overruns:0 frame:0
      TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)

主机的ipconfig      Windows IP配置

 Host Name . . . . . . . . . . . . : tosx500
 Primary Dns Suffix  . . . . . . . : 
 Node Type . . . . . . . . . . . . : Mixed
 IP Routing Enabled. . . . . . . . : No
 WINS Proxy Enabled. . . . . . . . : No

 Ethernet adapter Local Area Connection 10: 

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : TAP-Win32 Adapter V9
 Physical Address. . . . . . . . . : 00-FF-6A-96-C7-8E
 DHCP Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes

 Ethernet adapter Local Area Connection 6:

 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : Microsoft Loopback Adapter
 Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
 DHCP Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes
 Link-local IPv6 Address . . . . . : fe80::f139:e3f3:81f4:cb87%20(Preferred) 
 Autoconfiguration IPv4 Address. . : 169.254.203.135(Preferred) 
 Subnet Mask . . . . . . . . . . . : 255.255.0.0
 Default Gateway . . . . . . . . . : 
 DHCPv6 IAID . . . . . . . . . . . : 654442572
 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-B2-35-4A-C8-0A-A9-0D-C5-90
 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                   fec0:0:0:ffff::2%1
                                   fec0:0:0:ffff::3%1
 NetBIOS over Tcpip. . . . . . . . : Enabled

 Wireless LAN adapter Wireless Network Connection 2:

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
 Physical Address. . . . . . . . . : 70-F1-A1-04-70-B5
 DHCP Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes

 Wireless LAN adapter Wireless Network Connection:

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC
 Physical Address. . . . . . . . . : 70-F1-A1-04-70-B5
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes

 Ethernet adapter Local Area Connection:

 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : Atheros AR8131 PCI-E Gigabit Ethernet Controller
 Physical Address. . . . . . . . . : C8-0A-A9-0D-C5-90
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes
 Link-local IPv6 Address . . . . . : fe80::3593:4f1f:e8a5:9468%11(Preferred) 
 IPv4 Address. . . . . . . . . . . : 192.168.20.103(Preferred) 
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . . . . : fe80::204:edff:fea9:39c%11
                                   192.168.20.1
 DNS Servers . . . . . . . . . . . : 192.168.20.1
 NetBIOS over Tcpip. . . . . . . . : Enabled



Ethernet adapter VirtualBox Host-Only Network:

 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-4C-76
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred) 
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 
DNS Servers . . . . . . . . . . . : 192.168.20.1
NetBIOS over Tcpip. . . . . . . . : Enabled

 Tunnel adapter Teredo Tunneling Pseudo-Interface:

 Media State . . . . . . . . . . . : Media disconnected
 Connection-specific DNS Suffix  . : 
 Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
 DHCP Enabled. . . . . . . . . . . : No
 Autoconfiguration Enabled . . . . : Yes

2 个答案:

答案 0 :(得分：0)

您可能需要在Windows 7上创建网桥，以便将虚拟NIC与物理网桥桥接。使用VirtualBox设置桥接网络有点棘手（VMware自动神奇地做到这一点）。想想我刚刚将两个适配器添加到网桥并为其启用了DHCP（如果我没记错的话）。以防万一：使用WireShark查看实际情况。

答案 1 :(得分：0)

这适用于我在Windows主机上。

将网络适配器配置为

1）允许网络适配器唤醒计算机，

2）允许魔术包唤醒计算机，

3）允许IPV6

http://www.worldstart.com/dropped-internet-connection-in-sleep-mode/

现在，我可以睡觉并唤醒我的机器，客人和主机都将拥有网络，而不仅仅是主机。

相关问题
最新问题