Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 1 subscriber
  • Views 4023 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HTTPS error - Mismatch Hyper-V IP and host IP for WebAdmin

ShadowHunter
Hello, 

I’m trying to resolve a minor annoyance with WebAdmin accessed in local network. 

[LIST=1]
  • UTM runs in Hyper-V and WebAdmin is accessed via 192.168.1.110:4444
  • Hyper-V runs on Server 2012R2 on 192.168.1.115 (name: server_1)
[/LIST]

When I download the webAdmin certificate and install it on the PC from where I access WebAdmin I receive the warning that I’m trying to access 192.168.1.110 but that the server identifies itself as “server_1”, I already issued certificate via Remote Access on IP but obviously this was not working...

How should I resolve this? Any thoughts are most welcome.

Thank you [:D]

ShadowHunter


This thread was automatically locked due to age.
Parents
  • 0
    With DynDNS, you can have a free hostname that is resolvable in public DNS, and that's what you should do.  Visit FreeDNS and generate an FQDN like utm.familyname.twilightparadox.com, and then follow the Zeroeth Rule.  Also, you will be happier if you put your modem into bridge mode so that you can have your public IP on the External interface of the UTM.

    Cheers - Bob
Reply
  • 0
    With DynDNS, you can have a free hostname that is resolvable in public DNS, and that's what you should do.  Visit FreeDNS and generate an FQDN like utm.familyname.twilightparadox.com, and then follow the Zeroeth Rule.  Also, you will be happier if you put your modem into bridge mode so that you can have your public IP on the External interface of the UTM.

    Cheers - Bob
Children
No Data