Best practice for establishing a QNTC path

I am looking for a better solution or a preferred best practice for
establishing a QNTC path from our IBM i to a Windows File Share, each being
on a different LAN subnet?



*Current Problem*

Our IBM i resides on a 192.168.0.0/24 subnet. Our new Windows File Server
is on a 10.0.0.0/23 subnet. Both can ping and talk to each other. There
are no firewalls between, just routing/networking. As I understand, QNTC
will broadcast out to dynamically find its Network Neighbors (via network
broadcast). However, with the new 10.0.0.0 subnets, the Dynamic Discovery
broadcasts do not make it to the new servers due to the broadcast domain.



If we manually create the QNTC path using MKDIR DIR(‘/QNTC/server’),
everything works as it should (stream files, copies, etc.). However when
the system IPLs, manually created QNTC paths are wiped out; thus the need
to be recreated.



*Possible Solutions*

1) Create a CL script that runs MKDIR DIR(‘/QNTC/server’) for each
remote file server as part of the startup IPL sequence.



2) Modify each CL/RPG program to check/create the link each time:
MKDIR DIR(‘/QNTC/server’)
MONMSG CPFA0A0 /* Ignore if object already exists */



Are there any other methods or preferred best practices?



-JA-