I have two separate networks I would like to join to a single Server 2012R2. One network has a router attached to a T1 line which has a fixed public IP address. This keeps an open FTP line to upload weather station data and webcam photos to several websites. The fixed IP is needed to keep the FTP open at all times. Presently this network is not connected to any storage server, but I would like to connect it to the 2012R2 Server as it has 15 TB of storage. (It was at one time) The data collecting devices are Raspberry Pi's and there are two PCs used to set up and maintain the RPi's. These have limited storage.The router on this network is the gateway and DNS.
The Server 2012R2 has multiple PC's connected to it and a separate Router that has no fixed public IP but does have a hi speed broadband connection. This network is a named domain. The router is the gateway and the Server is of course the DNS. The Server has two NICs, so I thought I might connect the other network to it so that the Server 2012R2 could act as a NAS and provide redundant data storage for the Raspberry Pi's. This would also allow access to the data from both networks. I have no need for these two networks to see each other (although it might prove useful). At one point everything had been on a single network,-the T1, so the address space is the same: 10.0.2.XXX on subnet 255.255.255.0
In my simple brain, I thought I would just configure the 2nd NIC on the Server to a separate subnet, like 255.255.0.0 or setup the two routers to separate IPV4 address spaces. DHCP is handled by each of the two Routers, but of course Server 2012R2 wants/needs to be the DNS Server. There is no need to provide a redundant internet connection. The Server is quite happy with it's broadband connection for cloud backup.
Would either of these approaches work?