We have a server located in a remote location on our network that can't be
mapped to from our Corporate headquarters using the FQDN or ipaddress
resolved by the corporate DNS server, but from our local headquarters we can
map just fine using the FQDN or ipaddress resolved by our local DNS server.
All of our local headquarter servers including our remote servers are
replicated from our local headquaters to our Corporated headquarters, which
is having problems mapping.This server is clustered so this FQDN is virtual
and can floats back and forth in case the server goes down. It is interesting
that the FQDN and ipaddress of the physical server can be mapped both from
our Corporate headquarters and our local headquarters.

Can anyone please in diagnosing this issue

Thank You,

Netahs
--
cool runnings.

In news:1689C483-99FA-4F81-98EC-68C18401B1D3@microsoft.com,
netahs <netahs@discussions.microsoft.com> stated, which I commented on
below:
> We have a server located in a remote location on our network that
> can't be mapped to from our Corporate headquarters using the FQDN or
> ipaddress resolved by the corporate DNS server, but from our local
> headquarters we can map just fine using the FQDN or ipaddress
> resolved by our local DNS server.

Does it resolve to the same IP from both servers or are they different?


>All of our local headquarter
> servers including our remote servers are replicated from our local
> headquaters to our Corporated headquarters, which is having problems
> mapping.

If the zone is being transferred, then I would highly assume the data is
identical.
As for replicating the zone, do you mean the zone is AD Integrated? If so,
it would be getting replicated as part of the AD replication process, since
the zone data exists in the actual AD database.

> This server is clustered so this FQDN is virtual and can
> floats back and forth in case the server goes down. It is interesting
> that the FQDN and ipaddress of the physical server can be mapped both
> from our Corporate headquarters and our local headquarters.

As far as I remember, you can map to each physcial member in a cluster. But
the idea is to map to the ClusterIP. Can I assume the cluster IP is the IP
in DNS? Unless there's more than one IP for the name showing up? If so, you
would only want the Cluster IP to be the one showing for the server's
hostname record in DNS.

>
> Can anyone please in diagnosing this issue
>
> Thank You,
>
> Netahs

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

Ace, we can map to the physical address of the severs but not to the virtual
ip that moves back and forth.Our local headquarters can map just fine in L.A
but in Cinncinati it wont connect when we try to map from a pc in L.A.
configured with the DNS server ipaddress in Cinncinati. The remote server we
are trying to connect to is in Chicago.
--
cool runnings.


"Ace Fekay [MVP]" wrote:

> In news:1689C483-99FA-4F81-98EC-68C18401B1D3@microsoft.com,
> netahs <netahs@discussions.microsoft.com> stated, which I commented on
> below:
> > We have a server located in a remote location on our network that
> > can't be mapped to from our Corporate headquarters using the FQDN or
> > ipaddress resolved by the corporate DNS server, but from our local
> > headquarters we can map just fine using the FQDN or ipaddress
> > resolved by our local DNS server.
>
> Does it resolve to the same IP from both servers or are they different?
>
>
> >All of our local headquarter
> > servers including our remote servers are replicated from our local
> > headquaters to our Corporated headquarters, which is having problems
> > mapping.
>
> If the zone is being transferred, then I would highly assume the data is
> identical.
> As for replicating the zone, do you mean the zone is AD Integrated? If so,
> it would be getting replicated as part of the AD replication process, since
> the zone data exists in the actual AD database.
>
> > This server is clustered so this FQDN is virtual and can
> > floats back and forth in case the server goes down. It is interesting
> > that the FQDN and ipaddress of the physical server can be mapped both
> > from our Corporate headquarters and our local headquarters.
>
> As far as I remember, you can map to each physcial member in a cluster. But
> the idea is to map to the ClusterIP. Can I assume the cluster IP is the IP
> in DNS? Unless there's more than one IP for the name showing up? If so, you
> would only want the Cluster IP to be the one showing for the server's
> hostname record in DNS.
>
> >
> > Can anyone please in diagnosing this issue
> >
> > Thank You,
> >
> > Netahs
>
> --
> Ace
> Innovative IT Concepts, Inc (IITCI)
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
> It's easy:
>
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Infinite Diversities in Infinite Combinations
> Assimilation Imminent. Resistance is Futile
> "Very funny Scotty. Now, beam down my clothes."
>
> The only constant in life is change...
>
>
>

In news:001D638B-AFA9-46A0-90F0-A4F9BAB447D4@microsoft.com,
netahs <netahs@discussions.microsoft.com> stated, which I commented on
below:
> Ace, we can map to the physical address of the severs but not to the
> virtual ip that moves back and forth.Our local headquarters can map
> just fine in L.A but in Cinncinati it wont connect when we try to map
> from a pc in L.A. configured with the DNS server ipaddress in
> Cinncinati. The remote server we are trying to connect to is in
> Chicago.

I guess what you mean by, "the virtual ip that moves back and forth" is due
to replication (exact copy I presume) of the two servers in different
locations. And it appears you are also saying that the two machines have the
same DNS host name but with two different IPs, one for the corp location and
one for the remote location.

Are you expecting DNS to provide fault tolerance in this scenario if one
were to go down and expect it to go the other? That's not really DNS' job.
That would be an application's job to provide fault tolerance. DNS only
offers load balancing.

