Joe's Twisted-up Network

Hello,

I have been here before, got some great help but however my twisted up
network has given me the blues : (

I thought this time before I would get a little better perspective on things
before posting, as it is, at this time, I have not been able to resolve my
problem.(4 weeks)

Furthermore it may not be resolvable in it;s current state.

I have posted images of the problem at this address so I can better explain
and shorten everything for anyone who may want to help out here: )
http://www.animocracy.com/Gallery1.htm

The issue remains that I am trying to work with two routers and keep
seperate public IP's on each router for two servers. I do not care what IP's
the XP machines get but the servers are crucial.

I am successful at this but I need to use a DC and I cannot see for the life
of me how to get this to work. These routers may not work but I am not
experienced enough to say with two routers
..
I realize that the DNS server for all Machines need to be the AD/DC
But how would you implement this into these routers?

My AD/DC experience is without routers and I used a Server as a router with
RRAS and an 8 port switch out to the other machines. However this had just
one IP on all machines and the DNS of the DC. Worked great.

Thank you for any help here.

Joe

1. The web site shows an incomplete IP for the router - 69.65.81

2. Your first DC will host a DNS zone with the same name as your AD domain
name. The DC and all AD client machines will point to the DC's IP for
primary DNS. In the DNS console on the DC you configure Forwarders to point
to the IP of your ISP's DNS server - 24.233.167.167 and 24.233.167.168. As
a result all DNS queries in the AD domain will be sent to the DC. If the
query is for a domain other than your AD domain, the DC forwards the query
to the ISP and passes the response back to client.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Joe" <(E-Mail Removed)> wrote in message
news:8A58C9FC-6DEE-4DEC-92E1-(E-Mail Removed)...
> Hello,
>
> I have been here before, got some great help but however my twisted up
> network has given me the blues : (
>
> I thought this time before I would get a little better perspective on
things
> before posting, as it is, at this time, I have not been able to resolve my
> problem.(4 weeks)
>
> Furthermore it may not be resolvable in it;s current state.
>
> I have posted images of the problem at this address so I can better
explain
> and shorten everything for anyone who may want to help out here: )
> http://www.animocracy.com/Gallery1.htm
>
> The issue remains that I am trying to work with two routers and keep
> seperate public IP's on each router for two servers. I do not care what
IP's
> the XP machines get but the servers are crucial.
>
> I am successful at this but I need to use a DC and I cannot see for the
life
> of me how to get this to work. These routers may not work but I am not
> experienced enough to say with two routers
> .
> I realize that the DNS server for all Machines need to be the AD/DC
> But how would you implement this into these routers?
>
> My AD/DC experience is without routers and I used a Server as a router
with
> RRAS and an 8 port switch out to the other machines. However this had just
> one IP on all machines and the DNS of the DC. Worked great.
>
> Thank you for any help here.
>
> Joe
>

Hello Doug,

Thank you foir your reply,

I need to do a tiny bit more explaining. The DNS's you see here are my ISP's
and I removed the IP's lase digits for security reasons.

WAN side of these routers are configured lke this
69.65.81.13x
255.255.255.0
69.65.81.1

DNS
24.233.167.168
24.233.167.168
This is the FR11P router

The other is the same with a public IP of 69.65.81.14x

THE WAN side of this is fine it is the internal part that is confusing me.
How do you get these routers to work toghether in an AD DC enviroment
internally?
Do you physically add a cable between them?
I do not see a DNS option on the LAN side of these routers. However I do see
a WINS option on the FVS318.

Thank you very much
Joe

"Doug Sherman [MVP]" wrote:

