Setting up Server 2003 as Router

Hi,

I am trying to set up my Server 2003 as a router to my client PC's.
I have 2 NIC's in the server. One for incoming internet and the other
going off to switch boards which my client PC's connect to,
My current network layout is:
NIC1
Modem - Router - Server NIC1
MIC2
Server NIC2 - Switch Boards - Client PC's
Is this structure correct for what i am trying to achieve.

The probem i am getting is that the server can see the interent but
none of the clients can. The NIC with the incoming interent to the
server functions correctly but the outgoing to the switch boards says
that the network cabble is unpluged.

Thanks in advance for any help.

"tuxedo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi,
>
> I am trying to set up my Server 2003 as a router to my client PC's.
> I have 2 NIC's in the server. One for incoming internet and the other
> going off to switch boards which my client PC's connect to,
> My current network layout is:
> NIC1
> Modem - Router - Server NIC1
> MIC2
> Server NIC2 - Switch Boards - Client PC's
> Is this structure correct for what i am trying to achieve.
>
> The probem i am getting is that the server can see the interent but
> none of the clients can. The NIC with the incoming interent to the
> server functions correctly but the outgoing to the switch boards says
> that the network cabble is unpluged.
>
> Thanks in advance for any help.
>

If you are getting a "network cable unplugged" message it is almost
certain to be a hardware problem. Does this cable work with another machine?
Does the switch port work with a different cable to a different machine?

If you have used these tests to check that both the switch port and the
cable are OK, it is probably a NIC problem. If it is a PCI card, check that
the card is properly seated. If nothing works, try a different NIC card.

When you solve the hardware problem, you may still have difficulty with
your setup. The machines behind the local router (ie your server) will not
be in the same IP subnet as the NIC1 of the server (which connects to the
Internet). If NIC1 gets a registered public IP you can get this to work by
configuring RRAS as a NAT router.

This is not a very good way to configure your LAN. Do you have a
particular reason for wanting to use the server as a router? (NB if the
server is a DC this is a particularly bad idea!)

"tuxedo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi,
>
> I am trying to set up my Server 2003 as a router to my client PC's.
> I have 2 NIC's in the server. One for incoming internet and the other
> going off to switch boards which my client PC's connect to,
> My current network layout is:
> NIC1
> Modem - Router - Server NIC1
> MIC2
> Server NIC2 - Switch Boards - Client PC's
> Is this structure correct for what i am trying to achieve.
>
> The probem i am getting is that the server can see the interent but
> none of the clients can. The NIC with the incoming interent to the
> server functions correctly but the outgoing to the switch boards says
> that the network cabble is unpluged.
>
> Thanks in advance for any help.
>

Hi,

Thanks for the reply,

I think that one of the main problems is that the server does not know
it is meant to be sending the interent through the 2nd NIC and is
looking for an incoming connection. I don't know how i am meant to
tell it to change this connection to outgoing. Thanks for any help

Install the Windows Server component "Routing and Remote Services" on the
server - you can then configure the server for LAN routing between interfaces.

Like Bill says, though, having a server internet facing without a decent
firewall is asking to be hacked.

"tuxedo" wrote:

> Hi,
>
> Thanks for the reply,
>
> I think that one of the main problems is that the server does not know
> it is meant to be sending the interent through the 2nd NIC and is
> looking for an incoming connection. I don't know how i am meant to
> tell it to change this connection to outgoing. Thanks for any help
>
>