Wisenet Wave Client Fails to Connect first time
If I view my systems by going to https://sync.wavevms.com/systems and then click the "Open in Wisenet WAVE" on one of my systems, my Wisenet WAVE client app opens and tries to connect, but I get the error "Failed to connect to Server". I click OK on the error pop-up and I can see all of my systems on the Wisenet WAVE client app screen, but they're all grayed out like they're offline. I wait about 15 seconds and then they all come back on. After that I can click on the System I was trying to connect to in the first place and it connects just fine. I have to do this every time I open the client app (let it fail once, wait 15 seconds, connect again).
While this is happening I can see on my Firewall logs that my Systems are trying to contact my PC on a variety of ports in the 52000-64000 range and are being denied (which is expected since they are on different VLANs and I don't want to open a ridiculous amount of ports between them).
-
تعليق رسمي
Hi Jespersen,
Thank you for your enquiry.
Typically in most cases ports don't really need to opened but again every network environment is different in it's own way.
Have you at least tried opening ports for the Wave services like 7001, 80, 443 and 3345 to see if that makes any difference.
Also what version of Wave are you experiencing this with?
-
I do have those ports open from my computer to the internet, but not from my computer to the NVRs directly. When I run Wisenet from behind our firewall, I see my computer attempting to reach out directly to my NVRs on ports 59346, 40387, 58045, 50673, 33331, etc., all on UDP. Then I see my computer trying to reach out to my building's external IP on the same random ports, then I see the NVRs trying to reach my computer on the same random ports. They are all getting denied because I don't have a rule for these things. After that fails and I get the error message, I think Wisenet then reaches out to the internet and establishes the connection and then it works. I can see my computer reaching out to a Wisenet IP on port 3345 and it's allowed. If I have my computer at home, which doesn't have a firewall nor a direct connection to any of the NVRs, the same thing happens. So I think it's still trying to reach out to the NVRs directly by IP, and after it can't find them it then goes through the cloud. Without a firewall at home I can't verify that. It happens no matter what network I'm on. I've tried it from a hotspot with the same results. The Wisenet WAVE Client on my computer is 6.0.5.41290. This also happens to my co-worker, so it's not just my computer.
0
الرجاء تسجيل الدخول لترك تعليق.
تعليقات
2 تعليقات