> 1. The web site shows an incomplete IP for the router - 69.65.81
>
> 2. Your first DC will host a DNS zone with the same name as your AD domain
> name. The DC and all AD client machines will point to the DC's IP for
> primary DNS. In the DNS console on the DC you configure Forwarders to point
> to the IP of your ISP's DNS server - 24.233.167.167 and 24.233.167.168. As
> a result all DNS queries in the AD domain will be sent to the DC. If the
> query is for a domain other than your AD domain, the DC forwards the query
> to the ISP and passes the response back to client.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Joe" <(E-Mail Removed)> wrote in message
> news:8A58C9FC-6DEE-4DEC-92E1-(E-Mail Removed)...
> > Hello,
> >
> > I have been here before, got some great help but however my twisted up
> > network has given me the blues : (
> >
> > I thought this time before I would get a little better perspective on
> things
> > before posting, as it is, at this time, I have not been able to resolve my
> > problem.(4 weeks)
> >
> > Furthermore it may not be resolvable in it;s current state.
> >
> > I have posted images of the problem at this address so I can better
> explain
> > and shorten everything for anyone who may want to help out here: )
> > http://www.animocracy.com/Gallery1.htm
> >
> > The issue remains that I am trying to work with two routers and keep
> > seperate public IP's on each router for two servers. I do not care what
> IP's
> > the XP machines get but the servers are crucial.
> >
> > I am successful at this but I need to use a DC and I cannot see for the
> life
> > of me how to get this to work. These routers may not work but I am not
> > experienced enough to say with two routers
> > .
> > I realize that the DNS server for all Machines need to be the AD/DC
> > But how would you implement this into these routers?
> >
> > My AD/DC experience is without routers and I used a Server as a router
> with
> > RRAS and an 8 port switch out to the other machines. However this had just
> > one IP on all machines and the DNS of the DC. Worked great.
> >
> > Thank you for any help here.
> >
> > Joe
> >
>
>
>

As long as the routers have compatible LAN IP addresses - eg. 192.168.1.1
and 192.168.1.2 - you can use a standard ethernet cable to connect a LAN
port on one to a LAN port on the other - use an uplink port if the router
has one.

I would not enable DHCP on either of these routers. If you want DHCP,
configure it on the server.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Joe" <(E-Mail Removed)> wrote in message
news:7021FD69-253A-498C-9E7D-(E-Mail Removed)...
> Hello Doug,
>
> Thank you foir your reply,
>
> I need to do a tiny bit more explaining. The DNS's you see here are my
ISP's
> and I removed the IP's lase digits for security reasons.
>
> WAN side of these routers are configured lke this
> 69.65.81.13x
> 255.255.255.0
> 69.65.81.1
>
> DNS
> 24.233.167.168
> 24.233.167.168
> This is the FR11P router
>
> The other is the same with a public IP of 69.65.81.14x
>
> THE WAN side of this is fine it is the internal part that is confusing me.
> How do you get these routers to work toghether in an AD DC enviroment
> internally?
> Do you physically add a cable between them?
> I do not see a DNS option on the LAN side of these routers. However I do
see
> a WINS option on the FVS318.
>
> Thank you very much
> Joe
>
> "Doug Sherman [MVP]" wrote:
>
> > 1. The web site shows an incomplete IP for the router - 69.65.81
> >
> > 2. Your first DC will host a DNS zone with the same name as your AD
domain
> > name. The DC and all AD client machines will point to the DC's IP for
> > primary DNS. In the DNS console on the DC you configure Forwarders to
point
> > to the IP of your ISP's DNS server - 24.233.167.167 and 24.233.167.168.
As
> > a result all DNS queries in the AD domain will be sent to the DC. If
the
> > query is for a domain other than your AD domain, the DC forwards the
query
> > to the ISP and passes the response back to client.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Joe" <(E-Mail Removed)> wrote in message
> > news:8A58C9FC-6DEE-4DEC-92E1-(E-Mail Removed)...
> > > Hello,
> > >
> > > I have been here before, got some great help but however my twisted up
> > > network has given me the blues : (
> > >
> > > I thought this time before I would get a little better perspective on
> > things
> > > before posting, as it is, at this time, I have not been able to
resolve my
> > > problem.(4 weeks)
> > >
> > > Furthermore it may not be resolvable in it;s current state.
> > >
> > > I have posted images of the problem at this address so I can better
> > explain
> > > and shorten everything for anyone who may want to help out here: )
> > > http://www.animocracy.com/Gallery1.htm
> > >
> > > The issue remains that I am trying to work with two routers and keep
> > > seperate public IP's on each router for two servers. I do not care
what
> > IP's
> > > the XP machines get but the servers are crucial.
> > >
> > > I am successful at this but I need to use a DC and I cannot see for
the
> > life
> > > of me how to get this to work. These routers may not work but I am not
> > > experienced enough to say with two routers
> > > .
> > > I realize that the DNS server for all Machines need to be the AD/DC
> > > But how would you implement this into these routers?
> > >
> > > My AD/DC experience is without routers and I used a Server as a
router
> > with
> > > RRAS and an 8 port switch out to the other machines. However this had
just
> > > one IP on all machines and the DNS of the DC. Worked great.
> > >
> > > Thank you for any help here.
> > >
> > > Joe
> > >
> >
> >
> >

