Merging Two Networks

[Kent]

Everyone:

I'm looking for some advice.

My small office had (until recently) two separate networks:

1) a 35 user network running FileMaker Server 3.0 and macs and a few pcs on FileMaker Pro 3.0

2) a small 5- mac network running FileMaker Pro 3.0 with a host machine running "Multi-user" files from its own version of FileMaker Pro 3.0.

We recently combined both networks to share a high-speed internet connection (we had two different isps previously). After the conversion, the smaller network users could only access files that were opened through the FileMaker Server software on the large network server machine.

We have, at this point, put all of our files on the same server to ensure access, but we prefer to keep them separate (security is of some concern and we are hesitant to keep a system where users of one network can see files from the other), and if possible, keep the original system of hosting the small network files on a separate host machine without the need for FP Server.

Any ideas on how we can keep these two "sub networks" with only one physical network?

Thanks in advance,

Kent

[email protected]

[d94dsj]

The following reasoning assume that all Macs and PCs now use TCP/IP.

Maybe the smaller network before the migration only used AppleTalk for sharing? Then it wouldn't be surprising if you couldn't access the shared databases the same way as before.

Here is a simple test you can perform:

1. Find out what IP address the computer sharing the FMP databases have. Open the databases you want to share, in Multi-User mode. Make sure that FM is set to use TCP/IP.

2. Start FM from another of the hosts from the earlier smaller network. Make sure FM is set to use TCP/IP. Choose Open..Hosts from the menu. If no host names are shown, click "specify host" and enter the IP address from step 1. You should hopefully see the shared databases.

If this doesn't work, please supply more information.

If you really want to keep the two networks separate, you should create two subnets and block access to each others network through a firewall. A network administrator can help you set this up, together with Internet Access routing...

Good luck!

/Daniel

[Kent]

Hi Daniel, and thanks for the response.

I should give you a little bit more info before I proceed with your test.

The computers can all NOW see ALL databases as we have moved them all to the server which was on the larger network. The host from the smaller network is now just another client.

Both networks were accessing their respective host computers by tcp/ip before.

When any user now clicks on the "hosts" button, all the databases appear in the resulting dialog box. At the bottom, we have options for "Local Host" and "Specify Host." When we originally switched over, we tried inserting the IP address for the small network host in the "Specify Host" pop-up box, but the client could never find the smaller host computer.

As for separating the files, we're not too worried about access -- no one in our office has the technical savvy to open anything they can't see, nor would they try. We would just like to avoid inadvertent opening and editing of one file by a novice or new employee in the other group. Passwords would be a bother, but a simple solution, I suppose, but the ultimate solution is for our small group to see only their files when they hit the "Hosts" button, and the large group to see only their files when they hit the "Hosts" button.

What do you think?

Kent

[d94dsj]

Kent,

That is strange. Please proceed with my test - although it seems that you have already tried that, please do it again exactly as I outlined it.

If that doesn't work:

Try to ping the ip address of the computer hosting the files from the client from which you wish to access them. Do you get a reply? If so, you at least have a working TCP/IP connection between them.

Access to port 5003 must be enabled for the hosting computer to give out a list of databases - might there be any firewalls on the way preventing this?

This also means that, if you set up a firewall on the way to the server, you can configure it to block traffic to port 5003 for just the computers in the "small group", then they wouldn't see those databases!

Please let me know how you proceed!

/Daniel

[d94dsj]

quote:

---

Originally posted by CaptKurt:

Here is a simple solution.

Hide all the files, by making them open as multi-user hidden on the server. This way no one can see any files.

Now create 2 "opener" files and make them normal multi-user files. Everyone can see these two files.

Each opener is password protected and that password is only given out to those who need to access the file. Each opener then uses a startup script to open all the necessary files, thus the user get the correct files open without the need to see any body elses files.

---

Yes, that's a good way to fix the problem.

And it IS a good idea to keep all files on a real FM Server than on a regular host because of stability, performance, security, and a lot of other reasons (provided that the server is not overloaded, but I guess that is not the case since FMP Server is quite "thin").

Ideally, I would recommend local opener files, so each client wouldn't even have to go through the "Hosts" button to select the correct database.

If you don't know what an "opener" file is, there are some good posts describing them on this forum. Can't remember exactly where right now. Let me know if you can't find them if you want to know more about them.

/Daniel

[Kurt Knippel]

Here is a simple solution.

Hide all the files, by making them open as multi-user hidden on the server. This way no one can see any files.

Now create 2 "opener" files and make them normal multi-user files. Everyone can see these two files.

Each opener is password protected and that password is only given out to those who need to access the file. Each opener then uses a startup script to open all the necessary files, thus the user get the correct files open without the need to see any body elses files.

[Kent]

Thanks for the help guys.

I was sucessful in at least getting the files moved back to the original small server by playing with some ip addresses, etc. So everyone is happier. We still have the problem of people being able to open each other's files, but it's not a major one.

Thanks for the idea about opener databases... Unfortunately, inside of the large network, we have around 30 separate databases and who needs to open what database on any particular day is very complicated, often changing simply by one phone call -- so I'm hesitant to step in with such a level of control.

I suppose if it is a problem, we'll just password protect the small-network files (there are only 5 users so a minimum of disturbance is needed.)

Thanks again for the suggestions, and if you think of anything else that might help, please let me know!

Best,

Kent