16
General Software Discussion / Connecting a system on one network to a 2nd network for filesharing
« on: February 14, 2020, 03:00 PM »
If this question is in the wrong place, please tell me where to move it.
I have run into a situation where i need to connect a system that runs on a single static ip and give it a 2nd iip that is part of our local main network.
Example the systems must stay active at 184.174.129.235 and i need it also be seen at 10.0.70.xxx. My first thought was to use a 2nd NIC. My 2nd thought was to use duel VPNs Servers as a bridge . The 10.0.70. network already has Softether VPN and adding the same to the 184.174.xxx.xxx network should allow for a VPN Bridge.
But I am not sure which method would best allow for shared folders on the 184.174 system to be accessed by people on the 10.0.70 network.
The dual nics do work but from everything i can read, this is not the best way to go.
All pf the systems are running normal Windows 10 x64 Home. Unfortunately,. MS has recently removed the Homegroup option from 10 Home.
The third option (which might be best) would be to move the 184.174 system inside the 10.0.70 network but it is an small Apache Web Server that i would prefer to keep on the separate static IP it runs on now. The folder access is for people that have to load and edit files on the websites. None of them are proficient enough to deal with an FTP program and need this to be a simple shared network connection if possible
I have run into a situation where i need to connect a system that runs on a single static ip and give it a 2nd iip that is part of our local main network.
Example the systems must stay active at 184.174.129.235 and i need it also be seen at 10.0.70.xxx. My first thought was to use a 2nd NIC. My 2nd thought was to use duel VPNs Servers as a bridge . The 10.0.70. network already has Softether VPN and adding the same to the 184.174.xxx.xxx network should allow for a VPN Bridge.
But I am not sure which method would best allow for shared folders on the 184.174 system to be accessed by people on the 10.0.70 network.
The dual nics do work but from everything i can read, this is not the best way to go.
All pf the systems are running normal Windows 10 x64 Home. Unfortunately,. MS has recently removed the Homegroup option from 10 Home.
The third option (which might be best) would be to move the 184.174 system inside the 10.0.70 network but it is an small Apache Web Server that i would prefer to keep on the separate static IP it runs on now. The folder access is for people that have to load and edit files on the websites. None of them are proficient enough to deal with an FTP program and need this to be a simple shared network connection if possible