Of course dualies are feasible. That's all a router is after all. :)
The biggest problem with adding NIC's to a server split between subnets is
one of name resolution. You might need to put custom HOST and LMHOST files
on your workstations to point them to the appropriate IP address. Example:
hosts on the 10.1.1.0/24 network need to be able to resolve MAIL to
10.1.1.5, but hosts on the 10.1.2.0/24 network need to resolve the same
name, MAIL, to 10.1.2.5 Make sure that the first network doesn't wind up
looking for the NIC on the second network. Oh, and Win9x doesn't generally
deal well with multiple NICs, so this is an NT/2K only type of deal. Or
*nix. :)
This is not a substitution for routing between VLANS. I would not recommend
using NT 4 as a router but W2K does a decent job in a pinch. It even does
RIP v2 and OSPF. There is even a stripped down version of IGMP. Hell of an
ok P/NAT box. Just remember that a server is there to serve and there is
only so much PCI bus to go around. You don't want to run the thing out of
internal bandwidth while you are trying to shuffle I/O to the SQL or
Exchange processes. If you decide to do it, be sure to monitor your
server's performance and keep tabs on the end users experience so that you
know if things go south. All in all, it's usually cheaper in support
dollars to have a dedicated router - even if it does have a Microsoft OS.
Novel handles the name thing a bit differently than NT/2K, so if that's your
server disregard.
For information on HOST and LMHOST files, see the documentation in the
sample files on your server. Remember that you can preload part of the
LMHOST file using the #PRE tag and #DOM is for your domain controllers.
Now, after I go and say all that let us all gather round and face the facts:
This is a Cisco type email list. There IS a Cisco answer.
TTFN,
Bill 'layer 4 and up is for end users' Pearch, Anchorage AK
-----Original Message-----
From: Sammi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 7:35 AM
To: [EMAIL PROTECTED]
Subject: Re: VLAN's and Routers [7:2534]
Are dual NIC's feasible? Seems on the surface to be cheaper and more
straightforward but haven't seen it mentioned so I may be missing
something.
I can actually give each department their own server but accessing the
email server would present problems.
On 1 May 2001 10:47:35 -0400, [EMAIL PROTECTED] ("Curtis Call")
wrote:
>You could buy a special NIC card for your server that can handle ISL
>encapsulated frames. It might be cheaper to buy a router though since I
>don't think the lower end switches support ISL anyway.
>
>At 12:25 PM 4/30/01, you wrote:
>>Thanks all, that clarifies somewhat.
>>
>>On 30 Apr 2001 14:06:09 -0400, [EMAIL PROTECTED] ("Karen E Young")
>>wrote:
>>
>> > Usually there needs to be some form of communication
>> >between VLANS though, so practically speaking you do need a router.
>>
>>What I would like to do is create broadcast domains for different
>>departments, ie finance, admin. But all departments would need to
>>communicate with the same server(s).
>>I'd like to implement VLAN's without the expense of having to purchase
>>routers, but doesn't seem like it's feasible?
>>
>>I have ordered P. Openheimer's (sp) Top Down Design book and that may
>>better guide me in trying to implement an efficient network design.
>>FAQ, list archives, and subscription info:
>>http://www.groupstudy.com/list/cisco.html
>>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=2858&t=2534
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
