Re: A remote subnet cannot connect to domain server.
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Feb 2008 11:12:00 -0500
Job Andersson <JobAndersson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Out network consist of three subnets. Ive put them on subnets just or
the sake of siplicity, I am unaware of any complications this could
have with SBS server and it has worked fine this far.
Hmmm. Well, in general, "three subnets" and "simplicity" are not words I
see in the same sentence, but as you're talking about branch offices & VPN,
you really have no choice. I'm presuming you've got a single NIC in your SBS
box?
At the moment I am trying to connect a second remote office to our
domain through VPN. VPN connection checks out and seems to be
operating 100% correct. The network/router/VPN configuration is
essential the same as the first subnet I set up and connected to our
server. The first subnet works lika a charm. No problems at all.
What kind of VPN are you using? What kind of router is there on subnet 1?
I draw a quick illustration to show the network.
http://www.acc.umu.se/~storm/misc/share/vpn_en.png
Nicely done diagram! Especially "the internets."
So, give that VPN really works (which it is).
How do you know? From subnet 2, can you ping 192.168.1.2 ?
What are the specific errors you're seeing?
The problem must be that:
1.
Domain name server does not allow subnet 192.168.2.0 to make DNS
lookups. Can DNS be restricted in this way,
No....
how do I then remove that
restriction? I didnt need to configure DNS at all to allow subnet 0
to make DNS lookups and connect to server.
2.
The CISCO integrated service router is somehow still interfering with
connection to server from subnet 2. But I cannot understand how and
why, according to subnet 2 ISP their router doesnt stop any traffic
at all.
Well, as their device is the odd man out here, it is looking likely.
... any more ideas? At this stage I have absolute no clue and am
desperate for help. ANyone who set up / connected remote VPN networks
to your domain, had any problems like this?
And yeah, before anyone ask... I run IECW all the time, every second
of my life. :) So nm that. I am also aware that server IP must be DNS
at all networks to make that network able to connect to domain.
I will keep watchig this thread closely, if I left out anything
relevant dont hesitate to ask Ill reply asap.
Thanks for reading :) Any ideas?!1
One thing to mentoin - remote offices on the domain generally do better to
have a local DC/DNS/GC....even if it's running on crappy hardware.
Authentication over a WAN link,and group policy stuff, etc., do not work
well. Of course, you need to ensure you've got working VPN connectivity
first.
.
- Prev by Date: Re: Remote Web Workplace - Using Outlook
- Next by Date: Re: Remote Web Workplace - Using Outlook
- Previous by thread: Unable to enable message tracking...
- Next by thread: OWA HTTP 404 Error
- Index(es):
Relevant Pages
|
