VERY slow logon...

[Rich]

I just setup a server with AD, WIN2K server. Small network
for now,only 5 PC and 2 ntwk printers, DSL for internet.
When the users try to logon, it'll take 5 mins for their
desktop to show up. It'll stay dangling in APPLYING
PERSONAL SETTINGS.
I did exact setup in a lab and it works just fine. Someone
yesterday suggested my DNS server was set wrong. In fact
it was and I did correct that but it didn't do much help
with logging in.
ANYONE HAVE MORE IDEAS?? Pleas HELP!!
THANKS

 

[Scott Harding - MS MVP]

Are your clients pointing to your internal DNS server? They should not be
pointing to any ISP DNS servers and your server needs to be pointing to
itself for DNS aswell.

 

[Guest]

They are DHCP..should they be set manualy?
The server I do know is pointing to it's self..128.0.0.1

 

[Oli Restorick [MVP]]

DHCP is good -- don't hardcode. You need to make sure that the workstations
point only to your own DNS server. You then use a forwarder on your DNS
server to allow name resolution with the outside world.

Hope this helps

Oli

 

[Rich]

Oli, Do I need to input the DNS servers IP manaully on the
workstations? They are DHCP but the DNS IP is from the
router and not from the server. I assume that to modify
this I need to input it manually on each
workstation..right?
Thanks again...!!!!!!

 

[Rich]

Me again...OLI...I did do the forwarding with advise from
someone yesterday...but like you mention the DNS number on
the workstations are the routers and not the servers.
I guess I need to input the servers DNS IP into the
workstations manually....right???
Thanks for your help..

 

[Oli Restorick [MVP]]

You need to change the DNS entries in the DHCP server settings. Whether
you're using Windows as a DHCP server or your router shouldn't matter --
both will have a place to change it. If your router is acting as a DHCP
server, there will be an option to change the DNS addresses it gives out.

Of course, the DNS server itself will be hardcoded to point to itself only
for DNS.

If you really can't help it, hardcoding the DNS entries on the workstations
would work, but try and do it properly first.

Regards

Oli

 

[Rich]

Oli, this is what I"ve done. My server has 127.0.0.1 as
DNS address, I forworded the routers IP's which are
66.75.160.41 and 37 and 42..
On the worksstations I added DNS 127.0.0.1 and no other
number, but now I loose the internet access. If I take out
the 127.0.0.1 and just let it pick up what ever it wants
it'll pick up the numbers above starting with
66.75.etc...then internet access is fine.
WHat am I doing wrong..then????

 

[Guest]

LOL, man you need to get a clue.

The IP address of 127.0.0.1 is a special address setup to
point right back at itself. So when you set the DNS IP on
the workstations to 127.0.0.1, they are trying to use
themselves as a DNS server. You need to set them to the
actual IP address of your DNS server. And if your DNS
server's IP address is 127.0.0.1, you'll need to change
that. (BTW, setting the DNS server's DNS IP address to
127.0.0.1 will work because it is supposed to be pointing
at itself. I usually just use the actually IP of the
server though.)