Welcome to 

    micky.com

   


















     

     

    

    




Welcome to my SBS page for networking


Knowledge base articles
Using browstat status to trouble shoot browsers



Notes


DNS servers
These DNS servers allow public access
4.2.2.1                 (vnsc-pri.sys.gtei.net)
4.2.2.2                 (vnsc-bak.sys.gtei.net)
65.74.140.3         (noc.arpa.org)
206.111.255.123 (nic.arpa.org)
216.185.111.10   (ns1.servermatrix.com)
69.56.222.10       (ns2.servermatrix.com)
67.19.0.10           (ns3.servermatrix.com)
67.19.1.10           (ns4.servermatrix.com)
70.84.160.11       (ns5.servermatrix.com)

Time servers
More information at NTP.Servers Web
Area: HostName:
Worldwide pool.ntp.org
Asia asia.pool.ntp.org
Europe europe.pool.ntp.org
North America north-america.pool.ntp.org
Oceania oceania.pool.ntp.org
South America south-america.pool.ntp.org


How to configure an authoritative time server in Windows Server 2003
How to configure an authoritative time server in Windows 2000

Log on/off hanging
the system hangs when logging in, most of the time at the "applying network settings" section or "applying your personal settings" or "applying computer settings".

I have three possible solutions to this problem. One if it is occurring on a laptop with wireless, Secondary, any PC with DNS issues and finally profile issues.

Wireless Go into your wireless settings and look at your list of "preferred networks." Every time you connect to a hotspot it will add itself to this list. Remove all of the "preferred networks" except for the ones you regularly use and it should fix the issue completely. Every time you boot fresh, or restart, the system checks the availability of each one of these connections before logging in.

If it only checks 4 or 5, you never see the slowness. When there is a build-up of them over time it will increase the logon time.

Wired
If it is a wired network (or the above solution does not work for your wireless connection), it is likely DNS. A lot of network slowness in a Microsoft environment is caused by a miss configured DNS server . This is because name resolution's last resort is broadcasts which take time.

Windows 2000 and XP use DNS to locate Domain Controllers. If DNS is not configured properly, a Windows 2000 or XP system will waste time waiting for a DNS query to timeout, then try NT4 NetBIOS (i.e., WINS) to locate a Domain Controller. See the Microsoft articles How Domain Controllers Are Located in Windows, or How Domain Controllers Are Located in Windows XP, for more information.

How Domain Controllers Are Located in Windows XP
How Domain Controllers Are Located in Windows


Solution
Ensure that the 2000 / XP clients are all configured to use the domain DNS server. If you're using DHCP on your LAN, the DHCP server should provide the address of the domain DNS server, not your ISP's DNS server(s). If you're not using DHCP, each client should provide the address of the domain DNS server individually.

Whether you use DHCP or not, don't specify your ISP's DNS server as a backup to your domain DNS server. If you're using DNS for name resolution, your ISP won't have your local addresses.

Check Properties for the DNS server Forward Lookup Zone.

On the General tab, ensure the domain DNS server is configured to permit dynamic updates.

On the Name Servers tab, ensure the DNS server points to itself as a DNS server.

Check Properties for the DNS server itself. For both LAN address resolution, and internet address resolution, specify your ISP's DNS server(s) in the Forwarders tab of the DNS server.

Make sure the binding order for you network cards is internal first.

Setting Up the Domain Name System for Active Directory
How to configure DNS for Internet access in Windows 2000
How to configure load balancing/secondary DNS

Profile
It could also be a large user profile , a large "my documents" redirection or offline files. You can diagnose using the User Profile Hive Cleanup Service
Another giveaway that the profile is in trouble is if there are tmp files in the profile. Do not underestimate the power of the Event log. Look on the server and workstation for errors regarding profiles (winlogon or user32 etc)

If you have a slow logoff and error in the event log indicating the registry hive could not be unloaded, use the UPHClean

example:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1517
Description:
Windows saved user ComputerName\UserName registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use. This is caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.


Offline file issues
I have had a few instances where the servers IP address has been changed or the workstation is migrating to a new domain. The Offline File service is still looking for the old server. The best solution for this is to click the offline icon in the task bar, pull up the settings, hold the shift key and tap the control key and then click the delete button and totally re initiate the offline cache. Then you can turn off the offline cache, and reboot. When you turn it back on, all should be fixed. If you can not get to the offline settings, open My Computer, Tools, Folder options and select the Offline tab. Correct the issue from here. Thanks to Tony Brewer for doing the research on this one !

 

 

 

 

 

 

    

 

     ( )

 

 

 

 

                                                             This page was written and designed by Michael Jenkin 2011 ©