win2k with 2 nics in dns

[Mark]

I have a win2k member server with two nics attach to two differnet subnets.
I would like to have the computers on one subnet access that server though
that nic that is on their side of the network. Is this possible? Do I have
to change anything in dns for this to happen?

Thanks for your help,
Mark

 

[Steven L Umbach]

It should work since by default when a W2K computer access dns to find a domain
computer and it finds more than one IP address for that computer, it will use the one
on it's subnet. This is explained in the link below. --- Steve

http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prjj_ipa_vitx.asp
http://tinyurl.com/ypw62 -- same link as above,shorter.

 

[Phillip Windell]

I have a win2k member server with two nics attach to two differnet subnets.
I would like to have the computers on one subnet access that server though
that nic that is on their side of the network. Is this possible?

Yes.
Just don't give the machine two Default Gateways. Only one NIC may have one,
the other must remain blank.

Do I have to change anything in dns for this to happen?

No, but they will always go to whatever IP# the machine's name resolves to
even if they "came in" though the second nic. If you don't want that then
you need two DNS server so the "other" clients can use the "other" DNS
Server the resolve the machine to the "other" address. Personally, I
consider it pointless to worry about and would never place two nics in a
machine for this purpose and would only add a second nic if
that machine was going to be used as a Router or Firewall.

I would just have a normal router between the subnets and the Server would
have only one nic and would live in the subnet I thought was best for the
purpose. The users opposite the server would simply come accross the router
like they are supposed to do and access the server by its "one-and-only" nic
& IP#. The router can control access via ACLs, ....

 

[Phillip Windell]

I tried to read that article, but it turned into "blah blah blah, blah blah"
after a while and my eyes glazed over. Sorry ,...some of those writers
need to be a bit less dry. Anyway, I was not aware it worked that way, in
that, the clients would go with the IP# that matched their subnet,...but I'm
glad it does. But is does seem like a hassle to have to rig up the DNS that
way when just normal "every-day" routing would handle that fine and the
server would only need one nic and live in one subnet.

 

[Steven L Umbach]

I agree and your suggestion makes a lot of sense. I guess Mark will have to figure
out what will work best for him. My head hurts after reading some of the
documentation, but after a while I learn to kinds speed read through them unless I am
totally clueless [which is more than not some days]. --- Steve

I tried to read that article, but it turned into "blah blah blah, blah blah"
after a while and my eyes glazed over. Sorry ,...some of those writers
need to be a bit less dry. Anyway, I was not aware it worked that way, in
that, the clients would go with the IP# that matched their subnet,...but I'm
glad it does. But is does seem like a hassle to have to rig up the DNS that
way when just normal "every-day" routing would handle that fine and the
server would only need one nic and live in one subnet.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

It should work since by default when a W2K computer access dns to find a domain
computer and it finds more than one IP address for that computer, it will use the one
on it's subnet. This is explained in the link below. --- Steve

http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prjj_ipa_vitx.asp

http://tinyurl.com/ypw62 -- same link as above,shorter.