"Chetan" <chetan.ka***@gmail.com> wrote in message
news:1139470018.180398.304590@g43g2000cwa.googlegroups.com...
> Hi,
>
> I am facing problem on a User Login.
> When a user login on domain account or local account on a Windows 2000
> professional machine it takes very long (10-15minutes) to loggon.
> machine is a part of Single Domain Enviornment.
>
> What can be the problem as System is Original IBM Desktop withPp-IV
> 2.8gz processor and 1GB RAM. Software loaded are limited only
> Office2003,Adobe Acrobat, etc
>
>
>
> Thanks
> CK-NET
>

"Chetan" <chetan.ka***@gmail.com> wrote in message
news:1139551244.099011.192350@g47g2000cwa.googlegroups.com...
> Yes it is i have DNS on DC and its the first dns server in list.
>
> If i do Nslookup it shows same DNS as i mentio before.
>
> CK-NET
>

"Chetan" <chetan.ka***@gmail.com> wrote in message
news:1139552264.415690.306950@g14g2000cwa.googlegroups.com...
>
> Yes Secondary DNS is ISP's DNS
>
> We have Static IP scheme instaed of DHCP.
>
> And in DNS MMC Domain Name is spelled correctly
>
> CK-NET
>

"Chetan" <chetan.ka***@gmail.com> wrote in message
news:1139573042.480745.241460@g14g2000cwa.googlegroups.com...
> Thanks
> I done that too but it doesnt work
>

"Cary Shultz" <cwshu***@mvps.org> wrote in message
news:uS5P1DkLGHA.2036@TK2MSFTNGP14.phx.gbl...
> Okay,
>
> Let's summarize what is going on here:
>
> You had it such that the secondary DNS information was the IP Address of
> your ISP's DNS Server.  This was on both the Domain Controller and on all
> client workstations.  This information is set statically.  You changed the
> ISP information (is there another Domain Controller in your environment?).
> Now, by changing it does that mean that you removed it or that you entered
> in the IP Address of another DNS Server?  The name in your forward lookup
> zone matches exactly the name of your internal domain.
>
> You have rebooted all of the systems.  Another way would have been to do
> the following at a command prompt on each system:
>
> net stop netlogon
> ipconfig /flushdns
> ipconfig /registerdns
> net start netlogon
>
> This has not resolved anything?
>
> What happens if you use nslookup?  What does that tell you?
>
> Are you able to get to the Internet once you do finally connect?
>
> Do you have all of the subfolders in the FLZ?  Those would be _sites,
> _tcp, _udp and _msdcs.  And all of the records are there?
> What happens if you install the Support Tools and use dcdaig /v and
> netdiag /v?  What is the output from each of those?
>
> --
> Cary W. Shultz
> Roanoke, VA  24012
>
> "Chetan" <chetan.ka***@gmail.com> wrote in message
> news:1139573042.480745.241460@g14g2000cwa.googlegroups.com...
>> Thanks
>> I done that too but it doesnt work
>>
>
>

"Cary Shultz" <cwshu***@mvps.org> wrote in message
news:uULSVKkLGHA.1676@TK2MSFTNGP09.phx.gbl...
> Oh,
>
> And let's make sure that your domain is not a single-label domain
> (mydomain instead of mydomain.com) and let's make sure that you do not
> have a dual-homed situation (where the Domain Controller has two working
> network cards).
>
> --
> Cary W. Shultz
> Roanoke, VA  24012
>
> "Cary Shultz" <cwshu***@mvps.org> wrote in message
> news:uS5P1DkLGHA.2036@TK2MSFTNGP14.phx.gbl...
>> Okay,
>>
>> Let's summarize what is going on here:
>>
>> You had it such that the secondary DNS information was the IP Address of
>> your ISP's DNS Server.  This was on both the Domain Controller and on all
>> client workstations.  This information is set statically.  You changed
>> the ISP information (is there another Domain Controller in your
>> environment?). Now, by changing it does that mean that you removed it or
>> that you entered in the IP Address of another DNS Server?  The name in
>> your forward lookup zone matches exactly the name of your internal
>> domain.
>>
>> You have rebooted all of the systems.  Another way would have been to do
>> the following at a command prompt on each system:
>>
>> net stop netlogon
>> ipconfig /flushdns
>> ipconfig /registerdns
>> net start netlogon
>>
>> This has not resolved anything?
>>
>> What happens if you use nslookup?  What does that tell you?
>>
>> Are you able to get to the Internet once you do finally connect?
>>
>> Do you have all of the subfolders in the FLZ?  Those would be _sites,
>> _tcp, _udp and _msdcs.  And all of the records are there?
>> What happens if you install the Support Tools and use dcdaig /v and
>> netdiag /v?  What is the output from each of those?
>>
>> --
>> Cary W. Shultz
>> Roanoke, VA  24012
>>
>> "Chetan" <chetan.ka***@gmail.com> wrote in message
>> news:1139573042.480745.241460@g14g2000cwa.googlegroups.com...
>>> Thanks
>>> I done that too but it doesnt work
>>>
>>
>>
>
>

