excessive login times while logging into windows 2000 AD DC

I have 3 xp pro machines with all patches. They are all taking about a
minute or longer first to initially log into the domain then once the
user logs in it's another minute or so before they get the desktop. I
have killed the windows firewall completely and checked my dns settings.
I know there's a workaround i just don't remember what it is..

Hi,

So, how is DNS set up on the clients? ;-) And how is DNS set up on the DC
server? Where does preferred DNS server point to? How about other DNS
servers entered under TCP/IP?

Are there any errors in Event Logs (System and Application logs) on the
client and DC?

--
Mike
Microsoft MVP - Windows Security

"Hescominsoon" <(E-Mail Removed)> wrote in message
news:Z75hf.363$id.72@trnddc04...
>I have 3 xp pro machines with all patches. They are all taking about a
>minute or longer first to initially log into the domain then once the user
>logs in it's another minute or so before they get the desktop. I have
>killed the windows firewall completely and checked my dns settings. I know
>there's a workaround i just don't remember what it is..

Miha Pihler [MVP] wrote:
> Hi,
>
> So, how is DNS set up on the clients? ;-) And how is DNS set up on the DC
> server? Where does preferred DNS server point to? How about other DNS
> servers entered under TCP/IP?
>
> Are there any errors in Event Logs (System and Application logs) on the
> client and DC?
>
I have a linux firewall providing internet DNS. The DHCP is also on the
firewall machine. DHCP points the clients to the DC as primary DNS and
the linux machine as secondary dns. The DC is seutp to use the Linux
machine's it's primary DNS server. There ar not other DNS servers
entered into the DC's tcp/ip properties.

Hi,

DC also needs to point to itself or another Active Directory DNS. Change
this setting (e.g. point it back to itself -- if you do this, you can use
loop back adapter 127.0.0.1). Once you change it, restart Netlogon service
or reboot the server.

Now to enable clients to surf the web. Open DNS MMC on the Active Directory
DNS server. Right click on server name and click on Forwarders tab. Here
enter IP address of your Linux DNS server.

--
Mike
Microsoft MVP - Windows Security

"Hescominsoon" <(E-Mail Removed)> wrote in message
news:arnhf.19005$ZX3.11688@trnddc06...
> Miha Pihler [MVP] wrote:
>> Hi,
>>
>> So, how is DNS set up on the clients? ;-) And how is DNS set up on the DC
>> server? Where does preferred DNS server point to? How about other DNS
>> servers entered under TCP/IP?
>>
>> Are there any errors in Event Logs (System and Application logs) on the
>> client and DC?
>>
> I have a linux firewall providing internet DNS. The DHCP is also on the
> firewall machine. DHCP points the clients to the DC as primary DNS and
> the linux machine as secondary dns. The DC is seutp to use the Linux
> machine's it's primary DNS server. There ar not other DNS servers entered
> into the DC's tcp/ip properties.

ok so in the DC's tcp\ip properties..primarya nd secondary dns need to
point to itself? How will the DC get to the inet then for windows updates?


I will change the other settings in the DNS MMC for hte clients the next
time i am onsite.
Miha Pihler [MVP] wrote:
> Hi,
>
> DC also needs to point to itself or another Active Directory DNS. Change
> this setting (e.g. point it back to itself -- if you do this, you can use
> loop back adapter 127.0.0.1). Once you change it, restart Netlogon service
> or reboot the server.
>
> Now to enable clients to surf the web. Open DNS MMC on the Active Directory
> DNS server. Right click on server name and click on Forwarders tab. Here
> enter IP address of your Linux DNS server.
>

Hi,

As mentioned in my previous post...

Open DNS MMC and right click on server name. Now select Properties and
Forwarders. Here enter IP address of your Linux server.

This will forward all non-local domain DNS lookups (e.g. www.google.com)
that your local DNS server doesn't know about to Linux server and e.g. your
ISP and back to the server as an answer.


--
Mike
Microsoft MVP - Windows Security

"Hescominsoon" <(E-Mail Removed)> wrote in message
news:fZ4if.8886$F73.7962@trnddc03...
> ok so in the DC's tcp\ip properties..primarya nd secondary dns need to
> point to itself? How will the DC get to the inet then for windows
> updates?
>
>
> I will change the other settings in the DNS MMC for hte clients the next
> time i am onsite.
> Miha Pihler [MVP] wrote:
>> Hi,
>>
>> DC also needs to point to itself or another Active Directory DNS. Change
>> this setting (e.g. point it back to itself -- if you do this, you can use
>> loop back adapter 127.0.0.1). Once you change it, restart Netlogon
>> service or reboot the server.
>>
>> Now to enable clients to surf the web. Open DNS MMC on the Active
>> Directory DNS server. Right click on server name and click on Forwarders
>> tab. Here enter IP address of your Linux DNS server.
>>

rgr that..
Miha Pihler [MVP] wrote:
> Hi,
>
> As mentioned in my previous post...
>
> Open DNS MMC and right click on server name. Now select Properties and
> Forwarders. Here enter IP address of your Linux server.
>
> This will forward all non-local domain DNS lookups (e.g. www.google.com)
> that your local DNS server doesn't know about to Linux server and e.g. your
> ISP and back to the server as an answer.
>
>