Discussion Locked

Joining two networks

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have two distinct networks sharing a fast fibre backbone through Cisco Catalysts and 3Com hubs. They both use private addressing, one is 10.0.0.0 and the other 192.168.1.0. They are currently separated by Vlans on the switches. I want to run a database that users on both legs can use, but maintain the separation for security and resilience. If the database is on a Win2k box running SQL Server 2000, what is the best way to do this? The 10.0.0.0 network runs on Small Business Server 4.5 (singleserver with no trusts allowed by SBS) and the 192 side on NT4 SP6a (five machines). What is the best way to glue in the new database server? Can you offer wisdom to a keen but under-trained netman please?

11 replies

by nettek

You have a complex issue. You have two VLans: 10.0.0.0 and 192.168.1.0. A VLan is basically a switch that allows you to have two or more distinct logical LANs on the same physical network segment. In order to share a resources between VLans, which is what you want to do, you need to route traffic between your two VLans. You could purchase a standard router, or you could configure an NT server with two NICs, allow IP forwarding, and attach one NIC to each of your VLans.

Your problem, it seems, is that you state "no trusts allowed". The SQL database will have to reside on one of your two domains. If you would like nodes of one domain to access the database server on the other domain, you will need to set up a trust.

by tercos

On a test rig two nics did the trick, both networks seeing files on the link server. I can not set up trusts as SBS does not allow these, but do I need one? Perhaps not, unless SQL Server makes it impossible otherwise. Thanks, NetTek.

by timwalsh

I won't get into the harware side of the issue.

On the software side, "in a perfect world," setting up trust relationships between the 2 domains would be the way to go. However, as SBS doesn't allow trusts, your only choice is going to be to setup user accounts for all users (from both domains) who need access to SQL server on the domain that hosts SQL.

by tercos

Thanks, Tim. I don't have SQL Server set up yet but at least I can see files. I may need to set some gateways on clients to complete the deal but perhaps I'm getting there, with your help (and others).

by dieter.huerten

Hi there!

Why not giving the W2k-Box a second IP on the existing NIC (make sure there is NO ip-forwarding -- don't know at the moment how to justify);
make sure that SQL-Server is listening to every assigned nic;
try to ping the W2k-Box from within every VLAN;
try to reach the SQL-Server from each client.

I'm not sure if it would work, but that's the way I'd try to solve the problem ;-)

best greetings from
Solingen/Germany

by tercos

Not too happy with this idea, much preffering a tried and tested method, but thank you for your offer.

by meganetcomputers

You could always set up your network the way microsoft generally recommends. You can put all the servers and other resources you wish to share into a new domain called something like resource.domain.com then when you want to connect to this domain you can create a one way trust for both of the domains you will want to use. You will need to get a router of some sort before you link the vlans to the new domain. With this configuration I believe you may have some success. If I can be of any further assistance please contact me.

by meganetcomputers

or you could also do as the previous person said and place to nics in the server that you wish each domain to have access to and give the NIC an IP that belongs to each vlan. This would be the cheapest way to go.

This discussion is closed to new replies.