Hello Doug,

This is a tremendous help I thank you soo much!

I have some follow-up questions please.

1. When you say compatible I am able to set the routers to this eg.
192.168.1.1
> and 192.168.1.2 - and access the admin and go fromt here. Is this what you mean by compatible?

2. I have uplink ports on the routers. However if I can remember one router
takes over and gives the same IP . Is this normal or was it a lack of
knowledge in my previous config.? Also do I enable the uplink on both
routers? I say this because one has an auto sensing port and the other is a
manual swich to enable the uplinking.

3. Do these routers need the internal AD DNS inputted to them?

I think that should do it : )
Thank you
Joe

"Doug Sherman [MVP]" wrote:

> As long as the routers have compatible LAN IP addresses - eg. 192.168.1.1
> and 192.168.1.2 - you can use a standard ethernet cable to connect a LAN
> port on one to a LAN port on the other - use an uplink port if the router
> has one.
>
> I would not enable DHCP on either of these routers. If you want DHCP,
> configure it on the server.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Joe" <(E-Mail Removed)> wrote in message
> news:7021FD69-253A-498C-9E7D-(E-Mail Removed)...
> > Hello Doug,
> >
> > Thank you foir your reply,
> >
> > I need to do a tiny bit more explaining. The DNS's you see here are my
> ISP's
> > and I removed the IP's lase digits for security reasons.
> >
> > WAN side of these routers are configured lke this
> > 69.65.81.13x
> > 255.255.255.0
> > 69.65.81.1
> >
> > DNS
> > 24.233.167.168
> > 24.233.167.168
> > This is the FR11P router
> >
> > The other is the same with a public IP of 69.65.81.14x
> >
> > THE WAN side of this is fine it is the internal part that is confusing me.
> > How do you get these routers to work toghether in an AD DC enviroment
> > internally?
> > Do you physically add a cable between them?
> > I do not see a DNS option on the LAN side of these routers. However I do
> see
> > a WINS option on the FVS318.
> >
> > Thank you very much
> > Joe
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > 1. The web site shows an incomplete IP for the router - 69.65.81
> > >
> > > 2. Your first DC will host a DNS zone with the same name as your AD
> domain
> > > name. The DC and all AD client machines will point to the DC's IP for
> > > primary DNS. In the DNS console on the DC you configure Forwarders to
> point
> > > to the IP of your ISP's DNS server - 24.233.167.167 and 24.233.167.168.
> As
> > > a result all DNS queries in the AD domain will be sent to the DC. If
> the
> > > query is for a domain other than your AD domain, the DC forwards the
> query
> > > to the ISP and passes the response back to client.
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Joe" <(E-Mail Removed)> wrote in message
> > > news:8A58C9FC-6DEE-4DEC-92E1-(E-Mail Removed)...
> > > > Hello,
> > > >
> > > > I have been here before, got some great help but however my twisted up
> > > > network has given me the blues : (
> > > >
> > > > I thought this time before I would get a little better perspective on
> > > things
> > > > before posting, as it is, at this time, I have not been able to
> resolve my
> > > > problem.(4 weeks)
> > > >
> > > > Furthermore it may not be resolvable in it;s current state.
> > > >
> > > > I have posted images of the problem at this address so I can better
> > > explain
> > > > and shorten everything for anyone who may want to help out here: )
> > > > http://www.animocracy.com/Gallery1.htm
> > > >
> > > > The issue remains that I am trying to work with two routers and keep
> > > > seperate public IP's on each router for two servers. I do not care
> what
> > > IP's
> > > > the XP machines get but the servers are crucial.
> > > >
> > > > I am successful at this but I need to use a DC and I cannot see for
> the
> > > life
> > > > of me how to get this to work. These routers may not work but I am not
> > > > experienced enough to say with two routers
> > > > .
> > > > I realize that the DNS server for all Machines need to be the AD/DC
> > > > But how would you implement this into these routers?
> > > >
> > > > My AD/DC experience is without routers and I used a Server as a
> router
> > > with
> > > > RRAS and an 8 port switch out to the other machines. However this had
> just
> > > > one IP on all machines and the DNS of the DC. Worked great.
> > > >
> > > > Thank you for any help here.
> > > >
> > > > Joe
> > > >
> > >
> > >
> > >
>
>
>

