Solved

Slow logon to 2003 Server

Posted on 2006-11-05
4
212 Views
Last Modified: 2010-04-18
What can I do to speed up my logon from the client machines to the server
0
Comment
Question by:jontyplatt
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 51

Accepted Solution

by:
Netman66 earned 250 total points
ID: 17877029
Most of the time slow logons is due to the fact that you have the ISP DNS server on the client machines and not your own DNS server.  Make sure DNS is setup properly - all clients and servers inside your network will point exclusively to your DNS servers.  Use Forwarding in the properties of your DNS to send requests to the ISP.

Next, make sure if you use Roaming profiles that they are kept small.

Lastly, keep the number of GPOs you use to a bare minimum since each and every GPO must be parsed during logon.


0
 
LVL 16

Expert Comment

by:kshays
ID: 17878501
Other than what Netman66 said, which I would suspect you have your clients dns entries pointing toward either your ISP's dns servers or a router by chance and not your DNS server.  If you are using roaming profiles you might want to think about folder redirection also.

You could post the IP configuration of your client machine for us to look at :)
0
 

Author Comment

by:jontyplatt
ID: 17887969
no the DNS is set to the DNS server locally. is it better to have the DNS on ther server or on teh router? Do I need to statically assigne teh DNS on teh client machines - will this make it quicker?
0
 
LVL 16

Expert Comment

by:kshays
ID: 17888890
Typically in a windows environment with a domain a simple setup would be as follows.

ServerA
- DNS
- DHCP
- DC
TCP Info:
IP: 192.168.1.2
Netmask: 255.255.255.0
Default Gateway: IP of your router

ServerA resides inside your LAN.  You would want all of your workstations to obtain IP automatically in a large environment.  DHCP will also hand out and give the correct DNS entries for your workstations also.  If you are not using DHCP and you are statically assigning IP's on your workstations then you will want to go ahead and assign the DNS server IP to use which would be (192.168.1.2).  Remember, this is just ficticious IP's for examples only :)

I would rather have the DNS running as a service on my DC, but lots of people use the builtin DNS/dhcp that many routers use also though.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Group Policy & Netlogin Services 5 58
Bizarre hard disk problem 15 137
Unknown AD user under VMWare OU 4 72
Unexpected Windows system folders on D drive 16 99
Organizations create, modify, and maintain huge amounts of data to help their businesses earn money and generally function.  Typically every network user within an organization has a bit of disk space to store in process items and personal files.   …
Learn about cloud computing and its benefits for small business owners.
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Finding and deleting duplicate (picture) files can be a time consuming task. My wife and I, our three kids and their families all share one dilemma: Managing our pictures. Between desktops, laptops, phones, tablets, and cameras; over the last decade…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question