Moving Server to different subnet

I have a Citrix member of domain server currenlty on the local subnet with
the domain controllers, database server that it accesses. I want to move the
server to a differnet subnet with a new IP address but have remain in the
domain. Is this possible and what are the steps involved if so?

Thanks

"Andy1974" <(E-Mail Removed)> wrote in message
news:43C8FCCF-06CC-4C67-9C60-(E-Mail Removed)...
>I have a Citrix member of domain server currenlty on the local subnet with
> the domain controllers, database server that it accesses. I want to move
> the
> server to a differnet subnet with a new IP address but have remain in the
> domain. Is this possible and what are the steps involved if so?

There are no "steps". Just do it.

Domains and subnets have nothing to do with each other,...not even related.

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

I must be thinking of sites then. Will IP address for server on new network
be registered with the DNS server that is on the old network. Name
resolution should not be an issue either?


"Phillip Windell" wrote:

> "Andy1974" <(E-Mail Removed)> wrote in message
> news:43C8FCCF-06CC-4C67-9C60-(E-Mail Removed)...
> >I have a Citrix member of domain server currenlty on the local subnet with
> > the domain controllers, database server that it accesses. I want to move
> > the
> > server to a differnet subnet with a new IP address but have remain in the
> > domain. Is this possible and what are the steps involved if so?
>
> There are no "steps". Just do it.
>
> Domains and subnets have nothing to do with each other,...not even related.
>
> --
> 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.
> -----------------------------------------------------
>
>
>

"Andy1974" <(E-Mail Removed)> wrote in message
news7DB279E-CF09-4413-9651-(E-Mail Removed)...

> I must be thinking of sites then.

Site are only related to Domains in the context of Remote Office Sites
across slow WAN links where the Sites & Subnets Object manage/regulate the
Replication and direct Clients to use DCs in their own site for logins. So
in the end it is still irrelevant to what you are doing.

> Will IP address for server on new network
> be registered with the DNS server that is on the old network.

There is no "new network" and old "network",...it is all one network,...it
just has within it more than one subnet.

If the machine registers itself in DNS when it starts up that is all that
matters. DNS is relative to NameSpaces which is reflected in the Forward
Lookup Zones, not subnets,..subnets are irrelevant to DNS. Now Reverse
Lookup Zones are usually "superneted" to cover all the subnets of a LAN in a
single Zone, so they are only partially related to subnets. But the Reverse
Zones most of the time don't even need to exist in the first place.

Yes I know subnets are sometimes looked at as different "networks", but it
is really a matter of the "context" of what subject you are talking about
and what concepts you are dealing with. In this context you have One
network (the whole LAN) but it consists of more than one subnet within it.

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

I should have been more clear. It is actually a different private IP
network however not a subnet. Two networks are 192.168.0 and 10.2.0.0. Is
this the same scenario as far as what you are describing here for subnets?


"Phillip Windell" wrote:

> "Andy1974" <(E-Mail Removed)> wrote in message
> news7DB279E-CF09-4413-9651-(E-Mail Removed)...
>
> > I must be thinking of sites then.
>
> Site are only related to Domains in the context of Remote Office Sites
> across slow WAN links where the Sites & Subnets Object manage/regulate the
> Replication and direct Clients to use DCs in their own site for logins. So
> in the end it is still irrelevant to what you are doing.
>
> > Will IP address for server on new network
> > be registered with the DNS server that is on the old network.
>
> There is no "new network" and old "network",...it is all one network,...it
> just has within it more than one subnet.
>
> If the machine registers itself in DNS when it starts up that is all that
> matters. DNS is relative to NameSpaces which is reflected in the Forward
> Lookup Zones, not subnets,..subnets are irrelevant to DNS. Now Reverse
> Lookup Zones are usually "superneted" to cover all the subnets of a LAN in a
> single Zone, so they are only partially related to subnets. But the Reverse
> Zones most of the time don't even need to exist in the first place.
>
> Yes I know subnets are sometimes looked at as different "networks", but it
> is really a matter of the "context" of what subject you are talking about
> and what concepts you are dealing with. In this context you have One
> network (the whole LAN) but it consists of more than one subnet within it.
>
> --
> 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.
> -----------------------------------------------------
>
>
>

"Andy1974" <(E-Mail Removed)> wrote in message
news:E281DE3E-6F26-469A-A73C-(E-Mail Removed)...
>
>
> I should have been more clear. It is actually a different private IP
> network however not a subnet. Two networks are 192.168.0 and 10.2.0.0.

Same thing.
Doesn't change anything I said.

If you have a LAN Router sitting between these two "things" then you have a
LAN with multple IP Segments (more accuarte then saying "subnets") and the
LAN Router handles the routing between them.

If there is no LAN Router between them then,..yes,..you need to be a lot
more precise in your description,...nothing we have said up to now means
anything anymore and we are completely back at the beginning.


--
Phillip Windell
www.wandtv.com

There is a router sitting in between the two segments. Actually an Cisco ASA
but it is capable of acting as router between the two segments.

"Phillip Windell" wrote:

> "Andy1974" <(E-Mail Removed)> wrote in message
> news:E281DE3E-6F26-469A-A73C-(E-Mail Removed)...
> >
> >
> > I should have been more clear. It is actually a different private IP
> > network however not a subnet. Two networks are 192.168.0 and 10.2.0.0.
>
> Same thing.
> Doesn't change anything I said.
>
> If you have a LAN Router sitting between these two "things" then you have a
> LAN with multple IP Segments (more accuarte then saying "subnets") and the
> LAN Router handles the routing between them.
>
> If there is no LAN Router between them then,..yes,..you need to be a lot
> more precise in your description,...nothing we have said up to now means
> anything anymore and we are completely back at the beginning.
>
>
> --
> Phillip Windell
> www.wandtv.com
>
>
>

"Andy1974" <(E-Mail Removed)> wrote in message
news:F9C09370-8205-4307-B312-(E-Mail Removed)...
> There is a router sitting in between the two segments. Actually an Cisco
> ASA
> but it is capable of acting as router between the two segments.

Since an ASA is not really a "router" you need to be really really sure that
it is operating as a LAN Router with respect to those two IP Segments.

If it is,..fine.

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

"Andy1974" <(E-Mail Removed)> wrote in message
news:1413C685-5873-4EC6-B01B-(E-Mail Removed)...
> If it is operating as a LAN router than what you had previously said in
> regards to subnets is also true for this scenario?

Yes.
Just move the server and forget it.
The DNS "A"Record for the server (listed in the DNS Server service) should
change to the new IP shortly after the Citrix box boots up.
The Client's cached DNS resolution to the old IP# should expire in about 30
minutes from the last time they had to resolve it.

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

Hello Phillip,

As an addition for the moving keep in mind that the Citrix server has to
contact the Citrix license server and also the database/master server in
the citrix farm.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> "Andy1974" <(E-Mail Removed)> wrote in message
> news:1413C685-5873-4EC6-B01B-(E-Mail Removed)...
>
>> If it is operating as a LAN router than what you had previously said
>> in regards to subnets is also true for this scenario?
>>
> Yes.
> Just move the server and forget it.
> The DNS "A"Record for the server (listed in the DNS Server service)
> should
> change to the new IP shortly after the Citrix box boots up.
> The Client's cached DNS resolution to the old IP# should expire in
> about 30
> minutes from the last time they had to resolve it.
> The views expressed, are my own and not those of my employer, or
> Microsoft, or anyone else associated with me, including my cats.
> -----------------------------------------------------
>