Hello Doug,

I have been successfull up till now trying to join the domain. I got this
error

Note: This information is intended for a network administrator. If you are
not your network's administrator, notify the administrator that you received
this information, which has been recorded in the file
C:\WINDOWS\debug\dcdiag.txt.

The domain name slovaunmail might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
slovaunmail:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.slovaunmail

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

slovaunmail
.. (the root zone)

For information about correcting this problem, click Help.

Thank you
Joe

"Doug Sherman [MVP]" wrote:

> As long as the routers have compatible LAN IP addresses - eg. 192.168.1.1
> and 192.168.1.2 - you can use a standard ethernet cable to connect a LAN
> port on one to a LAN port on the other - use an uplink port if the router
> has one.
>
> I would not enable DHCP on either of these routers. If you want DHCP,
> configure it on the server.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Joe" <(E-Mail Removed)> wrote in message
> news:7021FD69-253A-498C-9E7D-(E-Mail Removed)...
> > Hello Doug,
> >
> > Thank you foir your reply,
> >
> > I need to do a tiny bit more explaining. The DNS's you see here are my
> ISP's
> > and I removed the IP's lase digits for security reasons.
> >
> > WAN side of these routers are configured lke this
> > 69.65.81.13x
> > 255.255.255.0
> > 69.65.81.1
> >
> > DNS
> > 24.233.167.168
> > 24.233.167.168
> > This is the FR11P router
> >
> > The other is the same with a public IP of 69.65.81.14x
> >
> > THE WAN side of this is fine it is the internal part that is confusing me.
> > How do you get these routers to work toghether in an AD DC enviroment
> > internally?
> > Do you physically add a cable between them?
> > I do not see a DNS option on the LAN side of these routers. However I do
> see
> > a WINS option on the FVS318.
> >
> > Thank you very much
> > Joe
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > 1. The web site shows an incomplete IP for the router - 69.65.81
> > >
> > > 2. Your first DC will host a DNS zone with the same name as your AD
> domain
> > > name. The DC and all AD client machines will point to the DC's IP for
> > > primary DNS. In the DNS console on the DC you configure Forwarders to
> point
> > > to the IP of your ISP's DNS server - 24.233.167.167 and 24.233.167.168.
> As
> > > a result all DNS queries in the AD domain will be sent to the DC. If
> the
> > > query is for a domain other than your AD domain, the DC forwards the
> query
> > > to the ISP and passes the response back to client.
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Joe" <(E-Mail Removed)> wrote in message
> > > news:8A58C9FC-6DEE-4DEC-92E1-(E-Mail Removed)...
> > > > Hello,
> > > >
> > > > I have been here before, got some great help but however my twisted up
> > > > network has given me the blues : (
> > > >
> > > > I thought this time before I would get a little better perspective on
> > > things
> > > > before posting, as it is, at this time, I have not been able to
> resolve my
> > > > problem.(4 weeks)
> > > >
> > > > Furthermore it may not be resolvable in it;s current state.
> > > >
> > > > I have posted images of the problem at this address so I can better
> > > explain
> > > > and shorten everything for anyone who may want to help out here: )
> > > > http://www.animocracy.com/Gallery1.htm
> > > >
> > > > The issue remains that I am trying to work with two routers and keep
> > > > seperate public IP's on each router for two servers. I do not care
> what
> > > IP's
> > > > the XP machines get but the servers are crucial.
> > > >
> > > > I am successful at this but I need to use a DC and I cannot see for
> the
> > > life
> > > > of me how to get this to work. These routers may not work but I am not
> > > > experienced enough to say with two routers
> > > > .
> > > > I realize that the DNS server for all Machines need to be the AD/DC
> > > > But how would you implement this into these routers?
> > > >
> > > > My AD/DC experience is without routers and I used a Server as a
> router
> > > with
> > > > RRAS and an 8 port switch out to the other machines. However this had
> just
> > > > one IP on all machines and the DNS of the DC. Worked great.
> > > >
> > > > Thank you for any help here.
> > > >
> > > > Joe
> > > >
> > >
> > >
> > >
>
>
>

