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

"markm75" <markm75c@xxxxxxx> wrote in message
news:1189787349.450280.58110@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'll start the description from scratch.. and maybe this will shed
some light:

I have a symantec gateway router.. connected to the internet and my
internal .100 lan (call it the real lan).

Ok. Let's call it the "100-LAN" and the "277-LAN". Numbers are more
specific,.."real" and "virtual" are too fuzzy. It really doesn't matter if
it is virtual or physical, it all works by the same rules.

On this device I setup the static route.. It is set to 192.168.227.0,
255.255.255.0 mask, 192.168.227.6 gateway (the RRAS on the virtual
LAN).

Ok. I belive that is wrong. But I can't tell wht it should be because you
haven't given the real IP#s numbers for the devices. The Symantec Device
eixsts on the 100-LAN,...Gateways must exist on the *same* network as the
device that uses it. Therefore the Gateway has to be a number from the
100-LAN.


In order to resolve names, using at least FQDN.. i then had to goto
the DNS on the .100 lan and... Right click the DNS server name..
properties.. Forwarders tab.. then.. rather than just clicking on "all
other dns domains" and adding the .227.2 (dns server) entry.. it
seemed i had to click the "new" button.. create a new DNS domain.. so
i put in psttest.local (our virtual lan domain name).. i then clicked
on that entry.. and entered the .227.2 address for the DNS server.

Then on the virtual lan.. i did this same thing.. only i created the
new dns domain called pst.local and then clicked the entry and added
the .100.2 (dns server) entry there.

No. Undo all that, put it back the way it was origninally. Setup "Zone
Tranfers". Do it on each LAN. The 100-DNS needs to pick up the Zone from
the 277-DNS,...and likewise the 277-DNS nees to pick up the Zone from the
100-DNS. The goal is that each DNS Server has a current copy of the Zone
from the other LAN.

Then on all the DNS Servers (all of them) add the ISP's DNS to the
Forwarders List in the DNS Service Config. The ISP's DNS is the only entry
that should be in there.

On the RRAS server.. I have two nics.. (virtual server).. one is
called "pst.local" while the other is "psttest.local".. the pst.local
nic has a .100.x address and the other has the .227.x address.

At this point i can ping either domain.. but only by FQDN.. ie: from
production: ping vpcServerA.psttest.local works fine and then the
reverse works fine from the test lan.

Then the RRAS LAN Router works. You are done with that.

If i try to ping an ip address on the internet.. ie: www.google.com
's ip address (not domain name).. it Fails.. likewise of course
pinging it by name fails.

That is because of the gateway error I mentioned at the beginning of this
post.

I tried going into the RRAS server and adding the NAT protocol.. i
wasnt sure if this was needed .. this didnt help things.. though I may
have had it configured wrong.

Remove that and put it all back like it was. There is not to be any "NAT"
going on around here.

Any thoughts on the step i'm missing to make internet pings work? Did
I do the DNS entries correctly in the forwarding tab? (I haven't done
any zone transfers or adding extra name servers thus far, as they dont
seem necessary since these are independent domains).

Yes.
1. The gateway error I mentioned at the beginning of this post
2. Do the Zone Transfers. However you can still ping by IP# without those.

--
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.
-----------------------------------------------------


.