8888 is forwarded to the Wiser's IP. The other traffic to ports on 125.30.124.159 seems okay. - at 455 and at 463 I see 192.168.1.7 connect to 120.75.253.40:8888 and get correct data. So that Wiser appears to be working correctly. I visited my customer for collecting packets data of error connection. But trouble was gone. I did not get any connection error not only remote connection but also local connection. I did not touch WISER. I did not turn off the power of WISER. I had same trouble in last month. I have two schedule to install WISER in next month. If i will have same trouble at WISER installation, It is very tough for me. Attached file is a Packets Capture Data by Packetyzer at my home. The PC at my home was able to connect to WISER at customer house. My customer address 125.30.73.143 PC in my home 192.168.1.7 I can not get any error messages that [TCP window Full] and [Bad Request Content-type]. If you give me any suggestion regarding getting data and testing for getting route cause of trouble, I will do it. I visited my customer for collecting packets data of error connection. But trouble was gone. I did not get any connection error not only remote connection but also local connection. Hi Yoshi, My pleasure. Your latest packet capture looks fine, I see a clean session from 192.168.1.7 to 125.30.73.143. I'm happy the problem is gone. Based on the previous packet capture, it looks