Slow Authentication

I am new to this "whole" networking thing. I have setup Windows Server
2003 for the sole purpose of getting some practical hands-experience
with this operating system. I have been able to get three clients
connected to my domain but it is a very slow process each time I
connect. It ususally takes about 5-10 minutes to anyone of the
computers and I have tried numerous things. I have pointed the DNS
server of the server back to itself. I have used the public DNS server
given by my ISP. I am running out of ideas. HELP!!!!!!!!!!!!

(E-Mail Removed) wrote in
news:(E-Mail Removed) oups.com:

> I am new to this "whole" networking thing. I have setup Windows Server
> 2003 for the sole purpose of getting some practical hands-experience
> with this operating system. I have been able to get three clients
> connected to my domain but it is a very slow process each time I
> connect. It ususally takes about 5-10 minutes to anyone of the
> computers and I have tried numerous things. I have pointed the DNS
> server of the server back to itself. I have used the public DNS server
> given by my ISP. I am running out of ideas. HELP!!!!!!!!!!!!
>
>

Hi there --

The first thing I would do is check all the hardware and cables. Then I
would install WINS.

WINS, like DNS, is a naming service that maps computer names to IP
addresses and on a small network such as yours it is totally trouble free -
- all you have to do is install it, no configuration necessary.

After you do that, assuming you don't have any hardware problems or that
you have fixed any problems you discovered, you can troubleshoot your DNS
issues.

I should also ask if you have installed and configured DHCP...? If you have
not manually configured the computers with an IP address in TCP/IP
properties, you need to either do that or deploy DHCP. (You should get the
computers configured with IPs before installing WINS.)

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

I have pointed the DNS
>> server of the server back to itself. I have used the public DNS server
>> given by my ISP. I am running out of ideas. HELP!!!!!!!!!!!!

Classic symptoms of your DNS being misconfigured.

Basic AD DNS setup

Point the DNS server set up for the AD domain to it self in the properties
of TCP/IP. Use the actual IP address not 127.0.0.1. This will allow the DNS
server to register it's SRV record in the DNS zone.
See:
http://support.microsoft.com/kb/814591/en-us



All AD clients must point to the DNS server set up for the AD domain ONLY.
Your AD clients need to find the SRV records for the AD domain in order to
"find" the domain. Your ISP will not let, nor do you want your private AD
domain listed on a public DNS server. Pointing them to the DNS server set up
for the AD domain, they will "find" the proper SRV records.
See:
http://support.microsoft.com/kb/825036/en-us

For Internet access, set up your AD DNS server to forward requests and list
your ISP's DNS servers as the forwarders. This is the only place on an AD
domain your ISP's DNS server should be listed. You can also use root hints.
See:
http://support.microsoft.com/kb/323380/en-us

hth
DDS
"James McIllece [MS]" <(E-Mail Removed)> wrote in message
news:Xns987092AF5C0F5jamesmcionlinemicros@207.46.2 48.16...
> (E-Mail Removed) wrote in
> news:(E-Mail Removed) oups.com:
>
>> I am new to this "whole" networking thing. I have setup Windows Server
>> 2003 for the sole purpose of getting some practical hands-experience
>> with this operating system. I have been able to get three clients
>> connected to my domain but it is a very slow process each time I
>> connect. It ususally takes about 5-10 minutes to anyone of the
>> computers and I have tried numerous things. I have pointed the DNS
>> server of the server back to itself. I have used the public DNS server
>> given by my ISP. I am running out of ideas. HELP!!!!!!!!!!!!
>>
>>
>
> Hi there --
>
> The first thing I would do is check all the hardware and cables. Then I
> would install WINS.
>
> WINS, like DNS, is a naming service that maps computer names to IP
> addresses and on a small network such as yours it is totally trouble
> free -
> - all you have to do is install it, no configuration necessary.
>
> After you do that, assuming you don't have any hardware problems or that
> you have fixed any problems you discovered, you can troubleshoot your DNS
> issues.
>
> I should also ask if you have installed and configured DHCP...? If you
> have
> not manually configured the computers with an IP address in TCP/IP
> properties, you need to either do that or deploy DHCP. (You should get the
> computers configured with IPs before installing WINS.)
>
> --
> James McIllece, Microsoft
>
> Please do not send email directly to this alias. This is my online
> account
> name for newsgroup participation only.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Posting the result of ipconfig /all here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
<(E-Mail Removed)> wrote in message news:(E-Mail Removed) oups.com...
I am new to this "whole" networking thing. I have setup Windows Server
2003 for the sole purpose of getting some practical hands-experience
with this operating system. I have been able to get three clients
connected to my domain but it is a very slow process each time I
connect. It ususally takes about 5-10 minutes to anyone of the
computers and I have tried numerous things. I have pointed the DNS
server of the server back to itself. I have used the public DNS server
given by my ISP. I am running out of ideas. HELP!!!!!!!!!!!!