Losing access to SMB/CIFS Share when Jail active

[notmyUsername]

Hi, I'm struggling with my set-up and need some help.

Config Summary
- Nas4Free IP: 192.168.10.200
- SlimNAS Jail IP: 192.168.10.201
- CIFS/SMB NetBIOS name: H
- SlimNAS Hostname: SlimNAS (as configured in TheBrig GUI and confirmed with jexec {jailnumber} hostname)

Problem
When the Jail is running I lose access to my CIFS/SMB shares when accessing them by hostname name from a Windows box, e.g. \\H\DML results in the generic "Network Error" Windows cannot access \\h\DML message.
If I ping my CIFS/SMB server "H" I get a response 192.168.10.201, the Jail IP, not the Nas IP.
Pinging either .200 and .201 with the -a (resolve) option both return H as hostname.
If I stop and restart the CIFS/SMB service (leaving the Jail running) I can then re-access the shares - a temporary workaround, rather than fix.

I assume the problem is something to do with two IP addresses on the single machine/MAC, but I'm lost as to what to do.

If I set-up a hosts file on my Windows systems that'd workaround the problem, but I want the shares to be generally accessible, so don't want a solution that requires client configurations. I'm running this on a small home network without a dedicated DNS server, so adding a DNS entry that just resolves H to the correct IP address isn't workable at this time. Another possibility that came to mind was somehow not having the Jail IP visible on the network and somehow internally within the Nas4Free box forward port (9000) to the Jail, meaning my SlimNAS server to the outside network would be 192.168.10.200:6000, but I don't know how that'd be achievable, or if it's even a reasonable solution.

Any ideas?