Printable View
Is there a domain controller update for windows server 2003 r2 standard
edition that helps with slow boot up process. It takes up to 8 minutes to get
to the login
screen. Sometimes it just gets stuck on preparing network connections and you
have to hold down the power button to power off the server and then it will
boot up in 8 minutes usually the second time
Jason wrote:
> Is there a domain controller update for windows server 2003 r2
> standard edition that helps with slow boot up process. It takes up to
> 8 minutes to get to the login
> screen. Sometimes it just gets stuck on preparing network connections
> and you have to hold down the power button to power off the server
> and then it will boot up in 8 minutes usually the second time
Yikes. A dangerous road with the power button.
Often this is a DNS configuration issues especially with only one domain
controller.
Suggest you post results of IPconfig/all, let us know service pack level and
your AD forest / domain configuration.
--
/kj
Windows IP Configuration
Host Name . . . . . . . . . . . . : pharmacyserver
Primary Dns Suffix . . . . . . . : bvpharmacy.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : bvpharmacy.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
10/100/1000B
ase-T Adapter
Physical Address. . . . . . . . . : 00-17-31-4D-AF-9A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 68.94.156.1
151.164.8.201
"kj [SBS MVP]" wrote:
> Jason wrote:
> > Is there a domain controller update for windows server 2003 r2
> > standard edition that helps with slow boot up process. It takes up to
> > 8 minutes to get to the login
> > screen. Sometimes it just gets stuck on preparing network connections
> > and you have to hold down the power button to power off the server
> > and then it will boot up in 8 minutes usually the second time
>
> Yikes. A dangerous road with the power button.
>
> Often this is a DNS configuration issues especially with only one domain
> controller.
>
> Suggest you post results of IPconfig/all, let us know service pack level and
> your AD forest / domain configuration.
>
>
>
> --
> /kj
>
>
>
Jason wrote:
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : pharmacyserver
> Primary Dns Suffix . . . . . . . : bvpharmacy.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : bvpharmacy.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
> 10/100/1000B
> ase-T Adapter
> Physical Address. . . . . . . . . : 00-17-31-4D-AF-9A
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.16
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.254
> DNS Servers . . . . . . . . . . . : 68.94.156.1
> 151.164.8.201
>
Your AD domain controllers should be running DNS (AD Integrated) and should
have the DNS clients configured to use ONLY AD DC/DNS servers.
Your DC is configured to use ISP DNS servers and therefore are unable to
locate the Active Directory DNS zone. Change to use 192.168.1.16 for the;
> DNS Servers . . . . . . . . . . . : 68.94.156.1
> 151.164.8.201
and remove the ISP's ( You can configure your AD/DC DNS server to foreward
to these ISP DNS servers for Internet resolution or use root hints by
personal preference.
This is what is causing your slow boot up.
>
> "kj [SBS MVP]" wrote:
>
>> Jason wrote:
>>> Is there a domain controller update for windows server 2003 r2
>>> standard edition that helps with slow boot up process. It takes up
>>> to 8 minutes to get to the login
>>> screen. Sometimes it just gets stuck on preparing network
>>> connections and you have to hold down the power button to power off
>>> the server and then it will boot up in 8 minutes usually the second
>>> time
>>
>> Yikes. A dangerous road with the power button.
>>
>> Often this is a DNS configuration issues especially with only one
>> domain controller.
>>
>> Suggest you post results of IPconfig/all, let us know service pack
>> level and your AD forest / domain configuration.
>>
>>
>>
>> --
>> /kj
--
/kj
Ok so does that mean I need to change the primary and secondary dns #'s to
192.168.1.16? or am I just totally confussed on this.
"kj [SBS MVP]" wrote:
> Jason wrote:
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : pharmacyserver
> > Primary Dns Suffix . . . . . . . : bvpharmacy.local
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : bvpharmacy.local
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
> > 10/100/1000B
> > ase-T Adapter
> > Physical Address. . . . . . . . . : 00-17-31-4D-AF-9A
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.16
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.254
> > DNS Servers . . . . . . . . . . . : 68.94.156.1
> > 151.164.8.201
> >
>
> Your AD domain controllers should be running DNS (AD Integrated) and should
> have the DNS clients configured to use ONLY AD DC/DNS servers.
>
> Your DC is configured to use ISP DNS servers and therefore are unable to
> locate the Active Directory DNS zone. Change to use 192.168.1.16 for the;
>
> > DNS Servers . . . . . . . . . . . : 68.94.156.1
> > 151.164.8.201
>
> and remove the ISP's ( You can configure your AD/DC DNS server to foreward
> to these ISP DNS servers for Internet resolution or use root hints by
> personal preference.
>
> This is what is causing your slow boot up.
>
>
>
>
> >
> > "kj [SBS MVP]" wrote:
> >
> >> Jason wrote:
> >>> Is there a domain controller update for windows server 2003 r2
> >>> standard edition that helps with slow boot up process. It takes up
> >>> to 8 minutes to get to the login
> >>> screen. Sometimes it just gets stuck on preparing network
> >>> connections and you have to hold down the power button to power off
> >>> the server and then it will boot up in 8 minutes usually the second
> >>> time
> >>
> >> Yikes. A dangerous road with the power button.
> >>
> >> Often this is a DNS configuration issues especially with only one
> >> domain controller.
> >>
> >> Suggest you post results of IPconfig/all, let us know service pack
> >> level and your AD forest / domain configuration.
> >>
> >>
> >>
> >> --
> >> /kj
>
> --
> /kj
>
>
>
Jason wrote:
> Ok so does that mean I need to change the primary and secondary dns
> #'s to 192.168.1.16? or am I just totally confussed on this.
If you have only one AD/DC then configure only the primary to 1.16, remove
the secondary coimpletely.
Add the ISP servers as DNS forwarders in the DNS console.
>
> "kj [SBS MVP]" wrote:
>
>> Jason wrote:
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : pharmacyserver
>>> Primary Dns Suffix . . . . . . . : bvpharmacy.local
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : Yes
>>> WINS Proxy Enabled. . . . . . . . : Yes
>>> DNS Suffix Search List. . . . . . : bvpharmacy.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
>>> 10/100/1000B
>>> ase-T Adapter
>>> Physical Address. . . . . . . . . : 00-17-31-4D-AF-9A
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.16
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.254
>>> DNS Servers . . . . . . . . . . . : 68.94.156.1
>>> 151.164.8.201
>>>
>>
>> Your AD domain controllers should be running DNS (AD Integrated) and
>> should have the DNS clients configured to use ONLY AD DC/DNS servers.
>>
>> Your DC is configured to use ISP DNS servers and therefore are
>> unable to locate the Active Directory DNS zone. Change to use
>> 192.168.1.16 for the;
>>
>>> DNS Servers . . . . . . . . . . . : 68.94.156.1
>>> 151.164.8.201
>>
>> and remove the ISP's ( You can configure your AD/DC DNS server to
>> foreward to these ISP DNS servers for Internet resolution or use
>> root hints by personal preference.
>>
>> This is what is causing your slow boot up.
>>
>>
>>
>>
>>>
>>> "kj [SBS MVP]" wrote:
>>>
>>>> Jason wrote:
>>>>> Is there a domain controller update for windows server 2003 r2
>>>>> standard edition that helps with slow boot up process. It takes up
>>>>> to 8 minutes to get to the login
>>>>> screen. Sometimes it just gets stuck on preparing network
>>>>> connections and you have to hold down the power button to power
>>>>> off the server and then it will boot up in 8 minutes usually the
>>>>> second time
>>>>
>>>> Yikes. A dangerous road with the power button.
>>>>
>>>> Often this is a DNS configuration issues especially with only one
>>>> domain controller.
>>>>
>>>> Suggest you post results of IPconfig/all, let us know service pack
>>>> level and your AD forest / domain configuration.
>>>>
>>>>
>>>>
>>>> --
>>>> /kj
>>
>> --
>> /kj
--
/kj
Jason wrote:
> Ok so does that mean I need to change the primary and secondary dns
> #'s to 192.168.1.16? or am I just totally confussed on this.
additionaly see;
http://www.microsoft.com/technet/com...d/tnti-35.mspx
>
> "kj [SBS MVP]" wrote:
>
>> Jason wrote:
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : pharmacyserver
>>> Primary Dns Suffix . . . . . . . : bvpharmacy.local
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : Yes
>>> WINS Proxy Enabled. . . . . . . . : Yes
>>> DNS Suffix Search List. . . . . . : bvpharmacy.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
>>> 10/100/1000B
>>> ase-T Adapter
>>> Physical Address. . . . . . . . . : 00-17-31-4D-AF-9A
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.16
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.254
>>> DNS Servers . . . . . . . . . . . : 68.94.156.1
>>> 151.164.8.201
>>>
>>
>> Your AD domain controllers should be running DNS (AD Integrated) and
>> should have the DNS clients configured to use ONLY AD DC/DNS servers.
>>
>> Your DC is configured to use ISP DNS servers and therefore are
>> unable to locate the Active Directory DNS zone. Change to use
>> 192.168.1.16 for the;
>>
>>> DNS Servers . . . . . . . . . . . : 68.94.156.1
>>> 151.164.8.201
>>
>> and remove the ISP's ( You can configure your AD/DC DNS server to
>> foreward to these ISP DNS servers for Internet resolution or use
>> root hints by personal preference.
>>
>> This is what is causing your slow boot up.
>>
>>
>>
>>
>>>
>>> "kj [SBS MVP]" wrote:
>>>
>>>> Jason wrote:
>>>>> Is there a domain controller update for windows server 2003 r2
>>>>> standard edition that helps with slow boot up process. It takes up
>>>>> to 8 minutes to get to the login
>>>>> screen. Sometimes it just gets stuck on preparing network
>>>>> connections and you have to hold down the power button to power
>>>>> off the server and then it will boot up in 8 minutes usually the
>>>>> second time
>>>>
>>>> Yikes. A dangerous road with the power button.
>>>>
>>>> Often this is a DNS configuration issues especially with only one
>>>> domain controller.
>>>>
>>>> Suggest you post results of IPconfig/all, let us know service pack
>>>> level and your AD forest / domain configuration.
>>>>
>>>>
>>>>
>>>> --
>>>> /kj
>>
>> --
>> /kj
--
/kj
You should only have internal DNS servers specified in the DNS settings.
As kj has said, external DNS servers belong in the forwarders section of
the DNS server setup.
On a server that is also a DNS server, I usually put the server's IP
address in the primary address. If you have additional DNS servers, put
one in the secondary server location.
On other servers (that are not DNS servers) and workstations, set the
primary and secondary addresses to different DNS server IP addresses. If
you only have one DNS server, then put it in the primary location and
leave the secondary blank.
--
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
Jason wrote:
> Ok so does that mean I need to change the primary and secondary dns #'s to
> 192.168.1.16? or am I just totally confussed on this.
>
> "kj [SBS MVP]" wrote:
>
>> Jason wrote:
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : pharmacyserver
>>> Primary Dns Suffix . . . . . . . : bvpharmacy.local
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : Yes
>>> WINS Proxy Enabled. . . . . . . . : Yes
>>> DNS Suffix Search List. . . . . . : bvpharmacy.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
>>> 10/100/1000B
>>> ase-T Adapter
>>> Physical Address. . . . . . . . . : 00-17-31-4D-AF-9A
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.1.16
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.254
>>> DNS Servers . . . . . . . . . . . : 68.94.156.1
>>> 151.164.8.201
>>>
>> Your AD domain controllers should be running DNS (AD Integrated) and should
>> have the DNS clients configured to use ONLY AD DC/DNS servers.
>>
>> Your DC is configured to use ISP DNS servers and therefore are unable to
>> locate the Active Directory DNS zone. Change to use 192.168.1.16 for the;
>>
>>> DNS Servers . . . . . . . . . . . : 68.94.156.1
>>> 151.164.8.201
>> and remove the ISP's ( You can configure your AD/DC DNS server to foreward
>> to these ISP DNS servers for Internet resolution or use root hints by
>> personal preference.
>>
>> This is what is causing your slow boot up.
>>
>>
>>
>>
>>> "kj [SBS MVP]" wrote:
>>>
>>>> Jason wrote:
>>>>> Is there a domain controller update for windows server 2003 r2
>>>>> standard edition that helps with slow boot up process. It takes up
>>>>> to 8 minutes to get to the login
>>>>> screen. Sometimes it just gets stuck on preparing network
>>>>> connections and you have to hold down the power button to power off
>>>>> the server and then it will boot up in 8 minutes usually the second
>>>>> time
>>>> Yikes. A dangerous road with the power button.
>>>>
>>>> Often this is a DNS configuration issues especially with only one
>>>> domain controller.
>>>>
>>>> Suggest you post results of IPconfig/all, let us know service pack
>>>> level and your AD forest / domain configuration.
>>>>
>>>>
>>>>
>>>> --
>>>> /kj
>> --
>> /kj
>>
>>
>>