Hi
Reason this is happening is that the SE has access to the VLAN that the Server is connected on.
The way to get around that is to create a Static Route that forces the connection via the new VLAN.
In essence the static route will be:
Gateway - 172.16.10.10/32 or IP range if you have more than one server.
Next Hop will be the Gateway for VLAN 10.10.10.0/24 which is possibly 10.10.10.1
This will force it to use the 10.10.10.0 IP range to connect to the servers