"Paul Bergson" <pbergson@allete_nospam.com> wrote in message
news:%23r2jfikLGHA.1288@TK2MSFTNGP09.phx.gbl...
> Also let run diagnostics against the domain and see if there are any
> lingering issues you may not be aware of.
>
> Running diagnostics against your Active Directory domain.
>
> If you don't have the tools installed, install them from your server
> install disk.
> d:\support\tools\setup.exe
>
> Run dcdiag and netdiag in verbose mode.
>
> If you download a gui script I wrote it should be simple to set and run.
> It also has the option to run individual tests without having to learn all
> the switch options.  The details will be output in notepad text files that
> pop up automagically.
>
> The script is located in the download section on my website at
> http://pbbergs.dynu.com/windows
>
> Just select both dcdiag and netdiag make sure verbose is set.  (Leave the
> default settings for dcdiag as set when selected)
>
> When complete search for fail, error and warning messages.
>
>
> --
>
> Paul Bergson  MCT, MCSE, MCSA, CNE, CNA, CCA
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Cary Shultz" <cwshu***@mvps.org> wrote in message
> news:uULSVKkLGHA.1676@TK2MSFTNGP09.phx.gbl...
>> Oh,
>>
>> And let's make sure that your domain is not a single-label domain
>> (mydomain instead of mydomain.com) and let's make sure that you do not
>> have a dual-homed situation (where the Domain Controller has two working
>> network cards).
>>
>> --
>> Cary W. Shultz
>> Roanoke, VA  24012
>>
>> "Cary Shultz" <cwshu***@mvps.org> wrote in message
>> news:uS5P1DkLGHA.2036@TK2MSFTNGP14.phx.gbl...
>>> Okay,
>>>
>>> Let's summarize what is going on here:
>>>
>>> You had it such that the secondary DNS information was the IP Address of
>>> your ISP's DNS Server.  This was on both the Domain Controller and on
>>> all client workstations.  This information is set statically.  You
>>> changed the ISP information (is there another Domain Controller in your
>>> environment?). Now, by changing it does that mean that you removed it or
>>> that you entered in the IP Address of another DNS Server?  The name in
>>> your forward lookup zone matches exactly the name of your internal
>>> domain.
>>>
>>> You have rebooted all of the systems.  Another way would have been to do
>>> the following at a command prompt on each system:
>>>
>>> net stop netlogon
>>> ipconfig /flushdns
>>> ipconfig /registerdns
>>> net start netlogon
>>>
>>> This has not resolved anything?
>>>
>>> What happens if you use nslookup?  What does that tell you?
>>>
>>> Are you able to get to the Internet once you do finally connect?
>>>
>>> Do you have all of the subfolders in the FLZ?  Those would be _sites,
>>> _tcp, _udp and _msdcs.  And all of the records are there?
>>> What happens if you install the Support Tools and use dcdaig /v and
>>> netdiag /v?  What is the output from each of those?
>>>
>>> --
>>> Cary W. Shultz
>>> Roanoke, VA  24012
>>>
>>> "Chetan" <chetan.ka***@gmail.com> wrote in message
>>> news:1139573042.480745.241460@g14g2000cwa.googlegroups.com...
>>>> Thanks
>>>> I done that too but it doesnt work
>>>>
>>>
>>>
>>
>>
>
>