See, with multiple IPs to one hostname, DNS uses Round Robin and Netmask
Ordering, depending on the scenario, to give out an IP. This means with a
scenario where a quering client is on one subnet and both IPs of the
hostname in DNS are on the same subnet, it will toggle back and forth for
the response of each query due to Round Robin. However, if the two hostname
IPs are on different subnets, the querying client on a specific subnet will
get the ip of the hostname on it's own subnet due to Netmask Ordering
superceding Round Robin.

Aolso, you didn't exactly specify what type of problem you are seeing when
trying to map, such as, is it asking for credentials, or just saying that
the host or server cannot be found and cannot connect at all.

If the local workstations can connect fine in LA by IP or FQDN, but not to
the remote location by IP or FQDN, then it's hinting at something else going
on, such as possibly blocked ports, especially if the mapping won't connect
by IP. Maybe even worse, depending on how or what you are using to
replicate, that it may be a duplicate SID and the Kerberos ticket expired
and won't renew with the domain because of the dupe SID.

Interesting scenario...

Ace

Ace, is it possible to send you a viso diagram via e-mail ?, it would be
easier to explain.

Netahs
--
cool runnings.


"Ace Fekay [MVP]" wrote:

> In news:001D638B-AFA9-46A0-90F0-A4F9BAB447D4@microsoft.com,
> netahs <netahs@discussions.microsoft.com> stated, which I commented on
> below:
> > Ace, we can map to the physical address of the severs but not to the
> > virtual ip that moves back and forth.Our local headquarters can map
> > just fine in L.A but in Cinncinati it wont connect when we try to map
> > from a pc in L.A. configured with the DNS server ipaddress in
> > Cinncinati. The remote server we are trying to connect to is in
> > Chicago.
>
> I guess what you mean by, "the virtual ip that moves back and forth" is due
> to replication (exact copy I presume) of the two servers in different
> locations. And it appears you are also saying that the two machines have the
> same DNS host name but with two different IPs, one for the corp location and
> one for the remote location.
>
> Are you expecting DNS to provide fault tolerance in this scenario if one
> were to go down and expect it to go the other? That's not really DNS' job.
> That would be an application's job to provide fault tolerance. DNS only
> offers load balancing.
>
> See, with multiple IPs to one hostname, DNS uses Round Robin and Netmask
> Ordering, depending on the scenario, to give out an IP. This means with a
> scenario where a quering client is on one subnet and both IPs of the
> hostname in DNS are on the same subnet, it will toggle back and forth for
> the response of each query due to Round Robin. However, if the two hostname
> IPs are on different subnets, the querying client on a specific subnet will
> get the ip of the hostname on it's own subnet due to Netmask Ordering
> superceding Round Robin.
>
> Aolso, you didn't exactly specify what type of problem you are seeing when
> trying to map, such as, is it asking for credentials, or just saying that
> the host or server cannot be found and cannot connect at all.
>
> If the local workstations can connect fine in LA by IP or FQDN, but not to
> the remote location by IP or FQDN, then it's hinting at something else going
> on, such as possibly blocked ports, especially if the mapping won't connect
> by IP. Maybe even worse, depending on how or what you are using to
> replicate, that it may be a duplicate SID and the Kerberos ticket expired
> and won't renew with the domain because of the dupe SID.
>
> Interesting scenario...
>
> Ace
>
>
>

In news:62AD5F96-F06E-4F24-B67F-CDF0D5E68EB4@microsoft.com,
netahs <netahs@discussions.microsoft.com> stated, which I commented on
below:
> Ace, is it possible to send you a viso diagram via e-mail ?, it would
> be easier to explain.
>
> Netahs

Sure. Send it to:
_ace_fekay_AT_hotmail._comm_

My email address has no underscores in it, so remove all the underscores.

Ace

--
Law N.


"netahs" wrote:

> We have a server located in a remote location on our network that can't be
> mapped to from our Corporate headquarters using the FQDN or ipaddress
> resolved by the corporate DNS server, but from our local headquarters we can
> map just fine using the FQDN or ipaddress resolved by our local DNS server.
> All of our local headquarter servers including our remote servers are
> replicated from our local headquaters to our Corporated headquarters, which
> is having problems mapping.This server is clustered so this FQDN is virtual
> and can floats back and forth in case the server goes down. It is interesting
> that the FQDN and ipaddress of the physical server can be mapped both from
> our Corporate headquarters and our local headquarters.
>
> Can anyone please in diagnosing this issue
>
> Thank You,
>
> Netahs
> --
> cool runnings.

--
Law N.
Have you tried DNS Expert AD to analyize your DNS health. An Evaluation copy
is available from www.menandmice.com. The eval copy is limited to testing 10
functions but the registered version is loaded to test over 100 functions.


"netahs" wrote:

> We have a server located in a remote location on our network that can't be
> mapped to from our Corporate headquarters using the FQDN or ipaddress
> resolved by the corporate DNS server, but from our local headquarters we can
> map just fine using the FQDN or ipaddress resolved by our local DNS server.
> All of our local headquarter servers including our remote servers are
> replicated from our local headquaters to our Corporated headquarters, which
> is having problems mapping.This server is clustered so this FQDN is virtual
> and can floats back and forth in case the server goes down. It is interesting
> that the FQDN and ipaddress of the physical server can be mapped both from
> our Corporate headquarters and our local headquarters.
>
> Can anyone please in diagnosing this issue
>
> Thank You,
>
> Netahs
> --
> cool runnings.