Slow login..help pls!!

[Rich]

PLS HELP!! samll network is very slow to logon. IT takes
at least mins to logon.
I just setup a small network with Win2000 Server using AD.
My conections are all fine once I'm logged on but the
login just takes to long. As soon as the user enters their
password hit enter it'll take 5 mins to show the desk
top.It stays dangling in the window that reads "APPLYING
YOUR PERSONAL SETTINGS" Network is new 5 users only and no
other service running off that server. As a matter a fact
there is no other server. IN advance Thanks!!!
HELP PLS..!!

 

[Marina Roos [SBS-MVP]]

Check the ipconfig/all on the clients. Does everything point to your
server-IP? How many nics in the server?

 

[Rich]

The server only has one NIC and results on the IPCONFIG
seems that the workstations are pointing to the router DNS
numbers and not the servers which is 128.0.0.1..should all
workstations be pointing to that number? Should I enter
those manually?
Thanks for your help..!!

 

[Guest]

IF you've installed DNS on one of your servers, the PCs need to point to that server for DNS. If you installed DHCP, that should take care of it IF you use DHCP on the PCs

jwk

 

[Rich]

I did that, changing DNS on workstations to point to the
servers 127.0.0.1 and now I lost access to the internet.
But if I take the DNS off and let it pick up what DHCP is
sending it'll pick up the routers numbers and the internet
will work just fine. I did omit to mention the my router
is acting like a DHCP server and not my Win2000 server.
Could that be my problem? Should I let windows server be
the DHCP server instead of my router?
Thanks in advance

 

[Guest]

Nothing should be pointing to 127.0.0.1 for DNS or anything. That IP address is a "loopback" for EACH system. All PCs should be using DHCP from one of YOUR systems UNLESS the router points to your DNS server for DNS lookups. Just let me say it would be better that you have DNS AND DHCP on your servers. The DNS forwarders are a good idea; not required but faster. Of course, if your DNS FORWARDERS are down, you'll have problems

jwk

 

[Ben M. Schorr, MVP-OneNote]

127.0.0.1 is the local loopback address. You need to check again to see
what the IP address of your DNS server is - it can't be that. I'd be inclined
to let Windows handle your DHCP because you get a lot more flexibility
that way - including the ability to let the DHCP service hand out the address
of your DNS server to the workstations.
Aloha,

-Ben-
Ben M. Schorr, OneNote-MVP
http://home.hawaii.rr.com/schorr
http://www.thespoke.net/MyBlog/bschorr/MyBlog.aspx

**I apologize but I am unable to respond to direct requests for assistance.
Please post questions and replies here in the newsgroup. Mahalo!

 

[robert]

all workstations should point to a local DNS, and your local dns should
forward to the routers ip to resolve external requests.

 

[Guest]

Check out or reinstall your DNS Server. Then, configure every client PC to have as primary DNS ip address the ip address of your Server (DC). Use commands like ipconfig /all, ipconfig flushdns, ipconfig registerdns etc

 

[Marina Roos [SBS-MVP]]

You have a server, right? So let it do all the serving including DNS and
DCHP.
DNS should be point to your server-IP on your servernic. In DNS-server it
should be listening to its own IP. You can put the ISP-DNS-numbers on the
tab Forwarders.
If you have options 003, 006 and 015 in DHCP-server, Scope options, all
settings will be automagically pushed to your clients.