[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 216
  • Last Modified:

Slow logon to 2003 Server

What can I do to speed up my logon from the client machines to the server
0
jontyplatt
Asked:
jontyplatt
  • 2
1 Solution
 
Netman66Commented:
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
 
Kevin HaysIT AnalystCommented:
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
 
jontyplattAuthor Commented:
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
 
Kevin HaysIT AnalystCommented:
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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now