Web browser issue for a web browser

Hello,

are these devices in another network segment or in the same address range?

all the machines are in the network segement 192.168.10.10 include my machine who has access

So you try to reach a system in the 192.168.200.0 /24 network from a device in the 192.168.10.0 / 24 network?

Yes, as I wrote, I can access from my machine to the 192.168.200.100, my machine has the IP 192.168.10.9

How is the network layout?

What do you mean? I am sure, there are a rule defined on the Sophos UTM 9, but where?

I mean, how are these network connected to the UTM? Are there two ports on the UTM, each connected to one network? Or is there a switch in between, are VLANs defined and used?

At best you could give us a simple diagram of your network and the IP addresses.

Sorry, tell me easy where I can search and I can add the IP address range or one IP to having access

This is kind of "wash me, but don't make me wet", sorry.

I was asking to help you, not to disturb you. Without knowing about your config, I can't give any advice.

I know what you mean, but on the UTM 9 are defined which machines can access to the HyperV web browser, my machine is included, but I cannot find the entry

OK.

[Glass ball modus=ON] On the Sophos UTM have a look at Network Protection/Firewall then "rules" and search for a rule containing your Hyper-V host. Then try to modify source and/or destination in this rule.[Glass ball modus=OFF]

There should be an object for the IP address of your Hyper-V machine, this is what you are looking for.

I'll preface by saying i've never used HyperV, but imagine it functions similarly to vmware's vmworkstation.

As such, the latter does a sort of nat function between the device's network interface and a virtual nic. This is done in part to isolate the vm to some extent from the host. Vmworkstation's network editor looks like this.

So, what I gather from the conversation is the OP is attempting to connect to the guest vm (which resides on this NATted network) using external lan clients.

It appears to facilitate this function, VM's network editor allows one to map a port forwarding function. That is inbound traffic to the host on port X gets routed to a VM on port Y.

This functionality has nothing to do with UTM or any firewall rules.  In fact, it's quite messy to say the least.

@OP, if you want to play with virtual machines, either set the guest's network to be bridged (same subnet as pc running hyperv), or use a proper level 1 hypervisor (proxmox, esxi, etc.)

GIGO!

I'll preface by saying i've never used HyperV, but imagine it functions similarly to vmware's vmworkstation.

As such, the latter does a sort of nat function between the device's network interface and a virtual nic. This is done in part to isolate the vm to some extent from the host. Vmworkstation's network editor looks like this.

So, what I gather from the conversation is the OP is attempting to connect to the guest vm (which resides on this NATted network) using external lan clients.

It appears to facilitate this function, VM's network editor allows one to map a port forwarding function. That is inbound traffic to the host on port X gets routed to a VM on port Y.

This functionality has nothing to do with UTM or any firewall rules.  In fact, it's quite messy to say the least.

@OP, if you want to play with virtual machines, either set the guest's network to be bridged (same subnet as pc running hyperv), or use a proper level 1 hypervisor (proxmox, esxi, etc.)

GIGO!