Hi @guyd2 

Thanks for posting in our business forum.

Give this a try?

What If My Windows Computer Is Not Accessible or Pingable Over the VPN/VLAN Interface

What you described gives me a feelings that this has nothing to do with the router/switch.

When you have devices like a server, you always have options to declare the access authority for different users and IPs.

Hi @guyd2 

Thanks for posting in our business forum.

guyd2 wrote

  @Clive_A 

 

Thank you for replying.

I didn't fully understand what you suggest me to do.

Beside, I tool another PC, Windows 11, connected to it to the same LAN port ( in case there are some limitation on that port), and both problems remain.

 

Guy

I mean, basically, in your network, you are deploying some kind of server. Right?

If you deploy the servers, the servers have rules and firewalls. The machine to host the servers itself will also have a firewall.

Have you ruled out that the server instance itself does not exclude the connections from the other subnets?

You said yourself that you can access the broker in the same subnet.

WDcloud, not sure what that is, but should be implementing the same mind note of troubleshooting as the link I gave.

Since you have not ruled these out, I cannot say it is a VLAN error. What VLAN error would that be? I am quite curious if you insist on this. I am also not convinced by your test methodology that this indicates a VLAN error/failure. VLAN is actually layer 2. It integrates the routing. It should at least be something related to the routing and firewall.