Assign a Win2003 server with a remote IP address in a different su

[Guest MatriX]

Hi all,

 

I am building up a new server for our remote office. The remote office have

an address of 172.19.2.X. This server will be promoted to Active Directory

and Global Catalog. I like to build the server in-house (HQ) and do all

configurations and promote the server with the remote office IP address, when

done shipped to that office. The problem is, HQ has a different IP address,

vLAN and gateway. Question is and if possible, how do I make it work by

assigning the same IP address as the remote office as well as the subnet and

gateway? By assigning the remote office ip address, i cannot ping HQ network

and the server that I assign with the remote office address.

 

Please help. Thank you.

 

--

MatriX

[Guest Meinolf Weber]

Re: Assign a Win2003 server with a remote IP address in a different su

 

Hello MatriX,

 

No need for the remote ip. Just install it in the main network completely,

after everything is running and checked with dcdiag/v, netdiag /v and repadmin

/showreps, change the ip settings to the remote subnet and shutdown the server.

After restarting in the remote office, start with pinging to main office

via ip address, computername and FQDN. If this is running fine, check again

with dcdiag, netdiag and repadmin for errors.

If you still will use the remote ip you have to add a router in the main

network and simulate on this way the remote network.

 

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

> Hi all,

>

> I am building up a new server for our remote office. The remote

> office have an address of 172.19.2.X. This server will be promoted to

> Active Directory and Global Catalog. I like to build the server

> in-house (HQ) and do all configurations and promote the server with

> the remote office IP address, when done shipped to that office. The

> problem is, HQ has a different IP address, vLAN and gateway. Question

> is and if possible, how do I make it work by assigning the same IP

> address as the remote office as well as the subnet and gateway? By

> assigning the remote office ip address, i cannot ping HQ network and

> the server that I assign with the remote office address.

>

> Please help. Thank you.

>

[Guest MatriX]

Re: Assign a Win2003 server with a remote IP address in a differen

 

Re: Assign a Win2003 server with a remote IP address in a differen

 

Hi Meinolf Weber,

 

Thank you.

The remote office has its own dedicated lan setup already. So, I can just

promote the server in-house with the server name and ip address. Once that

is all taken care of. I can just ship the server to that office. Once there,

I match the TCP/IP setting to match that office, right? How about the, AD

sites and services, do I just need to move it to that site and correspond the

subnet address to that remote office location?

 

Thanks.

 

--

MatriX

 

 

"Meinolf Weber" wrote:

> Hello MatriX,

>

> No need for the remote ip. Just install it in the main network completely,

> after everything is running and checked with dcdiag/v, netdiag /v and repadmin

> /showreps, change the ip settings to the remote subnet and shutdown the server.

> After restarting in the remote office, start with pinging to main office

> via ip address, computername and FQDN. If this is running fine, check again

> with dcdiag, netdiag and repadmin for errors.

> If you still will use the remote ip you have to add a router in the main

> network and simulate on this way the remote network.

>

> 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

>

> > Hi all,

> >

> > I am building up a new server for our remote office. The remote

> > office have an address of 172.19.2.X. This server will be promoted to

> > Active Directory and Global Catalog. I like to build the server

> > in-house (HQ) and do all configurations and promote the server with

> > the remote office IP address, when done shipped to that office. The

> > problem is, HQ has a different IP address, vLAN and gateway. Question

> > is and if possible, how do I make it work by assigning the same IP

> > address as the remote office as well as the subnet and gateway? By

> > assigning the remote office ip address, i cannot ping HQ network and

> > the server that I assign with the remote office address.

> >

> > Please help. Thank you.

> >

>

>

>

[Guest Meinolf Weber]

Re: Assign a Win2003 server with a remote IP address in a differen

 

Re: Assign a Win2003 server with a remote IP address in a differen

 

Hello MatriX,

 

Yes, i forget the ADSS, when you have configured the new ip for remote site

and shutdown, also move the dc to the respective subnet in ADSS. If you then

startup the server the basics should be correct.

 

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

> Hi Meinolf Weber,

>

> Thank you.

> The remote office has its own dedicated lan setup already. So, I can

> just

> promote the server in-house with the server name and ip address. Once

> that

> is all taken care of. I can just ship the server to that office. Once

> there,

> I match the TCP/IP setting to match that office, right? How about

> the, AD

> sites and services, do I just need to move it to that site and

> correspond the

> subnet address to that remote office location?

> Thanks.

>

> "Meinolf Weber" wrote:

>

>> Hello MatriX,

>>

>> No need for the remote ip. Just install it in the main network

>> completely,

>> after everything is running and checked with dcdiag/v, netdiag /v and

>> repadmin

>> /showreps, change the ip settings to the remote subnet and shutdown

>> the server.

>> After restarting in the remote office, start with pinging to main

>> office

>> via ip address, computername and FQDN. If this is running fine, check

>> again

>> with dcdiag, netdiag and repadmin for errors.

>> If you still will use the remote ip you have to add a router in the

>> main

>> network and simulate on this way the remote network.

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

>>> Hi all,

>>>

>>> I am building up a new server for our remote office. The remote

>>> office have an address of 172.19.2.X. This server will be promoted

>>> to Active Directory and Global Catalog. I like to build the server

>>> in-house (HQ) and do all configurations and promote the server with

>>> the remote office IP address, when done shipped to that office. The

