J
James W. Long
Hi All:
This is not the same question as I asked in my last post.
Larger networking problem. I'm in the design phase of connecting
135 offices to
our corporate office.
Each office has 4 win2k workgroup computers networked together.
One of these is special.
I'll call that special one a "remote office server"
{even though its not a server},
and I'll cal the other three
" remote office networked computers".
we want each remote office to establish a full time vpn link
with coprorate. so thats 135 vpn links to corporate.
ultimately we want to be able to get to the files and shares
on the remote office server and the files and the shares on
the remote office networked computers. but lets not
go all the way there just yet.
I think this is a router to router configuration,
where all the security and encryption is between the the
routers.
everyone will get addresses by DHCP at corporate
everyone registers in WINS and DNS.
when the "remote office servers" vpn's in to corporate,
they appears on our local lan.
and thats were the dillema begins.
our corporate lan is a 10.0.0.x with a mask of 255.255.255.0
so thats 10.0.0.0/24 I think.
We dont have room in the corporate lan for 135 more clients.
so I was thinking that I might want to go to
a 10.0.0.0./16 or 10.0.x.x with a mask of 255.255.0.0.
this mask would go on all the servers and all the clients
and our vpn/firewall at corporate to give us a {much} larger
address space with which to accomodate the 135 new
vpn clients (plus plus and then some and thats okay)
the current IP config at each office is
4 computers with IP's of 10.0.0.1,10.0.0.2
10.0.0.3 and 10.0.0.4 (I did not set it up)
the remote office server is 10.0.0.1 and it vpn's in here
to corporate and gets a dhcp address
in our subnet just fine.
I already have clients/and/or/servers on
10.0.0.2 here at corporate
there is no way I can ping a remote office computer
at 10.0.0.2 is there? didnt think so.
Second Question:
How can I set up the
{etire}?
address scheme
so that I can get to the remote office computers
thru the vpn tunnel established from the
remote office server to corporate?
for instance
if I set office 52 up as
server 10.0.52.10
computer1 10.0.52.20
computer2 10.0.52.30
computer3 10.0.52.40
gateway: 10.0.52.1
mask 255.255.0.0
and corporate was
server 10.0.0.9
gateway 10.0.0.1
mask 255.255.0.0
if office 52 established a vpn tunnel in here
then I could remote desktop to office 52
and see office 52 in network places from corporate
see its shares on its server
I dont think I can ping the remote office computer at 10.0.52.20
from corporate because the router wont go there
but, having a remote desktop session to
the office 52 server I am then on thier network,
I could then ping for instance remote office computer
at 10.0.0.20 and it would then work
right? or I get to its administrative shares?
(goto to run, type dir \\server1\c$)
Any advice is much appreciated!
Thank you in advance,
James W. Long
That mask would have to be everywhere, right?
This is not the same question as I asked in my last post.
Larger networking problem. I'm in the design phase of connecting
135 offices to
our corporate office.
Each office has 4 win2k workgroup computers networked together.
One of these is special.
I'll call that special one a "remote office server"
{even though its not a server},
and I'll cal the other three
" remote office networked computers".
we want each remote office to establish a full time vpn link
with coprorate. so thats 135 vpn links to corporate.
ultimately we want to be able to get to the files and shares
on the remote office server and the files and the shares on
the remote office networked computers. but lets not
go all the way there just yet.
I think this is a router to router configuration,
where all the security and encryption is between the the
routers.
everyone will get addresses by DHCP at corporate
everyone registers in WINS and DNS.
when the "remote office servers" vpn's in to corporate,
they appears on our local lan.
and thats were the dillema begins.
our corporate lan is a 10.0.0.x with a mask of 255.255.255.0
so thats 10.0.0.0/24 I think.
We dont have room in the corporate lan for 135 more clients.
so I was thinking that I might want to go to
a 10.0.0.0./16 or 10.0.x.x with a mask of 255.255.0.0.
this mask would go on all the servers and all the clients
and our vpn/firewall at corporate to give us a {much} larger
address space with which to accomodate the 135 new
vpn clients (plus plus and then some and thats okay)
the current IP config at each office is
4 computers with IP's of 10.0.0.1,10.0.0.2
10.0.0.3 and 10.0.0.4 (I did not set it up)
the remote office server is 10.0.0.1 and it vpn's in here
to corporate and gets a dhcp address
in our subnet just fine.
I already have clients/and/or/servers on
10.0.0.2 here at corporate
there is no way I can ping a remote office computer
at 10.0.0.2 is there? didnt think so.
Second Question:
How can I set up the
{etire}?
address scheme
so that I can get to the remote office computers
thru the vpn tunnel established from the
remote office server to corporate?
for instance
if I set office 52 up as
server 10.0.52.10
computer1 10.0.52.20
computer2 10.0.52.30
computer3 10.0.52.40
gateway: 10.0.52.1
mask 255.255.0.0
and corporate was
server 10.0.0.9
gateway 10.0.0.1
mask 255.255.0.0
if office 52 established a vpn tunnel in here
then I could remote desktop to office 52
and see office 52 in network places from corporate
see its shares on its server
I dont think I can ping the remote office computer at 10.0.52.20
from corporate because the router wont go there
but, having a remote desktop session to
the office 52 server I am then on thier network,
I could then ping for instance remote office computer
at 10.0.0.20 and it would then work
right? or I get to its administrative shares?
(goto to run, type dir \\server1\c$)
Any advice is much appreciated!
Thank you in advance,
James W. Long
That mask would have to be everywhere, right?