How to set up Private Network on SQL 2000 EE on Windows 2003

To All Gurus:
I have a question on SQL Server 2000 Network routing Where any help is
appreciated. I would like to know if it is possible for a SQL Server to talk
to another SQL Server using a private network. What I am trying to do is I
have
transactional replcation enabled where I want to use private network
for data transfer between publisher\subscriber\distributor. I have 3
NICs on Each. One is reserved for public routing, second is for backup
routing and the third one can be on private network. How do I
architect this kind of design in my SQL Server shop.
Thanks in advance,Mark wrote:
> To All Gurus:
> I have a question on SQL Server 2000 Network routing Where any help is
> appreciated. I would like to know if it is possible for a SQL Server to ta
lk
> to another SQL Server using a private network. What I am trying to do is I
> have
> transactional replcation enabled where I want to use private network
> for data transfer between publisher\subscriber\distributor. I have 3
> NICs on Each. One is reserved for public routing, second is for backup
> routing and the third one can be on private network. How do I
> architect this kind of design in my SQL Server shop.
> Thanks in advance,
>
Hi Mark
I'm not sure that I understand what you mean about Private Network, but
nevertheless it shouldn't be a problem to do what you want. You can
access the server either via the IP address or the name, but you just
have to make sure that you have a route to the server. If they are not
on the same subnet, you'll have to have route between the networks in
your DNS.
The easiest place to start, might be to register the server(s) in EM.
When you have that in place, you can also setup the replication.
HTH
Regards
Steen|||Hi Steve:
Thanks for your response.
I am sorry if I wasn't clear on my explanation. I had few questions in my
mind:
1. If I have 3 Separate NIC Cards on my SQL Server and all of them are
publicly routed with in the LAN, would SQL Server listen to all NICs? Or do
I
have to do something special for SQL to listen to all NICs.
2. Do all these NICs have to be on different subnet or can they be on same
subnet?
3. If they are on separate subnet, what do I need to do extra?
4. I dont know how to route between the network in DNS? Can you provide some
more explanation or some white paper link for that.
Thanks in advance.
"Steen Persson (DK)" wrote:

> Mark wrote:
> Hi Mark
> I'm not sure that I understand what you mean about Private Network, but
> nevertheless it shouldn't be a problem to do what you want. You can
> access the server either via the IP address or the name, but you just
> have to make sure that you have a route to the server. If they are not
> on the same subnet, you'll have to have route between the networks in
> your DNS.
> The easiest place to start, might be to register the server(s) in EM.
> When you have that in place, you can also setup the replication.
> HTH
> Regards
> Steen
>|||Mark wrote:
> Hi Steve:
> Thanks for your response.
> I am sorry if I wasn't clear on my explanation. I had few questions in my
> mind:
> 1. If I have 3 Separate NIC Cards on my SQL Server and all of them are
> publicly routed with in the LAN, would SQL Server listen to all NICs? Or d
o I
> have to do something special for SQL to listen to all NICs.
> 2. Do all these NICs have to be on different subnet or can they be on same
> subnet?
> 3. If they are on separate subnet, what do I need to do extra?
> 4. I dont know how to route between the network in DNS? Can you provide so
me
> more explanation or some white paper link for that.
>
1. You should be able to contact the server from all 3 nic's (Have never
tried it myself though...)
2. From a SQL server point of view, they haven't got to be on the same
subnet. They'll just each of them listen to what comes to their IP
address on the specified port. It's then their IP address and subnet
together with your routing schema that determines which clients that can
"talk" to the server.
4. Here you have to talk to your network people or read up on IP
addresses/Subnetmasks and Routing. I haven't got any specific links to
that but I'm sure that a search on google will give you a lot if hits.
This isn't specific to SQL server, so for that it might be the wrong
group. A quick search on google found this one -
http://www.nwc.com/unixworld/tutorial/001.html . It might not be the
best, but it's maybe a start.
Regards
Steen
Regards