Networking Forums

Networking Forums > Computer Networking > Windows Networking > Can i use Routing and Remote Access to connection two internal networks.

Reply
Thread Tools Display Modes

Can i use Routing and Remote Access to connection two internal networks.

 
 
Ian Groves
Guest
Posts: n/a

 
      02-28-2005, 12:44 PM
We need to connect 2 internal lans using our windows 2003 server, can i use
routing and remote access to do this or do i need isa server, or is setting
a network bridge the answer?

lan1:

192.168.0.*
255.255.255.0
Gateway 192.168.0.5 (ADSL Router)
dns1: 192.168.0.1 (2003 server)
dns2: 192.168.0.5 (adsl router)


lan2:

192.168.102.*
255.255.255.0
no gateway or dns set


i need clients on lan 2 to be able to access 192.168.0.1 file sharing and
the internet through 192.168.0.5, i do not need the connection to be secure
as it is all in one building.

is routing and remote access all i need?
how should i configer the clients on lan2?

Many Thanks in advance.

Ian Groves.


 
Reply With Quote
 
 
 
 
Doug Sherman [MVP]
Guest
Posts: n/a

 
      02-28-2005, 01:14 PM
Yes, you can do this with 2 NICs in the server by implementing LAN routing
in RRAS:

1. Machines on lan2 must use the server's 192.168.102.* NIC as a default
gateway.

2. The ADSL router must have a static route pointing to the server's
192.168.0.* NIC to reach the 192.168.102.* network.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Ian Groves" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We need to connect 2 internal lans using our windows 2003 server, can i

use
> routing and remote access to do this or do i need isa server, or is

setting
> a network bridge the answer?
>
> lan1:
>
> 192.168.0.*
> 255.255.255.0
> Gateway 192.168.0.5 (ADSL Router)
> dns1: 192.168.0.1 (2003 server)
> dns2: 192.168.0.5 (adsl router)
>
>
> lan2:
>
> 192.168.102.*
> 255.255.255.0
> no gateway or dns set
>
>
> i need clients on lan 2 to be able to access 192.168.0.1 file sharing and
> the internet through 192.168.0.5, i do not need the connection to be

secure
> as it is all in one building.
>
> is routing and remote access all i need?
> how should i configer the clients on lan2?
>
> Many Thanks in advance.
>
> Ian Groves.
>
>



 
Reply With Quote
 
Ian Groves
Guest
Posts: n/a

 
      02-28-2005, 01:41 PM
I have enabled routing and remote access using lan routing and set a test
machine on lan 2 as

192.168.10.2.50 and set the gateway to 192.168.102.254 (the 192.168.102.*
card in the server)

at this point i would expect to be able to ping 192.168.0.1 (server) from
the lan2 client, but i cant?

I do not need to router to be able to see the 192.168.102.* clinets, but for
the 192.168.102.* clients to be able to see the router, do i still need to
set the static route?


Thanks again.

Ian.


"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:%2323Jg$(E-Mail Removed)...
> Yes, you can do this with 2 NICs in the server by implementing LAN routing
> in RRAS:
>
> 1. Machines on lan2 must use the server's 192.168.102.* NIC as a default
> gateway.
>
> 2. The ADSL router must have a static route pointing to the server's
> 192.168.0.* NIC to reach the 192.168.102.* network.
>
> Doug Sherman
> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "Ian Groves" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> We need to connect 2 internal lans using our windows 2003 server, can i

> use
>> routing and remote access to do this or do i need isa server, or is

> setting
>> a network bridge the answer?
>>
>> lan1:
>>
>> 192.168.0.*
>> 255.255.255.0
>> Gateway 192.168.0.5 (ADSL Router)
>> dns1: 192.168.0.1 (2003 server)
>> dns2: 192.168.0.5 (adsl router)
>>
>>
>> lan2:
>>
>> 192.168.102.*
>> 255.255.255.0
>> no gateway or dns set
>>
>>
>> i need clients on lan 2 to be able to access 192.168.0.1 file sharing and
>> the internet through 192.168.0.5, i do not need the connection to be

> secure
>> as it is all in one building.
>>
>> is routing and remote access all i need?
>> how should i configer the clients on lan2?
>>
>> Many Thanks in advance.
>>
>> Ian Groves.
>>
>>

>
>



 
Reply With Quote
 
Ian Groves
Guest
Posts: n/a

 
      02-28-2005, 01:47 PM
forget the last question, did as you said and i works fine..


Thanks

Ian.

