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

On Sep 13, 7:34 pm, "Bill Grant" <not.available@online> wrote:
Yes, it probably is a routing issue. The Internet router probably has no
idea where the new inner subnet is. You need a route on the Internet router
to forward traffic for the new subnet to the internal router.

"markm75" <markm...@xxxxxxx> wrote in message

news:1189716017.545836.210710@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



On Sep 13, 10:53 am, markm75 <markm...@xxxxxxx> wrote:
On Sep 12, 7:02 pm, "Bill Grant" <not.available@online> wrote:

"markm75" <markm...@xxxxxxx> wrote in message

news:1189608019.269001.233850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Aug 8, 4:09 am, "Bill Grant" <not.available@online> wrote:
"markm75" <markm...@xxxxxxx> wrote in message

news:1186544433.210552.313670@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Aug 7, 9:26 pm, "Bill Grant" <not.available@online> wrote:

I would recommend that you set up your new domain on an isolated
network
and get it working properly on its own subnet using its own DNS and
DHCP.
When that all works, set up a virtual machine (not the DC) as a
router
between that subnet and your existing physicalLAN. You will need
extra
routing so that the existingLANknows where the new subnet is and how
to
reach it. You will also need to set up your DNS on the new domain to
forward
to a DNS server which can resolve public URLs.- Hide quoted text -

- Show quoted text -

Working like a charm so far.. All i had to do was add a static route
in my router to the RAS server on my virtual network.. and on that
RAS
server have a secondary nic with an ip address in the real domain..
all machines in the virtual realm have the gateway set to the RAS
server address..

Now onto secondary thing.. DNS.. what is the usual way to hack this
one.. should i just put for the secondary dns addresses on every
machine in the Virtual Network, the dns of the real network? Or can I
just do a forward from within the DNS manager (right click server
name.. forwards tab.. enter ip address of the opposite dns servers?)
on the Virtual network and the same on the real.. i think this one
would be simpler?

I can only ping by ip as of now naturally.

UPDATE: Tried adding the real domains ip addresses to the forwarders
tab, recycled things, waited, i still cant ping them by name as of
now. Actually.. i can ping the other domain.. but only if i add the
domain suffix.. ie: ping serverA.domain.local I'm guessing i can
tweak
the settings to fix this.. hoping i dont need to add this suffix to
every machine in the virtual realm. This ping with the suffix
actually
works without doing anything to DNS on either side too.

Have you tried simply setting the new DNS to forward all requests
to the
existing DNS on the physical network? Another solution would be to make
the
new DNS a secondary for the original DNS so that it had a local copy.-
Hide quoted text -

- Show quoted text -

I think at first i did try the forwarding option, just adding the ips,
but...

I fixed the problem.. on the server properties for each dns server on
each side.. i had to add a new dns domain for the opposite domain (not
just add the ip), then the dns server(s) ip addresses.. once i did
this.. they started communicating from either side.. but only by
FQDN..

I cant run DHCP on the virtual LAN, or so i think, because if i do..
it may give out those .227.x addresses to the .100.x machines by
mistake (hence I think, naturally, the test domain machine names dont
auto get put into DNS, with their A records).. so everything is manual
on the virtual side.. meaning now to ping either side.. i use the
FQDN, but name nonetheless (\\server.domain.local)- Hide quoted text -

- Show quoted text -

Actually I have a new problem.. for some reason my virtual lan cannot
access the internet.. I cant even ping via internet ip addresses.. so
i dont think it is a dns issue, more likely a routing issue.- Hide quoted text -

- Show quoted text -

My virtual network is the one running the RRAS server on .227.6
while my real network is on .100.1 (gateway, symantec router, internet
router). I previously added a static route to the Symantec Gateway
router to the 192.168.227.0 / 6 subnet.. so communication could occur
between the two.

Are you saying the RRAS server needs its own static route to the
Symantec .100.1 router? I dont see why, as i can ping back and forth
and dns works back and forth (FQDN).. I also tried pinging internet IP
addresses.. they fail too.


.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)