Unable to Connect to WISER

Hi

I'm managing two WISERs.
One is my customer's and other is my office's.
These two site have same configuration.
LAN address : 192.168.100.***
Router address : 192.168.100.1
WISER address : 192.168.100.150
CNI address : 192.168.100.151

WISER is LAN connection mode.
I arranged same Router unit for both site.

I updated firmware to 1.25.0 for both sites.
After that, I can not connect to customer's WISER from remote.
Authentication window is appeared.
But I got [Unable to Connect to WISER] message.
But I can connect my office's WISER from remote.
I swapped WISER between my customer's and my offices's.

But trouble is still there.
I can not connect to customer's WISER from remote.

The difference between my customer site and my office is ISP.

Attached file is Packets Capture Data by Packetyzer at my home.
My office address 120.75.253.40
My customer address 125.30.124.159
PC in my home 192.168.1.7

I got [TCP window Full] message in number 2851 packet and [Bad Request Content-type] in number 2915 packet.
I found these messages only error connection between 192.168.1.7 and 125.30.124.159.

I guess this trouble is related difference of ISP.

Please get cause of trouble.
I will arrange firmware downgrade unit at customer site in next Monday.
And will try to get Packets Capture Data.

Thank you very much.

P.S. I already changed WISER password. nobody can not connect WISERs to use old password in capture data.

 

Hi Yoshi,

Thanks for the packet capture. Here is what I see:

- starting at 2981, also at 2904
I see 192.168.1.7 connect to 125.30.124.159:8888 and get HTTP/1.0 400 Bad Request. This is unusual because wiser's 8888 is a c-bus XML socket, not a HTTP server so the HTTP response is being generated by something else. It appears port 8888 is being port forwarded/port mapped/intercepted to/by a web server. I would check the port settings on 125.30.124.159 (I presume this is a router in front of Wiser) and ensure 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.

 

Hi Kjayakumar,

Thank you very much for your analysis of my capture data.

As 125.30.124.159 is a global address of my customer's Router.

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.

Thank you very much.

 

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 clear that the problem was due to a web server being sent the trafic on 8888. I can't think of a probably cause other than the frontend router being configured to forward 8888 trafic to a different port. One other thing to check is whether UPnP is enabled on the frontend router, if it is, you may want to verify that it is not overlaying another service onto 8888 upon request by a device on the customer's LAN.