Announcement

Collapse
No announcement yet.

Hyper-V & MyHS & Wrong IP

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Hyper-V & MyHS & Wrong IP

    I am using MyHS on my phone and tablet to interact with HS3. The problem I am having is that when my device is on the local WiFi network, MyHS3 picks up the IP address of the Hyper-V's virtual network card instead of the IP address of my HS3 computer. How can I make MyHS pick up the correct IP address?

    How does MyHS actually figure out the IP address? I thought it's something like a dynamic IP service where HS3 sends the public IP to the MyHS service. Then when the MyHS app is started, it contacts the MyHS service to get the public IP. The router then forwards traffic to the HS3 computer (assuming port forwarding has been setup). Maybe MyHS can somehow sense that it is local, avoids contacting the MyHS service but then for whatever reason picks up the wrong network card?

    #2
    I had some issues with another program in a Hyper-V VM. The solution there was to 'bridge' the hyper-v connector with the physical card in the host machine.
    You can bridge it and if it doesn't work just un-bridge it!
    Last edited by IanIreland; June 9, 2018, 12:34 AM. Reason: typo

    Comment


      #3
      Originally posted by mulu View Post
      How does MyHS actually figure out the IP address?
      What does https://find.homeseer.com show for your HS3 local IP address?
      My assumption is that the MyHS redirect to local address is using that information. When the MyHS server realizes that the connecting computer has the same outward facing address as the target HS3 server, MyHS server redirects to the local IP address reported thru the find.homeseer.com service.

      The router then forwards traffic to the HS3 computer (assuming port forwarding has been setup).
      MyHS doesn't require port forwarding so it can't be counting on that. The redirect is by the HomeSeer server, so it has to have knowledge of your internal LAN.

      Interesting side note: starting on the MyHS web login page, if I click 'Manage Account' then 'Access System' on the next page, the connection goes thru the https://connected.homeseer.com proxy even when local. The redirect to local doesn't happen.

      Comment


        #4
        zwolfpack, thanks for the explanation. I suspected that might be happening because from outside you don't see the IP addresses of the network card in my HS3 computer. I tried https://find.homeseer.com and it reports 192.168.56.1:8080 The 56 is actually the virtual network card.

        I bridged the virtual network card and the physical network card as IanIreland suggested. However, then things got even stranger. I did set the bridge to a fixed IP because that is what I had with the physical card (and other components rely on that IP). Then when I did go to https://find.homeseer.com a new address 192.168.1.16:8080 showed up. My static IP is not 1.16 and there is no other device that has that IP so I have no idea where that is coming from. Btw, the MyHS app picks up that exact same wrong IP. So at this point I still have the same issue.

        Comment


          #5
          That is strange, the local IP address shown on find.homeseer comes directly from the HS3 application. It should be the same one displayed on the HS3 help page.

          HS3 updates find.homeseer every 5 minutes with a URL like this:

          Code:
          https://find.homeseer.com/findhomeseer/default.aspx?machine=[hostname]&localip=[LANaddr]8&port=80&srcip=[WANaddr]
          This remains in the search results for 10 minutes.

          Comment


            #6
            Ok, it becomes stranger. When I click on "Web Interface" on the HS3 dialog box it brings me to 192.168.1.200:8080 which is the static IP of my HS3 computer. However, when I go to the help page it shows 192.168.56.1. Any idea where that discrepancy could come from?
            Attached Files

            Comment


              #7
              I'm having a hard time following your setup.

              What does ipconfig on the HS3 machine show?

              Comment


                #8
                ipconfig shows 192.168.1.200 for the physical network card and 192.168.56.1 for the virtual network card. Please see the attachment. So when I go on the HS3 web interface I am on 192.168.1.200. However, the help page shows 192.168.56.1 and that is what HSTouch apparently picks up. So the question is, why does the web interface go to one IP address but in the help page it shows a different IP.
                Attached Files

                Comment


                  #9
                  I see that its been up for 5 days. If you restart is it the same each time? Perhaps one of the two addresses is only set at startup and the other is dynamic...? Just a WAG.

                  Comment


                    #10
                    Yes, right after my last post I actually restarted HS3 (I didn't reboot the computer yet) to check on that and it was still the same mismatch. Before my last post I also did an ipconfig /flushdns just in case there are some outdated lookups.

                    Comment


                      #11
                      Since ipconfig shows two interfaces, I'd think that the web interface would be available over either?

                      Couple other ideas
                      1) On the Setup-> Labs tab, make sure "Bind Server to IP Address" is set to "No Binding"
                      2) On that same page, what happens if you disable "Use find.homeseer.com to find your HomeSeer system". Make sure you wait 10 minutes for the entries to clear out.
                      3) In cmd window, what does "route print -4" show?

                      Comment


                        #12
                        1) I set "Bind Server to IP Address" to "No Binding". Now when I click on "Web Interface" on the HS3Pro dialog it directs me to 192.168.56.1, i.e. my virtual network adapter. The web page is displayed correctly. Before it wouldn't pull up. Note that I also rebooted the computer. MyHS also tried to connect to 192.168.56.1 but fails. It simply shows a black screen with the screen resolution number in the top left. This happens even after shutting down HSTouch on my Android and deleting the data from the app settings.

                        2) When I disable "Use find.homeseer.com to find your HomeSeer system" and wait at least 10 minutes and then go to find.homeseer.com I get 192.168.56.1:8080, i.e. the IP of the virtual network card.

                        3) Attached is what the route command shows.

                        I also attached a screenshot of the help page. Now both the URL of the web page and the IP address listed on the help page point to 192.168.56.1 (the virtual network card). While it works, it's still strange that it gets the IP of the virtual network card (which I used by the VM and HS3 is NOT on the VM). However, HSTouch can't connect to 192.168.56.1.
                        Attached Files

                        Comment


                          #13
                          Re. HSTouch, make sure the firewall on the host has port 10200 opened.

                          Not what I expected when disabling find.homeseer. I haven't tried it but presumably the result of the disable would be to remove all the entries. Reason I suggested trying that was to see if removing the find.homeseer entry might force the MyHS connection to go thru the connected.homeseer.com proxy instead of redirecting to the local IP.

                          Comment

                          Working...
                          X