sedberg1
asked on
Firewall setup for file and print sharing
I have a program that stores data in a folder on its C drive. This is a Windows 7 machine. The folder is shared out. There is also a networked blotter printer that is used just for printing out the files in this share. The printer is shared out on the Windows 7 machine as well. This would be network A.
There are two remote networks, say B and C, that need to connect to this file share. Each network has a Windows-Explorer like program that accesses the file share and opens up these files, which are all proprietary file formats. Inside the network which contains the Windows 7 machine, there's no problem.
I need to set up these networks so that the users on the remote network will be able to access the file share on the Windows 7 machine. I have a decent understanding of routers, so I know I need to open up the WAN port on the network A router and set up forwarding so traffic is directed to the static of the Windows 7 machine. We still have a few public IPs available to us in our ISP-assigned range, so I'm going to dedicate an IP just for this traffic. Plus, I'm going to set up the firewall rules so only the IPs associated with network B and C are allowed to access the IP on the network A router.
What I would like to know is what port to actually open. Since there's a printer involved, the setup would have to allow users on network B and C to print to this printer. They are all near each other (neighbor buildings), so someone might print to this printer and come by to pick it up.
There are two remote networks, say B and C, that need to connect to this file share. Each network has a Windows-Explorer like program that accesses the file share and opens up these files, which are all proprietary file formats. Inside the network which contains the Windows 7 machine, there's no problem.
I need to set up these networks so that the users on the remote network will be able to access the file share on the Windows 7 machine. I have a decent understanding of routers, so I know I need to open up the WAN port on the network A router and set up forwarding so traffic is directed to the static of the Windows 7 machine. We still have a few public IPs available to us in our ISP-assigned range, so I'm going to dedicate an IP just for this traffic. Plus, I'm going to set up the firewall rules so only the IPs associated with network B and C are allowed to access the IP on the network A router.
What I would like to know is what port to actually open. Since there's a printer involved, the setup would have to allow users on network B and C to print to this printer. They are all near each other (neighbor buildings), so someone might print to this printer and come by to pick it up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The problem is that opening up NetBios ports on your firewall is definitely not a good idea.
A VPN is the best solution.
A VPN is the best solution.
ASKER
With the VPN, this is what I'm thinking then...
site-to-site between network A to B and C. The VPN is site-to-site so, the whole network would be trusted on the B and C site but route traffic to only allow access to the Windows 7 machine. Also allow traffic to the printer. Since it's a trusted network, there would be no need to open any particular port. However, I do not want users from A to get to B and C. Only the one way from B and C to A. Is that one-way type of VPN possible?
site-to-site between network A to B and C. The VPN is site-to-site so, the whole network would be trusted on the B and C site but route traffic to only allow access to the Windows 7 machine. Also allow traffic to the printer. Since it's a trusted network, there would be no need to open any particular port. However, I do not want users from A to get to B and C. Only the one way from B and C to A. Is that one-way type of VPN possible?
You can set up security rules in the firewall to determine who can access what.
ASKER
So this is how we are going to do it:
1. Set up site-to-site VPNs from network A to network B and then network A to network C.
2. Create static IP addresses for the workstations of users who need access
3. Set up address objects on the firewalls of the users' workstations
4. After verifying the site-to-site is running, create the routes to only allow the address objects access.
5. Create accounts for users to access the file share.
6. Map a drive on the users' workstation in B and C using a login script.
7. Since the users on B and C would be in different domains, rather than have them be constantly prompted to log into the file share, put the login credentials on the login script.
That was it. Thanks for your help!
1. Set up site-to-site VPNs from network A to network B and then network A to network C.
2. Create static IP addresses for the workstations of users who need access
3. Set up address objects on the firewalls of the users' workstations
4. After verifying the site-to-site is running, create the routes to only allow the address objects access.
5. Create accounts for users to access the file share.
6. Map a drive on the users' workstation in B and C using a login script.
7. Since the users on B and C would be in different domains, rather than have them be constantly prompted to log into the file share, put the login credentials on the login script.
That was it. Thanks for your help!
The VPN is the correct solution. The police dept rules would preclude most any other solution as not secure. Sedberg's plan posted 3/10 looks good.
ASKER