What if Windows and VirtualBox port number mappings fail?

When running an Ubuntu system in a VirtualBox virtual machine, it is sometimes necessary to use port mapping to implement the host PC-side and virtual-machine internal mirroring communication, and the ports and services within the virtual machine. These ports are mapped during the VirtualBox startup phase, but what happens when the port mappings fail for some machines in windows, and what about Windows and VirtualBox port number mappings?

　　The port mapping failure log is as follows:

00:00:01.125577 nat:set redirect UDP host 0.0.0.0:6000 = "Guest 10.0.2.15:6000

00:00:01.125748 Nat:can ' t create datagram socket

00:00:01.125763 nat:failed to redirect UDP 0.0.0.0:6000 = "10.0.2.15:6000

00:00:01.125774 nat:set redirect TCP host 0.0.0.0:6555 = "Guest 10.0.2.15:5555

00:00:01.125897 nat:failed to redirect TCP 0.0.0.0:6555 = "10.0.2.15:5555

　　Analysis:

1. The port number mapping here does not occupy the official Windows assigned port number, and any problem that does not exist that the port number is not being consumed by the Windows service causes an invalid mapping

2. View all ports using Netstat-ano, no mapped port number is occupied

3. The above two points are excluded, then troubleshoot the Windows system's own environment, by verifying that the problem can be fixed through the repair tool. That is because of Windows ' own environment.

Specific fixes: Repair Winsock & DNS Cache

　　The function description is as follows:

This'll clear the stored DNS cache in Windows. When the DNS becomes corrupt you are not being able to some sites. Flushing and rebuilding the DNS would fix that problem.

Also resets Winsock entries & resets TCP/IP stack.

These extra commands are run on Windows Vista and newer.

You can repair the failure of the port number mapping by performing the following commands and then rebooting, which is not limited to the port mappings that VirtualBox to use, and any other software that uses the port mappings and fails to repair it with the following commands:

netsh winsock reset all

netsh int 6to4 reset all

netsh int ipv4 reset all

netsh int ipv6 reset all

netsh int httpstunnel reset all

netsh int isatap reset all

netsh int portproxy reset all

netsh int tcp reset all

netsh int teredo reset all

These commands are derived from one of the Windows repair tools

If you have other windows problems, try to mirror the repair with this tool.