Windows implements intranet IPMI port forwarding

work often encounter, some customers do some network applications in debugging often need to break the network operation, but manufacturers provideIpmiaddress are intranet, the work of the springboard machine and do not want to give customers the use, this time can only use the public network provided by the manufacturerIPMIFeature , this feature requires the customer to provide localIP, and then on the function panel,IPMIintranet address and customer localIPaddress binding, this function looks very big, but the use of a lot of problems, first not every customer is willing to provide localIP, and secondly, most of the local people are using dynamicIPaddress, who knows whenIPchanged, so that caused a lot of customers are not connected, and some customers are not connected to the front of the front to push the problem to me, and to bind to the customer well we can not test (only the bound localIPaddress to access the public networkIPMI), and do not want to waste their time to help others work, after the study found that the use of port forwarding on the springboard machine can be implemented by the manufacturer of the public networkIPMIfunction, and there are several on the boardIPidle is not in use, the following will be described in detail how to do the public network on the springboard machineIPMIfunction pushes the issue back to the customer.

first of all, the manufacturer's machine provides IPMI is all over the IPMI, in the use of intranet IP Open Web site login operation, login page

from the page we can see IPMI 's IP Address provides a Port-based Web service, all of which are integrated into the site, and from this inference we have to forward the Port to provide the normal use of the site, well, next let's look at the addition of the established Port of communication, there are no other ports to communicate, first sent under the normal situation of the iKVM Console page

opened the Java IKVM after we see if there are other network connections, use command netstat-ant under DOS | findstr 172.17.5.36 to query, sure enough there are other TCP connections, query results such as:

sure enough, in addition to the port also has a 5900 Port connection, so we need to forward the port, but also to forward 5900 Port

Okay, you know what ports are going to start in communication, because the machine is a Windows system, so here are just some of the port forwarding methods in the Windos environment.

Altogether three orders

1. Create a port forwarding connection

command:netsh interface portproxy add v4tov4 listenaddress= the public IP used to forward IP listenport=80 connectaddress=172.17.5.36 connectport=80

1. View all forwarded connections that have been created

command:netsh interface portproxy show all

1. Remove a port forwarding connection

command netsh interface portproxy delete v4tov4 listenaddress= The public IP used to forward IP listenport=80

Okay, let's create the command we created separately . we're going to forward the IP Port is forwarded to the LAN IPMI Port,

the 5900 port is forwarded to the 5900 Port. Set it up and you're ready to test it.

Do not forget to use the Delete command to delete the forward after the customer.

Note: Always make sure that the port is not occupied before forwarding to the originator.

Windows implements intranet IPMI port forwarding