Re: How to enable communication between Two different lans (subnets)/ domains 2003 server based? Assistance?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

And also note that it is not a good idea to use a DC as a router, whatever
setup you are using. A DC should only have one NIC and one IP. You will get
all sorts of odd problems with a multihomed DC.

You will also almost certainly have DNS problems running a domain behind a
NAT router, if you go down that path. All machines in a domain, including
the DC itself should use the local DNS. If you want Internet access you need
to set up this DNS to forward to a public DNS service. Using the NAT router
for DNS will result in problems for your AD clients.

"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message
news:uPqzgpP2HHA.536@xxxxxxxxxxxxxxxxxxxxxxx
To add to Bill's comments, I need to clear something up before it becomes
a point of confusion.

Domains have nothing to do with subnets,...subnets have nothing to do with
Domains.
You can have 100 Domains all on one subnet,...or,..you can have one Domain
that runs over 100 subnets. There is just no relationship between the
two.

Sharing resources between two Domains is all about properly configured
Trusts, Share Permissions, and NTFS Permissions.

Functionality across subnets is a matter of a proper Layer3 LAN Routing
scheme.


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or
Microsoft, or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------

"markm75" <markm75c@xxxxxxx> wrote in message
news:1186431399.804955.180380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have our production lan that is on 192.168.100.x.. this is a 2003
server domain, with a DHCP server running on one of the 2003 boxes.

I also have a development test lan that is 192.168.227.x.. this too is
a 2003 domain with a DHCP server running on one of the 2003 boxes
there.

I want to be able to share resources between the 2.. ie: if i'm a box
on 227.x.. i want to be able to either say \\192.168.100.2\apps or \
\servername\apps..

I've tried setting up RAS servers on both ends.. then setting static
routes between them..

I've also tried adding the 100.x gateway as a secondary gateway on the
one 227.x server, but this didnt work either...

One thing to note.. the 227.x lan is actually run completely on my
Vista machine under Vmware Workstation 6.x I have the servers set to
"bridged mode" (there is also nat mode, which uses the same ip as the
host OS, or host only mode, which completely isolates the guest from
the host).

Ultimately too, I'd like to have someone running vmware on their
machine, to create say an XP virtual machine and join the test domain
that is running from my machine.

I dont think the issue is VMware related.. I think i'm just missing a
step in RAS (if ras is even needed) or somewhere else (maybe demand
dialing between the two ras servers if needed?)?

One key thing i was worried about was the fact i have a dhcp server on
both domains.. as i only want dhcp requests in the wild to be
processed by the 100.x server, so i'm guessing i'd have to turn off
the dhcp server on the test domain.

Thanks for any tips





.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)