2003 as a router

This topic contains 4 replies, has 4 voices, and was last updated by Avatar fcasco 13 years ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Avatar
    tonyyeb
    Member
    #116248

    Hi all

    We want to make a VLAN on our network but we dont have the right switching gear and have no money to buy it. But we do have a spare 2003 server with two network cards in. This was suggested to use as a ‘cheap’ solution to fragmenting our network. This is only going to be a test just to see if we can cut down broadcast traffic.

    Do we use RRAS? How should it be setup?

    LAN1 is 192.168.0.0 / 255.255.248.0

    LAN2 will be 192.168.10.0 / 255.255.248.0

    We will need to run DHCP on this server for the second LAN as well I guess. Is this correct? How do we stop it responding to the wrong network?

    Cheers guys – we are all new here to this sort of thing.

    #277305

    Re: 2003 as a router

    Hi,

    I’ve done this in a lab (I’m a student) but we used Suse Linux. Fairly easy to use (very good GUI interface), free and it has a good documentation.
    Just a thought…
    Regards,

    Avatar
    fcasco
    Member
    #285342

    Re: 2003 as a router

    You can do it by creating differente scopes one for each subnet.
    For example Scope 1: 192.168.0.1 to 192.168.0.254 will go out the corresponding nic with say an ip 192.168.0.1
    Scope 2: 192.168.10.1 to 192.168.10.254 will go out the corresponding nic with say an ip 192.168.10.1
    The dhcp will give te proper ip for the proper nic.
    Hope it helped.

    #284593

    Re: 2003 as a router

    I propose, instead of using 2,3 or more physical NIC use winnows LOOPBACK adapters (logical NIC). Install as much loopback adapters as you need and configure them in different subnets. Configure windows 2k3 as Router (install routing and remote access).

    Try Googleing for Loopback, and Routing and remote access.

    Avatar
    tonyyeb
    Member
    #223388

    Re: 2003 as a router

    fcasco wrote:
    You can do it by creating differente scopes one for each subnet.
    For example Scope 1: 192.168.0.1 to 192.168.0.254 will go out the corresponding nic with say an ip 192.168.0.1
    Scope 2: 192.168.10.1 to 192.168.10.254 will go out the corresponding nic with say an ip 192.168.10.1
    The dhcp will give te proper ip for the proper nic.
    Hope it helped.

    Thanks for that. I thought that is how it may work.

    Thanks again everyone. Anymore info, experiences, pitfalls etc…!

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.