"Ian Groves" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>I have enabled routing and remote access using lan routing and set a test
>machine on lan 2 as
>
> 192.168.10.2.50 and set the gateway to 192.168.102.254 (the 192.168.102.*
> card in the server)
>
> at this point i would expect to be able to ping 192.168.0.1 (server) from
> the lan2 client, but i cant?
>
> I do not need to router to be able to see the 192.168.102.* clinets, but
> for the 192.168.102.* clients to be able to see the router, do i still
> need to set the static route?
>
>
> Thanks again.
>
> Ian.
>
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> news:%2323Jg$(E-Mail Removed)...
>> Yes, you can do this with 2 NICs in the server by implementing LAN
>> routing
>> in RRAS:
>>
>> 1. Machines on lan2 must use the server's 192.168.102.* NIC as a default
>> gateway.
>>
>> 2. The ADSL router must have a static route pointing to the server's
>> 192.168.0.* NIC to reach the 192.168.102.* network.
>>
>> Doug Sherman
>> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>>
>> "Ian Groves" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> We need to connect 2 internal lans using our windows 2003 server, can i

>> use
>>> routing and remote access to do this or do i need isa server, or is

>> setting
>>> a network bridge the answer?
>>>
>>> lan1:
>>>
>>> 192.168.0.*
>>> 255.255.255.0
>>> Gateway 192.168.0.5 (ADSL Router)
>>> dns1: 192.168.0.1 (2003 server)
>>> dns2: 192.168.0.5 (adsl router)
>>>
>>>
>>> lan2:
>>>
>>> 192.168.102.*
>>> 255.255.255.0
>>> no gateway or dns set
>>>
>>>
>>> i need clients on lan 2 to be able to access 192.168.0.1 file sharing
>>> and
>>> the internet through 192.168.0.5, i do not need the connection to be

>> secure
>>> as it is all in one building.
>>>
>>> is routing and remote access all i need?
>>> how should i configer the clients on lan2?
>>>
>>> Many Thanks in advance.
>>>
>>> Ian Groves.
>>>
>>>

>>
>>

>
>



 
Reply With Quote
 
Doug Sherman [MVP]
Guest
Posts: n/a

 
      03-01-2005, 02:22 PM
There ya go. Without the static route, your ping will reach the 192.168.0.*
network, but you will not receive the reply. The static route is necessary
in order for traffic, including ping echoes, to find its way back to the
192.168.102.* network.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Ian Groves" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> forget the last question, did as you said and i works fine..
>
>
> Thanks
>
> Ian.
>
> "Ian Groves" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> >I have enabled routing and remote access using lan routing and set a test
> >machine on lan 2 as
> >
> > 192.168.10.2.50 and set the gateway to 192.168.102.254 (the

192.168.102.*
> > card in the server)
> >
> > at this point i would expect to be able to ping 192.168.0.1 (server)

from
> > the lan2 client, but i cant?
> >
> > I do not need to router to be able to see the 192.168.102.* clinets, but
> > for the 192.168.102.* clients to be able to see the router, do i still
> > need to set the static route?
> >
> >
> > Thanks again.
> >
> > Ian.
> >
> >
> > "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
> > news:%2323Jg$(E-Mail Removed)...
> >> Yes, you can do this with 2 NICs in the server by implementing LAN
> >> routing
> >> in RRAS:
> >>
> >> 1. Machines on lan2 must use the server's 192.168.102.* NIC as a

default
> >> gateway.
> >>
> >> 2. The ADSL router must have a static route pointing to the server's
> >> 192.168.0.* NIC to reach the 192.168.102.* network.
> >>
> >> Doug Sherman
> >> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >>
> >> "Ian Groves" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>> We need to connect 2 internal lans using our windows 2003 server, can

i
> >> use
> >>> routing and remote access to do this or do i need isa server, or is
> >> setting
> >>> a network bridge the answer?
> >>>
> >>> lan1:
> >>>
> >>> 192.168.0.*
> >>> 255.255.255.0
> >>> Gateway 192.168.0.5 (ADSL Router)
> >>> dns1: 192.168.0.1 (2003 server)
> >>> dns2: 192.168.0.5 (adsl router)
> >>>
> >>>
> >>> lan2:
> >>>
> >>> 192.168.102.*
> >>> 255.255.255.0
> >>> no gateway or dns set
> >>>
> >>>
> >>> i need clients on lan 2 to be able to access 192.168.0.1 file sharing
> >>> and
> >>> the internet through 192.168.0.5, i do not need the connection to be
> >> secure
> >>> as it is all in one building.
> >>>
> >>> is routing and remote access all i need?
> >>> how should i configer the clients on lan2?
> >>>
> >>> Many Thanks in advance.
> >>>
> >>> Ian Groves.
> >>>
> >>>
> >>
> >>

> >
> >

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
routing and remote access & remote desktop connection SJMP Windows Networking 1 10-22-2008 01:55 PM
Routing multiple public IPs to multiple internal networks epid Linux Networking 0 08-03-2006 03:19 AM
No access from remote networks callmebill@gmail.com Linux Networking 2 01-29-2005 08:06 AM
Remote Access Policies error in Routing & Remote Access Mark Windows Networking 1 06-28-2004 03:57 AM
remote desktop with routing and remote access Marcus \(Cascom\) Windows Networking 3 01-17-2004 05:15 PM



1 2 3 4 5 6 7 8 9 10 11