VERY slow login on W2K clients - NEED HELP

[Mark Bratcher]

Hello,

I helped a friend set up a 5 PC network to use a DSL gateway (Siemens
6520 Speedstream). Previously, they were not on the internet. The
clients are all Win2000 along with a Win2000 server. The clients all
login in with the server. Everything is fixed IP.

I added the DSL gateway to the net, setting up the LAN side to be
consistent with what they had: all fixed IP. Everything, including the
DSL gateway, plug into a simple multi-port hub. I gave it a unique
LAN-side fixed IP. I setup all the clients to point to the DSL gateway
as the DNS server on the LAN and as the gateway. Again, everything fixed
IP. The DSL gateway, on the WAN side, goes off and does its thing,
getting it's WAN side IP and DNS server addresses.

Everything works, EXCEPT it takes about 20 minutes for a client to boot
up and log in. That time is split between about 10 minutes to get to the
login screen. Then another 10 minutes to login while it says "loading
personal settings". This happens with ALL the clients on the network.

Anyone know what's wrong with this setup? Let me know what else I need
to describe to determine the problem. I've read a couple of threads
about this problem. But I don't see a solution. Some say, "check the DNS
settings" but don't suggest what correct settings look like. I think
they're correct, but perhaps they aren't.

Any help appreciated.

Thanks.

 

[Robert L [MS-MVP]]

Yes, this is DNS issue. Since you have a windows 2000 server, you may want to install an internal DNS instead of using your ISP DNS (assuming you are using the ISP DNS. these links may help,

DNS how to For more troubleshooting information about DNS configuration for Active Directory, see the following Microsoft Knowledge Base articles: ...
www.howtonetworking.com/server/dns.htm


DNS Concept
DNS How to
DNS Operations Topics

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
Hello,

I helped a friend set up a 5 PC network to use a DSL gateway (Siemens
6520 Speedstream). Previously, they were not on the internet. The
clients are all Win2000 along with a Win2000 server. The clients all
login in with the server. Everything is fixed IP.

I added the DSL gateway to the net, setting up the LAN side to be
consistent with what they had: all fixed IP. Everything, including the
DSL gateway, plug into a simple multi-port hub. I gave it a unique
LAN-side fixed IP. I setup all the clients to point to the DSL gateway
as the DNS server on the LAN and as the gateway. Again, everything fixed
IP. The DSL gateway, on the WAN side, goes off and does its thing,
getting it's WAN side IP and DNS server addresses.

Everything works, EXCEPT it takes about 20 minutes for a client to boot
up and log in. That time is split between about 10 minutes to get to the
login screen. Then another 10 minutes to login while it says "loading
personal settings". This happens with ALL the clients on the network.

Anyone know what's wrong with this setup? Let me know what else I need
to describe to determine the problem. I've read a couple of threads
about this problem. But I don't see a solution. Some say, "check the DNS
settings" but don't suggest what correct settings look like. I think
they're correct, but perhaps they aren't.

Any help appreciated.

Thanks.

 

[josepe]

Your resolve-name problem can be done by doing this:
-If you don't need a domain server -using like Group Server- the station
can shut to the DNS of the ISP. With this schema the server don't need
DNS in the ethernet card -if don't need internet access-
-If need the domain server, the pcs should shout to the DNS of the
server, and this resolve to the machines. In a small network this is not
necesary because the internet service is whithout server to admin.

 

[Mark Bratcher]

Thanks. So you're saying set up the local Win2K server as the DNS server
for the clients, and have the Win2K server resolve DNS through the DSL
gateway?

 

[josepe]

Yep.-

 

[Mark Bratcher]

Yep.-

THanks

Now, hypothetically, suppose they had just a peer-to-peer network with
no designated server and wanted an internet connection through a DSL
gateway. How would that be done then? Would you have to designate one of
the clients as the DNS server for the group to avoid the slow login problem?