Improve company productivity with a Business Account.Sign Up

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

How to speed up a slow Windows logon from a Vista Business pc to MS Server 2003 standard?

I have 5 vista business machines on my domain, and they take forever to logon, sometimes up to 10 minutes.    They are about a year old now and have gotten continually worse.  Any ideas?
0
cmwinchester
Asked:
cmwinchester
  • 7
  • 6
  • 2
1 Solution
 
gurutcCommented:
Hi,

Do you know how to check your DNS options in Network Connections?  Usually this is related to 'register this workstation's IP in DNS' or 'Use this connection's suffix in DNS registration'

Check these settings, the second one in particular should be unchecked.  

Good Luck,
- gurutc
0
 
KCTSCommented:
Slow logins are almost always a DNS issue - make sure the machines are set to use your Windows DNS server ONLY as their preferred DNS server.
0
 
cmwinchesterAuthor Commented:
Checking right now,  thanks for the quick response!
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
cmwinchesterAuthor Commented:
Logon times have not improved after making the above changes.  If it helps at all, when I logon to the machine and not the domain it is very quick.
0
 
gurutcCommented:
Hi,

Do you have more than one confirued network connection?  If so, try disabling the ones that aren't in use.  Is this a laptop?

Good Luck,

- gurutc
0
 
cmwinchesterAuthor Commented:
Only one connection and this is a desktop Dell Vostro 400.  
0
 
cmwinchesterAuthor Commented:
What info can i provide to help?
0
 
KCTSCommented:
on both a worksation and a server, form the command prompt run
IPCONFIG /ALL
and post the results here
0
 
cmwinchesterAuthor Commented:
Server ipconfig /all:
Windows IP Configuration
Host Name.............................. SERVER02
Primary DNS suffux:................kwpremier.local
Node Type...............................Unknown
IP Routing.................................NO
WINS Proxy Enabled................NO
DNS Suffix Search List............kwpremier.local

Ehternet adapter Local Area Confiuration:
Connection-specific DNS Suffix
Description........................Intell(R) PRO/1000 MT Network Connection
Physical Address..............00:14:22;B3:GA:02
DHCP Enabled...................No
IP Address........................192.168.1.10
Subnet Mask.....................255.255.255.0
Default Gateway..............192.168.1.5
DNS Servers.....................127.0.0.1

From PC
Windows IP Configuration
Host Name.............................. bullpen1
Primary DNS suffux:................kwpremier.local
Node Type...............................Hybrid
IP Routing Enabled...................NO
WINS Proxy Enabled................NO
DNS Suffix Search List............kwpremier.local

Ehternet adapter Local Area Confiuration:
Connection-specific DNS Suffix
Description...........................Intell(R)  8256V2-210/100 Network Connection
Physical Address................00:1D:09:90:8B
DHCP Enabled......................Yes
Autoconfiguration Enabled...Yes
IPv4 Address........................192.168.1.119(Preferred)
IP Address...........................192.168.1.10
Subnet Mask........................255.255.255.0
Lease Obtained...................Sunday March 29
Lease Expires ....................Friday April 03
Default Gateway.................192.168.1.5
DHCP Servers.....................192.168.1.5
DNS Servers.......................64.89.70.2
                                            64.89.74.2
Net Bios over TCP.IP...........Enabled


0
 
gurutcCommented:
Is DNS Server running on the server?  if so, configure the server's DNS server to be 192.168.1.10

Good Luck,

- gurutc
0
 
gurutcCommented:
Also, add the server's IP address as a secondary DNS server to the workstation.  That way, the workstation will be able to resolve the domain's DNS record, which is served by the server, and find the login domain.

Good Luck,

- gurutc
0
 
gurutcCommented:
What's happening is this, the workstation is trying to find a DNS record for the kwpremier.local domain, and its currently configured DNS server, 64.89.70.2, doesn't hold a record for that domain, but the domain server does.  So it needs to be one of the workstation's configured DNS servers.

Good Luck,

- gurutc
0
 
cmwinchesterAuthor Commented:
testing right now, will get back you asap. Thaks!
0
 
cmwinchesterAuthor Commented:
Perfect!
0
 
gurutcCommented:
Sweet!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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