Solved

very slow logon from XP pro workstation

Posted on 2008-06-16
12
573 Views
Last Modified: 2008-08-02
we have a single microsoft small business 2003 server, and 5 xp pro workstations connected in a small network. We are also running exchange. This network has been running fine for the past year, but we are now experiencing speed issues when logging in from each workstation. I have checked the DNS and all looks fine. I can confirm that when we restart the server, it seems to resolve the problem for a short while, but we do not want to have to do this every day. The exchange mailboxes are pretty empty.
Does anyone have any suggestions as to how we can resolve this issue?
0
Comment
Question by:nigelbeatson
[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
  • 6
  • 4
  • 2
12 Comments
 
LVL 21

Assisted Solution

by:suppsaws
suppsaws earned 200 total points
ID: 21792363
Hello nigelbeatson,

Slow logons is mostly due to DNS issues.
Can you copy past the ipconfig /all of the server and one worksation please?
Do you see anything strange in the eventlogs of the server/clients?
Did you add these clients the correct 'connectcomputer' way to the domain?

Regards,

suppsaws
0
 

Author Comment

by:nigelbeatson
ID: 21792398
I will be going to the sate later this afternoon, and will provide the information requested at that time.
Many thanks for your help.
0
 
LVL 70

Assisted Solution

by:KCTS
KCTS earned 300 total points
ID: 21792574
I'll second that opinion - you say DNS if fin but in over 90% of cases incorrectly configured DNS is the problem, DNS *MUST* br configured as follows.

1. All workstations *MUST* point to the internal DNS server (normally the Domain Controller), ONLY. This is configured either in the TCP/IP properties on the Network Connections for static IPs where the internal server must be the preferred and only DNS server, or in the DHCP Options in DNS where the internal DNS server must be the only server listed.

2. Your Server *MUST* have a static IP and the preferred DNS server should point to itself

3. Ti resolve external names, set up forwarders to point to your ISPs DNS severs as detailes at http://www.petri.co.il/configure_dns_forwarding.htm, this is the ONLY place any external DNS servers should be registered.
0
Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

 

Author Comment

by:nigelbeatson
ID: 21792695
Thankyou for your input. I am going out to this site later on today, so will update everyone at that time. One thing I would point out is that this server / network has been working fine for around a year, and none of the settings have been changed (by design anyway!) since then. Update later.
0
 
LVL 70

Expert Comment

by:KCTS
ID: 21792757
Sometimes the issue can emerge when an external DNS server is specified as an alternate DNS server, most of the time its neve used and everything works fine, but if the preferred server becomes busy, the clients will switch to the alternate server and from that point on all internal name resolution fails and logon slows down or does not happen at all.
0
 
LVL 21

Expert Comment

by:suppsaws
ID: 21792790
the forwarders need to be configured in the 'connect to the internet wizard'.
Rerun that wizard and place your ISP dns servers there.
Also, is your server the DHCP server for the domain, or is DHCP provided by a router? (which is not good)
0
 

Author Comment

by:nigelbeatson
ID: 21792971
Sorry for the delay, my visit to site has been delayed to tomorrow afternoon, so I will not be able to update this incident till then. Many thanks for input.
0
 
LVL 70

Expert Comment

by:KCTS
ID: 21793040
OK no problem
0
 

Author Comment

by:nigelbeatson
ID: 21801692
I have checked out this site and manually removed the workstation from the domain, deleted the computer from the active directory, renamed the workstation and tried connect mycomputer again. It goes through fine, right up to the point where it usually restarts, and after a short delay, we get the error "An error occured when configuring networking settings. See your network administrator."
Therfore the workstation cannot be added. I can add the workstation to the domain manually, but the login hangs on applying computer settings.
I can login locally.
I tried the other problem workstation and the connectcomputer util seems to have resolved this. Any ideas?
0
 
LVL 70

Expert Comment

by:KCTS
ID: 21802032
Please run IPCONFIG /all on both workstation and server and post the results here.
0
 

Author Comment

by:nigelbeatson
ID: 21813434
ipconfig /all for workstation :-
Windows IP Configuration
        Host Name . . . . . . . . . . . . : alfbws
        Primary Dns Suffix  . . . . . . . : ctree.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : ctree.local
                                            ctree.local
Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : ctree.local
        Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet for hp
        Physical Address. . . . . . . . . : 00-0F-20-FC-78-C7
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.7.77
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.7.1
        DHCP Server . . . . . . . . . . . : 192.168.7.254
        DNS Servers . . . . . . . . . . . : 192.168.7.254
        Primary WINS Server . . . . . . . : 192.168.7.254
        Lease Obtained. . . . . . . . . . : 17 June 2008 15:40:12
        Lease Expires . . . . . . . . . . : 25 June 2008 15:40:12

ipconfig /all for server :-

Windows IP Configuration
   Host Name . . . . . . . . . . . . : sbserver
   Primary Dns Suffix  . . . . . . . : ctree.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : ctree.local

Ethernet adapter Server Local Area Connection:
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 EB1 Network Connection with I/O Acceleration
   Physical Address. . . . . . . . . : 00-1A-92-E0-57-0C
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.7.254
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.7.1
   DNS Servers . . . . . . . . . . . : 192.168.7.254
   Primary WINS Server . . . . . . . : 192.168.7.254

Hope this helps. Please advise.
0
 

Accepted Solution

by:
nigelbeatson earned 0 total points
ID: 21830794
OK. I hvae now resolved this issue. Not sure what the underlying problem was, but when I returned I managed to re connect the problem workstation with the connectcomputer wizard, where previous attemts had failed. It's now working fine. Thanks to all who helped.
0

Featured Post

Technology Partners: 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!

Question has a verified solution.

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

This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Small Business Server 2011. NOTE: This guide has been written using the preview version of SBS2011 therefore some of the screens may …
The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

691 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