>>> problem is, HQ has a different IP address, vLAN and gateway.

>>> Question is and if possible, how do I make it work by assigning the

>>> same IP address as the remote office as well as the subnet and

>>> gateway? By assigning the remote office ip address, i cannot ping

>>> HQ network and the server that I assign with the remote office

>>> address.

>>>

>>> Please help. Thank you.

>>>

[Guest MatriX]

Re: Assign a Win2003 server with a remote IP address in a differen

 

Re: Assign a Win2003 server with a remote IP address in a differen

 

Thank you. Looks straight forward to me now.

 

--

MatriX

 

 

"Meinolf Weber" wrote:

> Hello MatriX,

>

> Yes, i forget the ADSS, when you have configured the new ip for remote site

> and shutdown, also move the dc to the respective subnet in ADSS. If you then

> startup the server the basics should be correct.

>

> 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

>

> > Hi Meinolf Weber,

> >

> > Thank you.

> > The remote office has its own dedicated lan setup already. So, I can

> > just

> > promote the server in-house with the server name and ip address. Once

> > that

> > is all taken care of. I can just ship the server to that office. Once

> > there,

> > I match the TCP/IP setting to match that office, right? How about

> > the, AD

> > sites and services, do I just need to move it to that site and

> > correspond the

> > subnet address to that remote office location?

> > Thanks.

> >

> > "Meinolf Weber" wrote:

> >

> >> Hello MatriX,

> >>

> >> No need for the remote ip. Just install it in the main network

> >> completely,

> >> after everything is running and checked with dcdiag/v, netdiag /v and

> >> repadmin

> >> /showreps, change the ip settings to the remote subnet and shutdown

> >> the server.

> >> After restarting in the remote office, start with pinging to main

> >> office

> >> via ip address, computername and FQDN. If this is running fine, check

> >> again

> >> with dcdiag, netdiag and repadmin for errors.

> >> If you still will use the remote ip you have to add a router in the

> >> main

> >> network and simulate on this way the remote network.

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

> >>> Hi all,

> >>>

> >>> I am building up a new server for our remote office. The remote

> >>> office have an address of 172.19.2.X. This server will be promoted

> >>> to Active Directory and Global Catalog. I like to build the server

> >>> in-house (HQ) and do all configurations and promote the server with

> >>> the remote office IP address, when done shipped to that office. The

> >>> problem is, HQ has a different IP address, vLAN and gateway.

> >>> Question is and if possible, how do I make it work by assigning the

> >>> same IP address as the remote office as well as the subnet and

> >>> gateway? By assigning the remote office ip address, i cannot ping

> >>> HQ network and the server that I assign with the remote office

> >>> address.

> >>>

> >>> Please help. Thank you.

> >>>

>

>

>

[Guest Meinolf Weber]

Re: Assign a Win2003 server with a remote IP address in a differen

 

Re: Assign a Win2003 server with a remote IP address in a differen

 

Hello MatriX,

 

Wait for your feedback, how it is going on.:-)

 

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

> Thank you. Looks straight forward to me now.

>

> "Meinolf Weber" wrote:

>

>> Hello MatriX,

>>

>> Yes, i forget the ADSS, when you have configured the new ip for

>> remote site and shutdown, also move the dc to the respective subnet

>> in ADSS. If you then startup the server the basics should be correct.

>>

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

>>> Hi Meinolf Weber,

>>>

>>> Thank you.

>>> The remote office has its own dedicated lan setup already. So, I can

>>> just

>>> promote the server in-house with the server name and ip address.

>>> Once

>>> that

>>> is all taken care of. I can just ship the server to that office.

>>> Once

>>> there,

>>> I match the TCP/IP setting to match that office, right? How about

>>> the, AD

>>> sites and services, do I just need to move it to that site and

>>> correspond the

>>> subnet address to that remote office location?

>>> Thanks.

>>> "Meinolf Weber" wrote:

>>>

>>>> Hello MatriX,

>>>>

>>>> No need for the remote ip. Just install it in the main network

>>>> completely,

>>>> after everything is running and checked with dcdiag/v, netdiag /v

>>>> and

>>>> repadmin

>>>> /showreps, change the ip settings to the remote subnet and shutdown

>>>> the server.

>>>> After restarting in the remote office, start with pinging to main

>>>> office

>>>> via ip address, computername and FQDN. If this is running fine,

>>>> check

>>>> again

>>>> with dcdiag, netdiag and repadmin for errors.

>>>> If you still will use the remote ip you have to add a router in the

>>>> main

>>>> network and simulate on this way the remote network.

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

>>>>> Hi all,

>>>>>

>>>>> I am building up a new server for our remote office. The remote

>>>>> office have an address of 172.19.2.X. This server will be

>>>>> promoted to Active Directory and Global Catalog. I like to build

>>>>> the server in-house (HQ) and do all configurations and promote the

>>>>> server with the remote office IP address, when done shipped to

>>>>> that office. The problem is, HQ has a different IP address, vLAN

>>>>> and gateway. Question is and if possible, how do I make it work by

>>>>> assigning the same IP address as the remote office as well as the

>>>>> subnet and gateway? By assigning the remote office ip address, i

>>>>> cannot ping HQ network and the server that I assign with the

>>>>> remote office address.

>>>>>

>>>>> Please help. Thank you.

>>>>>