Linux and WinXP two client interoperability issues in Win7 virtual machines

I actually operate: Two virtual machines are selected Host-onl, view host VirtualBox host-only Network IP address is 192.168.56.1, then I let linux,windowsxp all let for the URL 192.168.56.2, 192.168.56.3,

You can then ping each of the two virtual machines in the following way, only the settings above, and may not be guaranteed to ping the Windows and Linux issues. This involves both sides of the firewall problem.

1. There is a firewall on the WinDOS side. If you find that Windows can ping Linux, and Linux cannot ping windows, it should be a problem with your Windows native Firewall policy. I was also tortured by this problem for a long time, until the shutdown of the WINDOSW this machine's firewall, and finally to achieve ping interoperability. The shutdown method for shutting down the native Windows Firewall is as follows:

Start, Control Panel, System and security, Windows Firewall on or off Windows Firewall, shut down Windows Firewall

2, there is a firewall on the Linux side. Linux can ping windows at this point, but Windows cannot ping Linux.

The way to check if Linux has a firewall is to:

The Iptables-l command looks at the current Linux system's policies.

I don't need a variety of firewall policies here, so it's straightforward to set up a firewall rule as follows:

Iptables-f//emptying current firewall rules

Iptables-x//Remove all firewall rules for system configuration

Iptables-p INPUT ACCEPT

Iptables-p OUTPUT ACCEPT

Iptables-p FORWARD ACCEPT

As long as the above command is configured to boot automatically, the current firewall policy for Linux systems after booting is as follows:

In this way, the firewall settings for Linux are removed.

Now, you can implement IP interoperability between Windows <-> Linux systems. With the SSH service on Linux, Samba services can be logged on from Windows normally.

////////////////////////////////////////////////////////////////////////////////////

About Win7 and virtual machine Linux interoperability issues

First, we'll show you how to set up a Linux network in VMware. The general network options are bridged, NAT, host-only several. This time with my implementation of the host-only as a sample to do a detailed explanation, such as:

After selecting Host-only mode, open the Network Properties edit window of VMware and you can see that the VMnet1 NIC is already visible.

Here VMnet1 can be set subnet IP is 192.168.0.0, mask is 255.255.255.0.

With regard to DHCP options, this can be done here, because I configure a static IP on a Linux virtual machine using YaST, such as: 192.168.0.222 (Note: This static IP address must be on the same network segment as the IP address set on subnet),

Regarding the NAT setting in the options, I have set the gateway IP address to 192.168.0.1 in strict accordance with the recommendations on the network (in fact, I also tried to use the 192.168.0.* any IP, as long as the host and the Linux virtual machine IP conflicts, no problem). Such as

Basically, the configuration of the above VMware virtual machines is done, and the Linux-side network configuration based on Host-only mode is available.

Then configure the new network interface card VMNET1 on the Windows local machine. Here also just set its IP address to 192.168.0.2 (must be in the same network segment as the previous subnet IP). Such as:

At this point, the network setup between the Windows native and the Linux virtual machine is complete.

Of course, only the above settings, may not be guaranteed to achieve Windows and Linux ping interoperability issues. This involves both sides of the firewall problem.

1. There is a firewall on the WinDOS side. If you find that Windows can ping Linux, and Linux cannot ping windows, it should be a problem with your Windows native Firewall policy. I was also tortured by this problem for a long time, until the shutdown of the WINDOSW this machine's firewall, and finally to achieve ping interoperability. The shutdown method for shutting down the native Windows Firewall is as follows:

Start, Control Panel, System and security, Windows Firewall on or off Windows Firewall, shut down Windows Firewall

2, there is a firewall on the Linux side. Linux can ping windows at this point, but Windows cannot ping Linux.

The way to check if Linux has a firewall is to:

The Iptables-l command looks at the current Linux system's policies.

I don't need a variety of firewall policies here, so it's straightforward to set up a firewall rule as follows:

Iptables-f//emptying current firewall rules

Iptables-x//Remove all firewall rules for system configuration

Iptables-p INPUT ACCEPT

Iptables-p OUTPUT ACCEPT

Iptables-p FORWARD ACCEPT

As long as the above command is configured to boot automatically, the current firewall policy for Linux systems after booting is as follows:

In this way, the firewall settings for Linux are removed.

Now, you can implement IP interoperability between Windows <-> Linux systems. With the SSH service on Linux, Samba services can be logged on from Windows normally.

Linux and WinXP two client interoperability issues in Win7 virtual machines