connection two building to share resources

By shortstuff ·
Hi guys, I support a local trust that wants to share resources ( files & outlook calender if possible and mail each other directly )
Currently both offices are in the same block but seperated by 2-3 shops covering a distance of about 30 ft.
Both have independant ISP's and their own peer to peer network, due manly to the fact that as a trust there interests have grown and changed.
Running a cable between the two isnt a problem, and had there been only 1 ISP things would be easier, but because both are on the edge of the server range ( according to both ISP's) the bandwidth is limited and just using one ISP might stretch resources too much.
So I'm after suggestions as the easiest, most cost effective way of linking the two together and sharing the items mentioned above.
As a charity cost is always a factor.
Id guess some sort of server would be needed but I dont have a great deal of experience in server technology.
I'm wiling to put the time in to learn if need be. Any guidence on 'hands on' books/guides would be appreciated also.
many thanks in advance,

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -


by jck In reply to connection two building t ...

I would say your cheapest way out would be to get two securable, wireless routers, link them.

Collapse -

2 distinct questions

by Churdoo In reply to connection two building t ...

I believe you're asking 2 distinct questions here:
1. Connectivity between the sites
2. Server solution for sharing files and email resources

1. Since you say you can pull cable between the buildings no problem , then go ahead and pull either CAT5e/6 or Fiber between the buildings and terminate in the distro area of each building. Even a lot of SOHO grade router appliances can add static routes, so if Building #1 is for example and Building #2 is, you can add a static route in each of the router appliances to route to the other building. Each building will use its default gateway to route its internet traffic through its own ISP connection, but IP traffic destined to the other building will be routed through the uplink between the buildings based on these static routes.

2. For a network resource sharing solution, you haven't provided nearly enough information: number of users, budget, desired functionality, etc. but one possible solution for you to check into may be MS Small Business Server.

Collapse -


by shortstuff In reply to 2 distinct questions

currently they both use ip adddress ranges etc .. to if I set the second static route to would that work the same??
as for the second question ( and yes is it tbh) we have 14 users in one building and 8 in the other ... as for budget they havent given me that yet, tbh they never do its usually a case of 'how cheap ...' etc
static routes would enable me to share files etc but would i need server technology to share the mail and/or outlook features such as calander ??
your input is much appreciated tho, many thanks

Collapse -

Separate networks

by Churdoo In reply to thanks

Yes you want each building LAN to be different, so you'll want to re-IP at least one of the buildings. So if you leave one of your buildings, building A =, you can make building B = for example. Then yes, your building A router will need to contain a static route for the network and your building B router will need to contain a static route for the network. Actual router capabilities and HOWTO depend on your specific router models of course.

Note: I could have used above but there are other reasons to stay away from that network, and consider getting off of the network as well, though I left that one alone in this example for the sake of simplicity.

These static routes will allow you to pass IP traffic from one building to the other, through the new cable run -- what that IP is carrying doesn't matter: files, email, etc. IP doesn't care.

I can't really comment much about the server technology as there's not enough info. SBS can easily handle the number of users that your talking about but there are some other factors to consider. Suggest you solve the IP issue first and then work on the server technology.

Collapse -

much appreciated

by shortstuff In reply to Separate networks

thanks for the input Churdoo, I really appreciate your input on this, most of my knowledge ( tho resonable ) is self taught ( one of the reasons I asked if anyone knew of good hands on tutorials. )
I'll do as you suggest and get the 2 buildings connected first, but just out of curiosity whas the advantages of using the addressing scheme, if its better and wont affect the network I can alter the settings while Im changing things around. I assume it wont affect the networked printer once ive due to dhcp info on the routers ..

Collapse - and

by Churdoo In reply to much appreciated

The reason that I try to stay away from these networks at a business is because many off the shelf home and soho routers default to these networks. This being the case, if you ever get to the point where you'll have home users trying to VPN into your network, those that are on these networks will have a problem with their VPN's, so I just like to keep the business off of these common networks and avoid the issue altogether.

Related Discussions

Related Forums