Help with VPN, two domains & Server 2003

  • Thread starter Thread starter Bababooey
  • Start date Start date
B

Bababooey

Hi - need some help with the following from all the network pro's ou
there

Here is the situation

Two offices we will call location A and location

Location A - Server 2003 - running active directory, DNS and DHCP wit
regular domain setup as "locationa.local" Internal Subnet i
192.168.2.

Location B - Server 2003 - running active directory, DNS and DHCP wit
regular domain setup as "locationb.local" Internal Subnet i
192.168.1.

Each office has broadband connection through a Linksys BEFSX41 (VP
Endpoint

Have established a VPN connection between the two routers
offices with no problem

From any computer at location A, can ping computer in location B wit
no problems - yet when going to network neighboorhood can only se
the local domain and not the remote domain at location

I figure that I need to somehow get the two subnets and domains t
talk to each other directly - but not quite sure what to do

Please help - and thank yo
 
On Tue, 11 Oct 2005 18:12:03 GMT,
Hi - need some help with the following from all the network pro's out
there.

Here is the situation.

Two offices we will call location A and location B

Location A - Server 2003 - running active directory, DNS and DHCP with
regular domain setup as "locationa.local" Internal Subnet is
192.168.2.0

Location B - Server 2003 - running active directory, DNS and DHCP with
regular domain setup as "locationb.local" Internal Subnet is
192.168.1.0

Each office has broadband connection through a Linksys BEFSX41 (VPN
Endpoint)

Have established a VPN connection between the two routers &
offices with no problems

From any computer at location A, can ping computer in location B with
no problems - yet when going to network neighboorhood can only see
the local domain and not the remote domain at location B

I figure that I need to somehow get the two subnets and domains to
talk to each other directly - but not quite sure what to do.

Please help - and thank you
Click to expand...

Long time since I messed with VPNs but I recall the subnet has to be
different on each domain otherwise comp A can't see comp B's folders
and vice versa. As I recall I left one network on 198.162.x.x and set
up the other on 10.x.x.x and it fired up nicely. Different Subnet
Masks as well I think.

Given up using it because it was so problematical and unreliable -
that was some time ago though.

Jonah
 
Thanks for the reply - tried the netbios thing on the Linksys and n
change. Thanks anywa

Ok, maybe I wasn't as clear as some of you wanted. I will try t
explain exactly where we are at

Location A
One Server running Server 2003 w/DNS/DHCP/A
Broadband connection through modem to Linksys BEFSX4
domain - locationa.local - not associated in any way with any othe
domain or offic
internal subnet 192.168.2.
40 workstations running XP Pr
VPN has been established with Location B via BEFSX41 Route

Location
One Server running Server 2003 w/DNS/DHCP/A
Broadband connection through modem to Linksys BEFSX4
domain - locationb.local - not associated in any way with any othe
domain or offic
internal subnet 192.168.1.
40 workstations running XP Pr
VPN has been established with Location B via BEFSX41 Route

From Location
From either server or workstation when going to networ
neighboorhood/entire network/microsoft network we only see th
locationa domain and when clicking on that all workstations an
server are visible. Pull up windows explorer and type in known I
address of another workstation at location b (when doing search fo
computers) that workstation is able to be viewed and file
transferred back and forth. When going into command prompt an
pinging any known ip's for workstations at location b, ping i
successful

On server at location A, attempted to open active directory trusts
right clicked on domain locationa.local and select properties the
trust and attempted to add locationb.local domain and message sai
that domain could not be foun

At this point, all what we would like to do (with what we have a
stated in the setup above) is that when a user at either location
or b goes into network neighboorhood, they will be able to view th
other domain and access the systems (granted they have the correc
username/password/permissions

Thanks agai
 
Thanks for the reply - tried the netbios thing on the Linksys and no
change. Thanks anyway

Ok, maybe I wasn't as clear as some of you wanted. I will try to
explain exactly where we are at.

Location A
One Server running Server 2003 w/DNS/DHCP/AD
Broadband connection through modem to Linksys BEFSX41
domain - locationa.local - not associated in any way with any other
domain or office
internal subnet 192.168.2.0
40 workstations running XP Pro
VPN has been established with Location B via BEFSX41 Router

Location B
One Server running Server 2003 w/DNS/DHCP/AD
Broadband connection through modem to Linksys BEFSX41
domain - locationb.local - not associated in any way with any other
domain or office
internal subnet 192.168.1.0
40 workstations running XP Pro
VPN has been established with Location B via BEFSX41 Router

From Location A
From either server or workstation when going to network
neighboorhood/entire network/microsoft network we only see the
locationa domain and when clicking on that all workstations and
server are visible. Pull up windows explorer and type in known IP
address of another workstation at location b (when doing search for
computers) that workstation is able to be viewed and files
transferred back and forth. When going into command prompt and
pinging any known ip's for workstations at location b, ping is
successful.

On server at location A, attempted to open active directory trusts,
right clicked on domain locationa.local and select properties then
trust and attempted to add locationb.local domain and message said
that domain could not be found

At this point, all what we would like to do (with what we have as
stated in the setup above) is that when a user at either location a
or b goes into network neighboorhood, they will be able to view the
other domain and access the systems (granted they have the correct
username/password/permissions)
Click to expand...

You have DNS problems.

If you want one domain to see the other you need to create DNS records
for each or to have some other means for DNS to identify each side to
the other.
 
Ok, one update on this.

It seems that enabling the netbios passthroughs on the Linksys route
has allowed each location to see each other in networ
neighboorhood

It seems that there was a delay before this happened

I guess the question is - is there a way to make this happen in Activ
Directory

Also how can you make it that location A can see everything a
location B but location B cannot see what is in location A

Thank
 
Ok, so what is the best way to set up the DNS between the two separat
domains as described in my previous post

Thank
 
Back
Top