"Cary Shultz" <cwshu***@mvps.org> wrote in message
news:eQHDWdoLGHA.3732@TK2MSFTNGP10.phx.gbl...
> Yea!
>
> Use Paul's tool.  I have not yet used it but I did open it up and take a
> look.  It looks nice....will have to play.  That comes later tonight.
>
> Paul, I will start sending people to your web site....if you do not mind.
>
> --
> Cary W. Shultz
> Roanoke, VA  24012
>
> "Paul Bergson" <pbergson@allete_nospam.com> wrote in message
> news:%23r2jfikLGHA.1288@TK2MSFTNGP09.phx.gbl...
>> Also let run diagnostics against the domain and see if there are any
>> lingering issues you may not be aware of.
>>
>> Running diagnostics against your Active Directory domain.
>>
>> If you don't have the tools installed, install them from your server
>> install disk.
>> d:\support\tools\setup.exe
>>
>> Run dcdiag and netdiag in verbose mode.
>>
>> If you download a gui script I wrote it should be simple to set and run.
>> It also has the option to run individual tests without having to learn
>> all the switch options.  The details will be output in notepad text files
>> that pop up automagically.
>>
>> The script is located in the download section on my website at
>> http://pbbergs.dynu.com/windows
>>
>> Just select both dcdiag and netdiag make sure verbose is set.  (Leave the
>> default settings for dcdiag as set when selected)
>>
>> When complete search for fail, error and warning messages.
>>
>>
>> --
>>
>> Paul Bergson  MCT, MCSE, MCSA, CNE, CNA, CCA
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Cary Shultz" <cwshu***@mvps.org> wrote in message
>> news:uULSVKkLGHA.1676@TK2MSFTNGP09.phx.gbl...
>>> Oh,
>>>
>>> And let's make sure that your domain is not a single-label domain
>>> (mydomain instead of mydomain.com) and let's make sure that you do not
>>> have a dual-homed situation (where the Domain Controller has two working
>>> network cards).
>>>
>>> --
>>> Cary W. Shultz
>>> Roanoke, VA  24012
>>>
>>> "Cary Shultz" <cwshu***@mvps.org> wrote in message
>>> news:uS5P1DkLGHA.2036@TK2MSFTNGP14.phx.gbl...
>>>> Okay,
>>>>
>>>> Let's summarize what is going on here:
>>>>
>>>> You had it such that the secondary DNS information was the IP Address
>>>> of your ISP's DNS Server.  This was on both the Domain Controller and
>>>> on all client workstations.  This information is set statically.  You
>>>> changed the ISP information (is there another Domain Controller in your
>>>> environment?). Now, by changing it does that mean that you removed it
>>>> or that you entered in the IP Address of another DNS Server?  The name
>>>> in your forward lookup zone matches exactly the name of your internal
>>>> domain.
>>>>
>>>> You have rebooted all of the systems.  Another way would have been to
>>>> do the following at a command prompt on each system:
>>>>
>>>> net stop netlogon
>>>> ipconfig /flushdns
>>>> ipconfig /registerdns
>>>> net start netlogon
>>>>
>>>> This has not resolved anything?
>>>>
>>>> What happens if you use nslookup?  What does that tell you?
>>>>
>>>> Are you able to get to the Internet once you do finally connect?
>>>>
>>>> Do you have all of the subfolders in the FLZ?  Those would be _sites,
>>>> _tcp, _udp and _msdcs.  And all of the records are there?
>>>> What happens if you install the Support Tools and use dcdaig /v and
>>>> netdiag /v?  What is the output from each of those?
>>>>
>>>> --
>>>> Cary W. Shultz
>>>> Roanoke, VA  24012
>>>>
>>>> "Chetan" <chetan.ka***@gmail.com> wrote in message
>>>> news:1139573042.480745.241460@g14g2000cwa.googlegroups.com...
>>>>> Thanks
>>>>> I done that too but it doesnt work
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>