W2003, 2 XP and a problem

At http://213.237.36.247/netvaerk/eng_prob.pdf I have drawn the LAN-setup
which should be used.
The problem is the server which needs to be configurated so that it is
possible to:

* Use the LAN between the two Windows XP-computers
* Use the LAN between the server in both directions
* The Internet on the server should go through the green line marked in the
PDF-file

I have though about bridging the connections (on the server) but it doesn't
help that much as I thought...

Any ideas?

// Peter

The link doesn't work.

"peter hansen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> At http://213.237.36.247/netvaerk/eng_prob.pdf I have drawn the LAN-setup
> which should be used.
> The problem is the server which needs to be configurated so that it is
> possible to:
>
> * Use the LAN between the two Windows XP-computers
> * Use the LAN between the server in both directions
> * The Internet on the server should go through the green line marked in
the
> PDF-file
>
> I have though about bridging the connections (on the server) but it
doesn't
> help that much as I thought...
>
> Any ideas?
>
> // Peter
>
>
>

"Rob Elder, MVP-Networking" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The link doesn't work.
[CUT]

hehe... it seems like my server is pretty offline - new URL
http://www.60696867.dk/w2003/eng_prob.pdf

// Peter

"peter hansen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> At http://213.237.36.247/netvaerk/eng_prob.pdf I have drawn the LAN-setup
> which should be used.
> The problem is the server which needs to be configurated so that it is
> possible to:
>
> * Use the LAN between the two Windows XP-computers
> * Use the LAN between the server in both directions
> * The Internet on the server should go through the green line marked in
the
> PDF-file
>
> I have though about bridging the connections (on the server) but it
doesn't
> help that much as I thought...
>
> Any ideas?

Change the subnet on the one side of the server. (I'll use router 1 for
this description)
Change the default LAN configuration on router 1 to 192.168.2.1
Configure the Routing and Remote Access on the server. Using the wizard
choose custom configuration and choose LAN routing.
Edit the routing table on the server to include the following line
0.0.0.0 0.0.0.0 192.168.1.1

Suggest using static IP on your server for best results.


>
>

[CUT]

> Change the subnet on the one side of the server. (I'll use router 1 for
> this description)
> Change the default LAN configuration on router 1 to 192.168.2.1

Done that so far

> Configure the Routing and Remote Access on the server. Using the wizard
> choose custom configuration and choose LAN routing.
> Edit the routing table on the server to include the following line
> 0.0.0.0 0.0.0.0 192.168.1.1
>
> Suggest using static IP on your server for best results.

Easy now - i am not following you hehe
Could you include a step-by-step ?

// Peter

open a command prompt on your server and type the following

route add 0.0.0.0 mask 0.0.0.0 192.168.1.1


"peter hansen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> [CUT]
>
> > Change the subnet on the one side of the server. (I'll use router 1 for
> > this description)
> > Change the default LAN configuration on router 1 to 192.168.2.1
>
> Done that so far
>
> > Configure the Routing and Remote Access on the server. Using the wizard
> > choose custom configuration and choose LAN routing.
> > Edit the routing table on the server to include the following line
> > 0.0.0.0 0.0.0.0 192.168.1.1
> >
> > Suggest using static IP on your server for best results.
>
> Easy now - i am not following you hehe
> Could you include a step-by-step ?
>
> // Peter
>
>

[CUT]

> open a command prompt on your server and type the following
>
> route add 0.0.0.0 mask 0.0.0.0 192.168.1.1

[CUT]

Is that it ? I don't have to configure any kind of IP etc. on the server ?
What about IP-configration to TCP/IP for the two NIC's ?

// Peter

That's it. The RRAS service on the service will handle communications
between your two internal networks. The modification to the routing table
will make that all requests for networks not in your table (connections to
the outside) will be passed through the 192.168.1.1 gateway.

"peter hansen" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> [CUT]
>
> > open a command prompt on your server and type the following
> >
> > route add 0.0.0.0 mask 0.0.0.0 192.168.1.1
>
> [CUT]
>
> Is that it ? I don't have to configure any kind of IP etc. on the server ?
> What about IP-configration to TCP/IP for the two NIC's ?
>
> // Peter
>
>

"Rob Elder, MVP-Networking" <(E-Mail Removed)> wrote in message
news:eOhX$(E-Mail Removed)...
> That's it. The RRAS service on the service will handle communications
> between your two internal networks. The modification to the routing table
> will make that all requests for networks not in your table (connections to
> the outside) will be passed through the 192.168.1.1 gateway.

But I have to run the route add 0.0.0.0 mask 0.0.0.0 192.168.1.1 everytime i
restart my server eah?...
anyway it doesn't work
The IP on both NIC's TCP/IP should be set as Obtain Automatic IP?

// Peter

"peter hansen" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
>
> "Rob Elder, MVP-Networking" <(E-Mail Removed)> wrote in message
> news:eOhX$(E-Mail Removed)...
> > That's it. The RRAS service on the service will handle communications
> > between your two internal networks. The modification to the routing
table
> > will make that all requests for networks not in your table (connections
to
> > the outside) will be passed through the 192.168.1.1 gateway.
>
> But I have to run the route add 0.0.0.0 mask 0.0.0.0 192.168.1.1 everytime
i
> restart my server eah?...
> anyway it doesn't work
> The IP on both NIC's TCP/IP should be set as Obtain Automatic IP?
>
> // Peter
>
>