Cant access ServerB from VM ServerA on same LAN

[moosport]

Trunas VM in Vmware can't access Trunas serverB connected to switch on the same LAN. Both are on 192.168.1.xxx IPs.

1. Vmware server is connected to switch with VLAN 20,40,50,60 tagged. Allowing both tag and untag. Default vlan 1. Vmware port group vlan id 4095.
2. pfsense connected to switch with VLAN 20,40,50,60 tagged. Allowing both tag and untag. Default vlan 1.
3. ServerB is connected to switch with no tag VLANs.
4. Ping from VM to ServerB do not work. But Trunas VM can list folders on ServerB when configuring replication. Replication job fail on network timed out.
5. Pfsense can ping ServerB.

PC connected WAP or wired has no issue access any servers on LAN.

There are other equipment connected to the switch and has no access issue. what could be the issue?

[SteveITS]

@moosport traffic on the same network doesn’t go through the router, so check the switch, VM virtual switch, etc.

[chpalmer]

@moosport said in Cant access ServerB from VM ServerA on same LAN:

Vmware server is connected to switch with VLAN 20,40,50,60 tagged. Allowing both tag and untag.

I don't play allot with tags on my VLANs but I do believe that just because you allow ServerA to see untagged does not mean that it will default transmit to it..

If you share more information on how your tagging is set up such as LAN subnets then it might be more obvious.

But if VLAN 20 is 10.10.10.0/24 and untagged is 172.16.1.0/24 then yes that traffic would pass through the router and need to be routed back.. but I may be way off there.

As Steve said though traffic on 10.10.10.0/24 (my example above) will not pass through the firewall and is simply a function of the switch to direct that traffic between clients on that VLAN.

Simply an If/Then problem solution. If desired address is inside my subnet then go thataway. If the traffic is outside my subnet then go to the gateway (router) for direction.

[moosport]

Not sure if the pfsense DHCP is cause of some issue. routing definitely not going through pfsense.

1. switch port 25 and 26 are connected to VMWare server.
2. switch port 27 is connected to ServerB.
3. switch port 28 is trunk to pfsense.