Thank you Mr. Sherman

I got it all completed now.

Thank you
Joe

"Doug Sherman [MVP]" wrote:

> As long as the routers have compatible LAN IP addresses - eg. 192.168.1.1
> and 192.168.1.2 - you can use a standard ethernet cable to connect a LAN
> port on one to a LAN port on the other - use an uplink port if the router
> has one.
>
> I would not enable DHCP on either of these routers. If you want DHCP,
> configure it on the server.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "Joe" <(E-Mail Removed)> wrote in message
> news:7021FD69-253A-498C-9E7D-(E-Mail Removed)...
> > Hello Doug,
> >
> > Thank you foir your reply,
> >
> > I need to do a tiny bit more explaining. The DNS's you see here are my
> ISP's
> > and I removed the IP's lase digits for security reasons.
> >
> > WAN side of these routers are configured lke this
> > 69.65.81.13x
> > 255.255.255.0
> > 69.65.81.1
> >
> > DNS
> > 24.233.167.168
> > 24.233.167.168
> > This is the FR11P router
> >
> > The other is the same with a public IP of 69.65.81.14x
> >
> > THE WAN side of this is fine it is the internal part that is confusing me.
> > How do you get these routers to work toghether in an AD DC enviroment
> > internally?
> > Do you physically add a cable between them?
> > I do not see a DNS option on the LAN side of these routers. However I do
> see
> > a WINS option on the FVS318.
> >
> > Thank you very much
> > Joe
> >
> > "Doug Sherman [MVP]" wrote:
> >
> > > 1. The web site shows an incomplete IP for the router - 69.65.81
> > >
> > > 2. Your first DC will host a DNS zone with the same name as your AD
> domain
> > > name. The DC and all AD client machines will point to the DC's IP for
> > > primary DNS. In the DNS console on the DC you configure Forwarders to
> point
> > > to the IP of your ISP's DNS server - 24.233.167.167 and 24.233.167.168.
> As
> > > a result all DNS queries in the AD domain will be sent to the DC. If
> the
> > > query is for a domain other than your AD domain, the DC forwards the
> query
> > > to the ISP and passes the response back to client.
> > >
> > > Doug Sherman
> > > MCSE, MCSA, MCP+I, MVP
> > >
> > > "Joe" <(E-Mail Removed)> wrote in message
> > > news:8A58C9FC-6DEE-4DEC-92E1-(E-Mail Removed)...
> > > > Hello,
> > > >
> > > > I have been here before, got some great help but however my twisted up
> > > > network has given me the blues : (
> > > >
> > > > I thought this time before I would get a little better perspective on
> > > things
> > > > before posting, as it is, at this time, I have not been able to
> resolve my
> > > > problem.(4 weeks)
> > > >
> > > > Furthermore it may not be resolvable in it;s current state.
> > > >
> > > > I have posted images of the problem at this address so I can better
> > > explain
> > > > and shorten everything for anyone who may want to help out here: )
> > > > http://www.animocracy.com/Gallery1.htm
> > > >
> > > > The issue remains that I am trying to work with two routers and keep
> > > > seperate public IP's on each router for two servers. I do not care
> what
> > > IP's
> > > > the XP machines get but the servers are crucial.
> > > >
> > > > I am successful at this but I need to use a DC and I cannot see for
> the
> > > life
> > > > of me how to get this to work. These routers may not work but I am not
> > > > experienced enough to say with two routers
> > > > .
> > > > I realize that the DNS server for all Machines need to be the AD/DC
> > > > But how would you implement this into these routers?
> > > >
> > > > My AD/DC experience is without routers and I used a Server as a
> router
> > > with
> > > > RRAS and an 8 port switch out to the other machines. However this had
> just
> > > > one IP on all machines and the DNS of the DC. Worked great.
> > > >
> > > > Thank you for any help here.
> > > >
> > > > Joe
> > > >
> > >
> > >
> > >
>
>
>