Switching by one managed switch several independent networks. Where is the mistake?

Question

Computer networks

There is a managed switch HP1910 24 POE.
It needs to make three independent networks
1-16.25 the first network
17-22.26 the second network
23.24 the third network
Changed VLAN0001 with number 1. it was untagged from 1 to 26, it became untagged from 1 to 16 and 25
. with number 2. added untagged from 17 to 22 and 26.
Created VLAN0003 with number 3. added untagged from 23 to 24.
Only VLAN0001 had an ip address set to access the switch.
VLAN0001 and VLAN0002 are two independent networks with their own dhcp on the DVR, but with the same network number 192.168.78.0/24
a network from one DVR comes to port 25, if you connect a PC to one of the first 16 ports, then the PC settings are received via DHCP from the DVR immediately without problems and hitches.
a network from another DVR comes to port 26, if you connect a PC to one of the ports from 17 to 22, then the PC does not receive settings. When manually setting the settings, the network also does not work.
Where is the mistake?

Answer 1

Absolutely similarly configured HP and Cisco managed switches + tagged ports for communication between switches - no problems.
First, find out if the problem is in the VLANs or in the settings of the computer and the DVR. Connect them instead of a managed one, to some simple separate switch.

Answer 2

I don’t know how to do this specifically on your switch, but usually on managed switches you can view the table of poppies by ports or vlans.
For example, show fdb port(vlan)... on D-Link or show mac-address-table int(vlan)... on Cisco. Something similar should be on HP (maybe even in the web interface).
It is worth looking to see if there are poppies on the ports of interest, in those vlans - this is where diagnostics begin.

Answer 3

Connect the computer to the required wealan, sniff the packets and see what flies / does not fly there. Maybe the problem is not in the Wealans, but in the ACL