| Author |
Message |
samG
Guest
|
 Posted:
Wed Jan 12, 2005 4:01 am Post subject:
Domain setup |
|
|
Currently running tests on a new server with Win2k3 at home using DHCP for
the network. Need to create a domain controller and run some tests. When
done, the server goes to the office were we run static IP addresses. Will
testing with DHCP create problems when transferring to the office and
changing from DHCP over to static IP ? Would it be better to do this at the
office instead of here at home ?
Thanks
--
samG |
|
| Back to top |
|
 |
Miha Pihler [MVP]
Guest
|
| Posted:
Wed Jan 12, 2005 5:15 am Post subject:
Re: Domain setup |
|
|
Hi,
If your main concern is change of IP address on domain controller then don't
worry. This can be done without any problem.
Once you decide to move your domain controller to new office, change the IP
address of the server and make sure that the server has correct settings for
preferred DNS (settings under TCP/IP properties). Preferred DNS should be
active directory DNS server (probably another active directory server) or
this server itself if the server will also be DNS server. Once all
information is correctly entered (change of IP address and DNS settings),
restart NetLogon service to update DNS entries to reflect IP change.
Now all you have to do is to update your clients in the office to e.g. use
this server and it's new IP address as preferred DNS server.
Feel free to post back if you have any additional questions.
I hope this helps.
--
Mike
Microsoft MVP - Windows Security
"samG" <samG@discussions.microsoft.com> wrote in message
news:8CFAEFBC-80F8-45C0-AC33-9AF8E39BD4AF@microsoft.com...
| Quote: | Currently running tests on a new server with Win2k3 at home using DHCP for
the network. Need to create a domain controller and run some tests. When
done, the server goes to the office were we run static IP addresses. Will
testing with DHCP create problems when transferring to the office and
changing from DHCP over to static IP ? Would it be better to do this at
the
office instead of here at home ?
Thanks
--
samG |
|
|
| Back to top |
|
|
samG
Guest
|
| Posted:
Wed Jan 12, 2005 7:59 am Post subject:
Re: Domain setup |
|
|
Miha:
We are a small bus with 14 users and 2 outdated servers in the main office.
The only reason for the domain is for AD so Exhange Server 2003 will run.
Owners like Exchange Server. The new unit I am testing will replace the 2
current servers. Per the OS Help if using Active Directory Installation
Wizard the Wizard will configure the new server as the local DNS server. If
this is so, I would expect it to happen since the IP and DNS ID's are
supplied by my router. Our ISP provides us with the static IP and the 2 DNS
ID's. Our current server uses these and so does our workstations, but our
workstations do not go through the server to access the internet. We bypass
the server on purpose due to previous server problems which shut us down a
number of times. 98% of our vendors are online, thus the need to have access
(providing the freak'n DSL doesn't go down} regardless of the servers. When
I put the new unit in I will use the ISP's DNS numbers. Exhange doesn't
really use them, but required if we ever use IE to go online.
Thanks for the help.
Sam
"Miha Pihler [MVP]" wrote:
| Quote: | Hi,
If your main concern is change of IP address on domain controller then don't
worry. This can be done without any problem.
Once you decide to move your domain controller to new office, change the IP
address of the server and make sure that the server has correct settings for
preferred DNS (settings under TCP/IP properties). Preferred DNS should be
active directory DNS server (probably another active directory server) or
this server itself if the server will also be DNS server. Once all
information is correctly entered (change of IP address and DNS settings),
restart NetLogon service to update DNS entries to reflect IP change.
Now all you have to do is to update your clients in the office to e.g. use
this server and it's new IP address as preferred DNS server.
Feel free to post back if you have any additional questions.
I hope this helps.
--
Mike
Microsoft MVP - Windows Security
"samG" <samG@discussions.microsoft.com> wrote in message
news:8CFAEFBC-80F8-45C0-AC33-9AF8E39BD4AF@microsoft.com...
Currently running tests on a new server with Win2k3 at home using DHCP for
the network. Need to create a domain controller and run some tests. When
done, the server goes to the office were we run static IP addresses. Will
testing with DHCP create problems when transferring to the office and
changing from DHCP over to static IP ? Would it be better to do this at
the
office instead of here at home ?
Thanks
--
samG
|
|
|
| Back to top |
|
|
Miha Pihler [MVP]
Guest
|
| Posted:
Wed Jan 12, 2005 3:22 pm Post subject:
Re: Domain setup |
|
|
Hi Sam,
Active Directory and everything around it (Exchange and domain clients) rely
heavily on _active directory_ DNS. Clients use DNS to find domain
controllers, global catalogs and other services in domain. If you will use
your ISP DNS on your clients then clients will fail to find these services.
Problems that can happen are e.g. clients won't be able to join the domain,
long logon times, ...
Usual scenario is to setup your active directory DNS (e.g. on your domain
controller) and point your clients to this DNS for preferred DNS. Even your
DC will have to point to this active directory DNS or again you could run
into problems.
Once this is set up, you can configure Forwarders on your active directory
DNS server. This will enable your clients to find servers on the internet.
You can use your ISP DNS servers for forwarders.
Feel free to post back if you have any additional questions.
--
Mike
Microsoft MVP - Windows Security
"samG" <samG@discussions.microsoft.com> wrote in message
news:B08C9105-A504-4FA5-964A-635337FDB480@microsoft.com...
| Quote: | Miha:
We are a small bus with 14 users and 2 outdated servers in the main
office.
The only reason for the domain is for AD so Exhange Server 2003 will run.
Owners like Exchange Server. The new unit I am testing will replace the 2
current servers. Per the OS Help if using Active Directory Installation
Wizard the Wizard will configure the new server as the local DNS server.
If
this is so, I would expect it to happen since the IP and DNS ID's are
supplied by my router. Our ISP provides us with the static IP and the 2
DNS
ID's. Our current server uses these and so does our workstations, but our
workstations do not go through the server to access the internet. We
bypass
the server on purpose due to previous server problems which shut us down a
number of times. 98% of our vendors are online, thus the need to have
access
(providing the freak'n DSL doesn't go down} regardless of the servers.
When
I put the new unit in I will use the ISP's DNS numbers. Exhange doesn't
really use them, but required if we ever use IE to go online.
Thanks for the help.
Sam
"Miha Pihler [MVP]" wrote:
Hi,
If your main concern is change of IP address on domain controller then
don't
worry. This can be done without any problem.
Once you decide to move your domain controller to new office, change the
IP
address of the server and make sure that the server has correct settings
for
preferred DNS (settings under TCP/IP properties). Preferred DNS should be
active directory DNS server (probably another active directory server) or
this server itself if the server will also be DNS server. Once all
information is correctly entered (change of IP address and DNS settings),
restart NetLogon service to update DNS entries to reflect IP change.
Now all you have to do is to update your clients in the office to e.g.
use
this server and it's new IP address as preferred DNS server.
Feel free to post back if you have any additional questions.
I hope this helps.
--
Mike
Microsoft MVP - Windows Security
"samG" <samG@discussions.microsoft.com> wrote in message
news:8CFAEFBC-80F8-45C0-AC33-9AF8E39BD4AF@microsoft.com...
Currently running tests on a new server with Win2k3 at home using DHCP
for
the network. Need to create a domain controller and run some tests.
When
done, the server goes to the office were we run static IP addresses.
Will
testing with DHCP create problems when transferring to the office and
changing from DHCP over to static IP ? Would it be better to do this
at
the
office instead of here at home ?
Thanks
--
samG
|
|
|
| Back to top |
|
|
samG
Guest
|
| Posted:
Wed Jan 12, 2005 5:59 pm Post subject:
Re: Domain setup |
|
|
Thanks Miha for your help.
Sam
"Miha Pihler [MVP]" wrote:
| Quote: | Hi Sam,
Active Directory and everything around it (Exchange and domain clients) rely
heavily on _active directory_ DNS. Clients use DNS to find domain
controllers, global catalogs and other services in domain. If you will use
your ISP DNS on your clients then clients will fail to find these services.
Problems that can happen are e.g. clients won't be able to join the domain,
long logon times, ...
Usual scenario is to setup your active directory DNS (e.g. on your domain
controller) and point your clients to this DNS for preferred DNS. Even your
DC will have to point to this active directory DNS or again you could run
into problems.
Once this is set up, you can configure Forwarders on your active directory
DNS server. This will enable your clients to find servers on the internet.
You can use your ISP DNS servers for forwarders.
Feel free to post back if you have any additional questions.
--
Mike
Microsoft MVP - Windows Security
"samG" <samG@discussions.microsoft.com> wrote in message
news:B08C9105-A504-4FA5-964A-635337FDB480@microsoft.com...
Miha:
We are a small bus with 14 users and 2 outdated servers in the main
office.
The only reason for the domain is for AD so Exhange Server 2003 will run.
Owners like Exchange Server. The new unit I am testing will replace the 2
current servers. Per the OS Help if using Active Directory Installation
Wizard the Wizard will configure the new server as the local DNS server.
If
this is so, I would expect it to happen since the IP and DNS ID's are
supplied by my router. Our ISP provides us with the static IP and the 2
DNS
ID's. Our current server uses these and so does our workstations, but our
workstations do not go through the server to access the internet. We
bypass
the server on purpose due to previous server problems which shut us down a
number of times. 98% of our vendors are online, thus the need to have
access
(providing the freak'n DSL doesn't go down} regardless of the servers.
When
I put the new unit in I will use the ISP's DNS numbers. Exhange doesn't
really use them, but required if we ever use IE to go online.
Thanks for the help.
Sam
"Miha Pihler [MVP]" wrote:
Hi,
If your main concern is change of IP address on domain controller then
don't
worry. This can be done without any problem.
Once you decide to move your domain controller to new office, change the
IP
address of the server and make sure that the server has correct settings
for
preferred DNS (settings under TCP/IP properties). Preferred DNS should be
active directory DNS server (probably another active directory server) or
this server itself if the server will also be DNS server. Once all
information is correctly entered (change of IP address and DNS settings),
restart NetLogon service to update DNS entries to reflect IP change.
Now all you have to do is to update your clients in the office to e.g.
use
this server and it's new IP address as preferred DNS server.
Feel free to post back if you have any additional questions.
I hope this helps.
--
Mike
Microsoft MVP - Windows Security
"samG" <samG@discussions.microsoft.com> wrote in message
news:8CFAEFBC-80F8-45C0-AC33-9AF8E39BD4AF@microsoft.com...
Currently running tests on a new server with Win2k3 at home using DHCP
for
the network. Need to create a domain controller and run some tests.
When
done, the server goes to the office were we run static IP addresses.
Will
testing with DHCP create problems when transferring to the office and
changing from DHCP over to static IP ? Would it be better to do this
at
the
office instead of here at home ?
Thanks
--
samG
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in