Port ing + peanut shell handle farm monitoring

Edit: What you see on a blog is interesting.

Big shrimp (dxm) Technical blog

When I was a child, an uncle who took me to school in his hometown could not connect to the farm monitoring he was doing.
This is a video surveillance system based on the DVR platform, which can be remotely monitored through webpages. The customer is a Hong Kong boss. his cattle farm is in our hometown. The Hong Kong Boss wants to see his ox in Hong Kong.

After receiving the call, I did not dare to neglect it. I opened QQ and connected his monitoring host with remote assistance.
Check the DVR help file to know that the WEB port of the DVR is 808, and the data ports are 9002.

Run netstat-a under the command line and find that all these ports are open.

Then, check the peanut shell and find that the IP address obtained by pinging XXX.gicp.net from the Internet is the Internet IP address on the router. No problem!

Check the previous installation records and find that the IP address of the machine was 192.168.1.102. Now it has become 192.168.1.101. How has it changed? It turns out that he is automatically assigned an IP address! This does not work. If it is automatically allocated, it will be different each time. How can we do port ing on the router? Then manually set the IP address.

Then, check the vro configuration, where the virtual server is found to have no entries, So I published ports 80, and 9002.

Then we can connect to the Internet and find that the connection is still disconnected. after observation, he found that the rising firewall was installed in his system, and the firewall that came with Windows. I first opened the above four ports on the windows Firewall and found that the ports are accessible.

In short, the lesson I learned from this story is that complex problems must be analyzed step by step and can always be solved.

Finally, let's take a look at the cattle raised by our hometown