Windows includes the W32Time Time service tool that is required by the Kerberos authentication protocol. The purpose of the Time service is to ensure that all computers that are running Windows 2000 or later in an organization use a common time. The Time service uses a hierarchical relationship that controls authority and does not permit loops to ensure appropriate common time usage.

Here is a quick fix... copy this into your command window: net time /setsntp: ntp2.usno.navy.mil

Windows-based computers use the following hierarchy by default:

• All client desktop computers nominate the authenticating domain controller as their in-bound time partner.
• All member servers follow the same process as client desktop computers.
• Domain controllers may nominate the primary domain controller (PDC) operations master as their in-bound time partner but may use a parent domain controller based on stratum numbering.
• All PDC operations masters follow the hierarchy of domains in the selection of their in-bound time partner.

Following this hierarchy, the PDC operations master at the root of the forest becomes authoritative for the organization, and you should configure the PDC operations master to gather the time from an external source. This is logged in the System event log on the computer as event ID 62. Administrators can configure the Time service on the PDC operations master at the root of the forest to recognize an external Simple Network Time Protocol (SNTP) time server as authoritative by using the following net time command, where server_list is the server list:

net time /setsntp: server_list

There are several SNTP time servers run by the U.S. Naval Observatory that are satisfactory for this function, for example:

• ntp2.usno.navy.mil at 192.5.41.209
• tock.usno.navy.mil at 192.5.41.41

After you set the SNTP time server as authoritative, run the following command on a computer other than the domain controller to reset the local computer's time against the authoritative time server:

net time /set

More information about the net time command is available at a command prompt if you type the following command:

net time /?

SNTP defaults to using User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers.

NOTE : Administrators can also configure an internal time server as authoritative by using the net time command. If the administrator directs the command to the operations master, it may be necessary to reboot the server for the changes to take effect.

For additional information, see the following Microsoft white paper:

The Windows Time Service
http://www.microsoft.com/windows2000/docs/wintimeserv.doc

From the command line, browse to the installation directory:

 (%WinDir%\Microsoft.Net\Framework\v1.1.4322} and run "aspnet_regiis.exe -i". 
This will install the sundry ASP.Net files, and register it with IIS correctly.

Also copy the aspnet_client from the wwroot and place the copy in any other web root directory that you may be using.

If you are trying to install Access 97 with Access 2000 or 2002 already installed you can get this error. Search for the font: Hatten.ttf move to another location(desktop). rename the .ttf to .old. or just delete. If you are in the Fonts folder you will not be able to change the TTF filename extension- You must move the Hatten file to another folder to change the name.

Re-instal Access 97
When you reinstall Access97 it will create a new Hatten.ttf in the Fonts
folder, then you could delete the other file that you changed.

Open the program...all fixed.
There is also a patch for this, however it only works with Windows 98!

Laptop users often experience problems when moving between networks where DHCP servers aren't consistently used (e.g., moving between an office that uses DHCP to assign IP addresses and a home network that uses static IP addresses). If you configure your computer to use DHCP and no DHCP server is available, the machine will typically use an IP address in the range 169.254.0.1 to 169.254.255.254 with a subnet mask of 255.255.0.0.

The actual IP address will depend on what IP addresses other machines on the local subnet have selected (XP will perform a limited test to ensure the Windows TCP/IP component doesn't use an address already in use). Because the local TCP/IP stack assigns no WINS, DHCP, or gateway information, all IP communication is limited to machines in the local subnet.

XP lets you create an alternate IP configuration that you can use when your system can't find a DHCP server. This alternate configuration lets you specify an IP address, subnet, gateway, and the other typical network settings. To create this alternate IP configuration, perform the following steps:

Open the Network Connections applet - (go to Start, Programs, Accessories, Communications and click Network Connections). Right-click the network adapter for which you want to specify an alternate IP configuration, then click Properties.  Select Internet Protocol (TCP/IP), then click Properties.
Under the General tab, ensure that you've configured the connection to use DHCP.
Select the Alternate Configuration tab, select "User configured," then fill in the static IP address details you want the connection to use when the system can't find a DHCP server.

If you are using a ststic address the 'Alternate Config' tab will not be shown!
You must be using DHCP.

XP stores the custom connection configuration settings under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\   registry subkeys

More on default settings

When Windows2000/XP is configured for TCP/IP "to Obtain an IP address automatically" via DHCP, it will first attempt to locate a DHCP-server (which can takes some time ). If no DHCP
server is found on the network, it will use the build-in "Automatic Client Configuration"
(sometimes referred to as APIPA ) to assign itself an IP-address in the address-range 169.254.x.x
with Subnet- mask 255.255.0.0.

On a large network with a predefined address range, this is often not required, because it will make
the trouble-shooting of networking problems more difficult when Windows2000 / XPtakes such an
"initiative" on its own.
It is possible to de-activate this feature. (The required changes in the registry are listed on the Microsoft Knowledge base articleQ244268):

You can deactivate the AutoIPgeneration for the complete computer using the Registry-key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add the following value to this key: "IPAutoconfigurationEnabled", Value type: REG_DWORD
Value in hexadecimal: 0 (A value of 0 disables APIPA support on this computer) :

You can deactivate the AutoIPgeneration for just one or more network adapters:

You need to find a registry entry under:
HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<adapter>

Create a new DWORD-key "IPAutoconfigurationEnabled" with the value set to 0 :

When restarting now Windows2000/ XP and no DHCP-server is found on the network,
no IP-address will be assigned:

in a Command-prompt window, run : ipconfig
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection

Connection-specific DNS SUffix . :
IP Address . . . . . . . . . . . . . .
Subnet Mask . . . . . . . . . . . .
Default Gateway
0.0.0.0
0.0.0.0

the IP-address "0.0.0.0" is invalid, it indicates that your system has no IP-address

How to identify the registry key for your network adapter ?

Check in the Properties of your Network configuration the EXACT name for your Network card, as listed under:
Connect using :( select it by dragging and copy it to the clipboard)

Search now the Registry for that "Adapter Description", you need to find the "ClassGUID",
a PCI-network card will be listed under
HKEY_LOCAL_MACHINE\system\CurrentControlSet\Enum\PCI :

with the "ClassGUID", search in
HKEY_LOCAL_MACHINE\system\CurrentControlSet\Control\Class\ for this class"

Check the sub-keys for the proper DriverDescription to match your network card. and look for the Key "NetCfgInstanceID", which is identical to your <adapter> number. if you have multiple matches showing the same DriverDescription, check under the sub-key  "Linkage" for the "UpperBind" to be "TCPIP".

HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}

HKEY_CLASSES_ROOT\LDAP

{228D9A81-C302-11cf-9AA4-00AA004A5691}

NOTE: If your registry keys contain values rather than being blank or missing, you should first back up the keys by using the Export Registry Key feature in Regedit.exe. You should then examine the entries for differences and merge them if you need to.

If the HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc} key is missing or damaged, add the following lines to a text file, rename it with a .reg extension, and then import it to your registry.

On a Windows 2000-based domain controller use the following text:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}] @="ADs LDAP Pathname Descriptor Object"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\InprocServer32]@="activeds.dll"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\ProgID] @="Pathname"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\TypeLib] @="{97d25db0-0363-11cf-abc4-02608c9e7553}"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\Version] @="0.0"

On a Windows 2000-based domain member computer use the following text:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}] @="ADs Pathname Object"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\InprocServer32]@="activeds.dll"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\ProgID] @="Pathname"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\TypeLib] @="{97d25db0-0363-11cf-abc4-02608c9e7553}"

[HKEY_CLASSES_ROOT\CLSID\{080d0d78-f421-11d0-a36e-00c04fb950dc}\Version] @="0.0"

If the HKEY_CLASSES_ROOT\LDAP key is missing, or damaged, use the following text:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\LDAP]
@="URL:LDAP Protocol"
"EditFlags"=hex:02,00,00,00
"URL Protocol"=""

[HKEY_CLASSES_ROOT\LDAP\Clsid]
@="{228D9A81-C302-11cf-9AA4-00AA004A5691}"

[HKEY_CLASSES_ROOT\LDAP\shell]

[HKEY_CLASSES_ROOT\LDAP\shell\open]

[HKEY_CLASSES_ROOT\LDAP\shell\open\command]
@="\"D:\\Program Files\\Outlook Express\\wab.exe\" /ldap:%1"

I have created these reg files in zip for easy download... see below.

Basically to be able to backup and restore individual Exchange Mailboxes the BackupEXEC Service account needs to be able to have access to all of those mailboxes via MAPI..  If you did not setup this service account during the initial install here is how to do it:

1. Create the account in Active Directory Users and Computers.  NOTE: The first five characters in the account name can not match that of any current/previous account or mailbox. 
   NOTE: DO NOT HIDE THIS ACCOUNT FROM EXCHANGE ADDRESS LISTS!
   
2. Join the account to the Administrators group of the domain.
   
3. Open up “Exchange System Manager“ and drill down to the Exchange Server that your mailbox is located on.  Right click the server name, select properties and then click on the “Security“ tab.  Add the account you just created and give it Full Control.
   
4. Go into Control Panel and open up the Services app.  Double click on all of your Backup EXEC services and have them logon as the service account you created.  You will be told at some point during this that the machine is granting the service the right to logon as a service.  Obviously this is exactly what you want :)
   
5. Once you've done this re-start all the Backup EXEC services.
   
6. Now open up the Domain Controller Security Policy console and drill down like this: Security Settings --> Local Policies --> User Rights Assignment. Double click “Log on locally“ and add the account you created in step 1.
   
7. Now logoff and log back on with the account you created in step 1 and run Backup EXEC.  In case you don't have an icon handy with this account the defalt for the EXE is:
   
   C:\Program Files\VERITAS\Backup Exec\NT\bkupexec.exe
   
8. Select the Backup Selections tab and you should be able to see all the mailboxes you wish to see.

Most PC's conduct Power On Self Tests prior to attempting to boot. Should there be a failure at this stage, you will hear a series of "beeps" which give an indication of the error. The following is a typical set of beep codes, used in AMI WinBios, which may or may not be correct for your particular machine - check your computer or motherboard manual for exact codes for your machine.

Beeps	Error Message
1	Refresh Failure
2	Parity Error
3	Base 64K RAM Failure
4	Timer Not Operational
5	Processor Error
6	Gate A20 Failure
7	Processor Exception Interrupt Error
8	Display Memory Read/Write Error
9	ROM Checksum Error
10	CMOS Shutdown Register Read/Write Error
11	Cache Memory Bad

How to Create a Bootable Disk for an NTFS or FAT Partition

Use a WMI script that changes the volume licensing product key, and then deploy this script in a startup script. The sample ChangeVLKey2600.vbs script and the sample ChangeVLKeySP1 script that are described in this section use the new volume licensing key that you want to enter, in its five-part alphanumeric form, as a single argument. Microsoft recommends that you use the ChangeVLKey2600.vbs script on Windows XP-based computers that are not running SP1 and that you use the ChangeVLKeySP1.vbs script on Windows XP-based computers that are running SP1. These scripts perform the following functions:

They remove the hyphen characters (-) from the five-part alphanumeric product key.
They create an instance of the win32_WindowsProductActivation class.
They call the SetProductKey method with the new volume licensing product key.

You can create a batch file or a CMD file that uses either of the following sample scripts, together with the new product key as an argument, and either deploy it as part of a startup script or run it from the command line to change the product key on a single computer.

----------->
'
' WMI Script - ChangeVLKey.vbs
'
' This script changes the product key on the computer
'
'***************************************************************************

ON ERROR RESUME NEXT

if Wscript.arguments.count<1 then
Wscript.echo "Script can't run without VolumeProductKey argument"
Wscript.echo "Correct usage: Cscript ChangeVLKey.vbs ABCDE-FGHIJ-KLMNO-PRSTU-WYQZX"
Wscript.quit
end if

Dim VOL_PROD_KEY
VOL_PROD_KEY = Wscript.arguments.Item(0)
VOL_PROD_KEY = Replace(VOL_PROD_KEY,"-","") 'remove hyphens if any

for each Obj in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf ("win32_WindowsProductActivation")

result = Obj.SetProductKey (VOL_PROD_KEY)

if err <> 0 then
WScript.Echo Err.Description, "0x" & Hex(Err.Number)
Err.Clear
end if

Next

--------------|

ChangeVLKey2600.vbs

-------------->
'
' WMI Script - ChangeVLKey.vbs
'
' This script changes the product key on the computer
'
'***************************************************************************

ON ERROR RESUME NEXT

if Wscript.arguments.count<1 then
Wscript.echo "Script can't run without VolumeProductKey argument"
Wscript.echo "Correct usage: Cscript ChangeVLKey.vbs ABCDE-FGHIJ-KLMNO-PRSTU-WYQZX"
Wscript.quit
end if

Dim VOL_PROD_KEY
VOL_PROD_KEY = Wscript.arguments.Item(0)
VOL_PROD_KEY = Replace(VOL_PROD_KEY,"-","") 'remove hyphens if any
Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents\OOBETimer" 'delete OOBETimer registry value
for each Obj in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf ("win32_WindowsProductActivation")

result = Obj.SetProductKey (VOL_PROD_KEY)

if err <> 0 then
WScript.Echo Err.Description, "0x" & Hex(Err.Number)
Err.Clear
end if

Next

--------------|

The following example describes how to use the ChangeVLKeySP1.vbs script from a command line:

Click Start, and then click Run.

In the Open box, type the following command, where ab123-456ab-ab789-876ab-ab123 is the new product key that you want to use, and then click OK:

c:\changevlkeysp1.vbs ab123-456ab-ab789-876ab-ab123

List of the more common Stop Messages and their meaning

0x0000000A: IRQL_NOT_LESS_OR_EQUAL - Usually cause by bad driver or incompatible hardware/software.
0x00000012: TRAP_CAUSE_UNKNOWN - Indicates a trap from an unknown cause. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000.
0x0000001A: MEMORY_MANAGEMENT - Indicates a general memory management problem. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system.
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED - Indicates that a kernel-mode exception was not handled. Usually, the exception address pinpoints the driver/function that caused the problem.
0x00000023: FAT_FILE_SYSTEM - Naturally caused by a FAT file system problem. If this is the first time you have booted after installing new hardware, remove the hardware and boot again.
0x00000024: NTFS_FILE_SYSTEM - A problem occurred within NTFS.SYS (the driver file that allows the system to read and write to NTFS file system drives.) There may be a physical problem with the disk, or an IRP may be corrupted.
0x0000002E: DATA_BUS_ERROR - Usually caused by defective RAM(on motherboard or video card). Also can be an indication of damamge to the hard drive due to a virus.
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS - Most often caused by a hardware driver issue.
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA - The requested data was not in memory. Caused by defective memory or incompatible software. Sometimes a hardware problem.
0x00000051: REGISTRY_ERROR - Pretty obvious that this is a registry issue. Usually a registry or configuration management issue.
0x00000058: FTDISK_INTERNAL_ERROR - Indicates an inconsistency between pages in the primary and secondary data caches. This is a fault-tolerant disk driver internal error.
0x0000005A: CRITICAL_SERVICE_FAILED - A critical service failed to initialize while starting the LastKnownGood control set. If this is the first time you have booted after installing new hardware, remove the hardware and boot again.
0x00000077: KERNEL_STACK_INPAGE_ERROR - Kernel data requested from the pagefile could not be found or read into memory. This message also may indicate disk hardware failure,data corruption, or virus.
0x0000007A: KERNEL_DATA_INPAGE_ERROR - Kernel data requested from the pagefile could not be found. Possibly due to incompatible disk or controller drivers, or hardware.
0x0000007B: INACCESSIBLE_BOOT_DEVICE - Caused by installing incorrect device drivers when installing or upgrading storage adapter hardware, or a virus.
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED - Almsot always caused by a hardware compatibility issue.
0x000000A5: ACPI_BIOS_ERROR - Errors in the ACPI BIOS. Nothing can be done at an operating system level to fix the problem.
0x000000B4: VIDEO_DRIVER_INIT_FAILURE - Video driver failed to initialize, video driver issue.
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY - Commonly occurs after installing a faulty device driver. To to correct the problem try disabling or removing the driver.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL - The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver.
0xC0000135: UNABLE TO LOCATE DLL - Windows attempted to load a DLL file and encountered an error condition. So of the possible causes are that the file is missing or damaged, or that the is Registry is corrupt.
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH - Possibly caused by driver problems, system file problems, disk corruption problems or faulty memory.
There are many many other STOP ERROR Messages that can be recieved, this is only a short compilation of some

'Extend the array boundries and add more entries and it should work
' HAVE FUN!
Option Explicit
Private extension(1)
extension(0) = ".txt"
Dim objArgs, argc, spellchk, objFSO, path, objFolder, filecollection, filename, objFile, i, ptr, wordin, wordfile, oDoc, myRange, stat, n, v
Set objArgs = WScript.Arguments
If objArgs.Count < 1 or objArgs.Count > 2 Then
Call Script_Error
End If
Wscript.echo "Text File conversion tool"
Wscript.echo "by James Lane"
wscript.echo ""
wscript.echo "Note: Formatting of files may be lost"
wscript.echo ""
argc = 0
spellchk = 0
Set objFSO = CreateObject("Scripting.FileSystemObject")
Do While argc < CInt(objArgs.Count)
Select Case objArgs(argc)
Case "-s"
spellchk = 1
Case Else
If objFSO.FolderExists(objArgs(argc)) Then
path = objArgs(argc)
Else
Wscript.Echo "Folder does not exist."
Call Script_Error
End If
End Select
argc = argc + 1
Loop
Set objFolder = objFSO.GetFolder(path)
Set filecollection = objFolder.Files
For Each filename In filecollection
Set objFile = objFSO.GetFile(filename)
If objFile.Size > 0 Then
Set objFile = objFSO.OpenTextFile(filename, 1)
If ext(filename) Then
wordin = objFile.ReadAll
wscript.echo "File: " & filename
wscript.echo ""
wordfile = Left(filename, Len(filename) - 4) & ".doc"
Call makeword(wordfile, wordin, spellchk)
wscript.echo ""
End If
End If
Next

Sub Script_Error
WScript.Echo ""
WScript.Echo "Converts txt files to word documents"
WScript.Echo ""
WScript.Echo "Usage: word.vbs [-s] folder"
WScript.Echo ""
WScript.Echo "Options : "
WScript.Echo ""
WScript.Echo "     -s    Runs a SpellCheck on the files as they are converted"
WScript.Echo ""
WScript.Quit
End Sub

Sub makeword(file, content, spellchk)
Set oDoc = CreateObject("Word.Document")
oDoc.Content = content
If spellchk = 1 Then
oDoc.CheckSpelling
oDoc.CheckGrammar
Set myRange = oDoc.Content
For Each stat In myRange.ReadabilityStatistics
n = stat.Name
v = stat.Value
Wscript.Echo "" & n & " : " & v & ""
Next
End If
oDoc.SaveAs file
wscript.sleep 1000
oDoc.Close
Set oDoc = Nothing
End Sub

Function ext(filename)
For i = 0 to (UBound(extension) - 1)
ptr = InstrRev(filename, extension(i), -1, 1) - 1
If (ptr + Len(extension(i))) = Len(filename) Then
    ext = true
    Exit For
Else
ext = false
End If
Next
End Function

The above converts txt files to word documents

Usage: word.vbs [-s] folder
Options : -s Runs a SpellCheck on the files as they are converted

applies to Windows 2000, XP

1. Right-click on the My Computer icon. (Under Windows XP, the My Computer Icon may be located in the start menu.)

2. Choose Properties from the context menu.

(Alternatively, you can double-click on the System icon in the Control Panel)

4. Click the Advanced tab.

5. Click the Environment Variables button.

6. Add the target directory to the end of the Path using a semi-colon as a separator. For example, if you want to add the path to MATLAB/bin to your system, which is located
at c:\roger\bin, you would enter the following at the end of the Path:

;c:\roger\bin

7. Restart your computer for your changes to take affect.

How to setup auto dial up to connect to ISP

To connect ISP automatically when run IE, open IE>Tools>Internet Options>Connection, check Always dial my default connection.

RAID (Redundant Array of Inexpensive Disks) is a method of combining multiple hard drives for data redundancy in case of a hard drive failure.

The different types of supported RAID configurations are:

RAID 0

RAID 1

RAID 5

Non-RAID

Toggle LAN Connection script

Const ssfCONTROLS = 3

sConnectionName = "Local Area Connection"

sEnableVerb = "En&able"
sDisableVerb = "Disa&ble"

set shellApp = createobject("shell.application")
set oControlPanel = shellApp.Namespace(ssfCONTROLS)

set oNetConnections = nothing
for each folderitem in oControlPanel.items
  if folderitem.name  = "Network and Dial-up Connections" then
    set oNetConnections = folderitem.getfolder: exit for
  end if
next

if oNetConnections is nothing then
  msgbox "Couldn't find 'Network and Dial-up Connections' folder"
  wscript.quit
end if

set oLanConnection = nothing
for each folderitem in oNetConnections.items
  if lcase(folderitem.name)  = lcase(sConnectionName) then
    set oLanConnection = folderitem: exit for
  end if
next

if oLanConnection is nothing then
  msgbox "Couldn't find '" & sConnectionName & "' item"
  wscript.quit
end if

bEnabled = true
set oEnableVerb = nothing
set oDisableVerb = nothing
s = "Verbs: " & vbcrlf
for each verb in oLanConnection.verbs
  s = s & vbcrlf & verb.name
  if verb.name = sEnableVerb then
    set oEnableVerb = verb 
    bEnabled = false
  end if
  if verb.name = sDisableVerb then
    set oDisableVerb = verb 
  end if
next

'debugging displays left just in case...
'
'msgbox s ': wscript.quit
'msgbox "Enabled: " & bEnabled ': wscript.quit

'not sure why, but invokeverb always seemed to work
'for enable but not disable. 
'
'saving a reference to the appropriate verb object
'and calling the DoIt method always seems to work.
'
if bEnabled then
'  oLanConnection.invokeverb sDisableVerb
  oDisableVerb.DoIt
else
'  oLanConnection.invokeverb sEnableVerb
  oEnableVerb.DoIt
end if

'adjust the sleep duration below as needed...
'
'if you let the oLanConnection go out of scope
'and be destroyed too soon, the action of the verb
'may not take...
'
wscript.sleep 1000

Info:

To be 100% robust, you should enable inline error handling and explicitly test for "not implemented" and use an alterative approach of an enumerated search of the Folder's FolderItems collection (returned by the Items() method) looking for a FolderItem.Name match. 

If you need the Folder interface rather that FolderItem, use the FolderItem.GetFolder property (yes, it  is  a property despite a method-like name;-).  On the other hand, if you have a Folder interface
and want its FolderItem interface, use the Folder.Self property.  Note the Self was added as of Windows 2000.

By default, simple file sharing is enabled on a Windows XP-based computer if the computer is not a member of a domain. simple file sharing lets you easily share folders with everyone on your workgroup or network and make folders in your user profile private. However, if simple file sharing is enabled, you cannot prevent specific users and groups from gaining access to your shared folders. If you disable simple file sharing, you can allow specific users and groups to gain access to a shared folder.Those users must be logged on with the credentials of user profiles that you've granted access, in order to gain access to your shared folder.

If simple file sharing is enabled, you see the simple file sharing user interface rather than the classic Security and Sharing tabs. By default, this new user interface is implemented in Windows XP Home Edition and in Windows XP Professional if you are working in a workgroup. If you disable simple file sharing, the classic Security and Sharing tabs appear, and you can specify which users and groups have access to shared folders on your computer.

Note You can set security only on a partition that uses the NTFS file system. If you remove the Everyone group from the NTFS permissions, you cannot use the file or folder over the network.

How to disable simple file sharing

1. Click Start, and then click My Computer.
2. On the Tools menu, click Folder Options, and then click the View tab.
3. In the Advanced Settings section, click to clear the Use simple file sharing (Recommended) check box.
4. Click OK.

How to share a folder or a drive with other people

1. Click Start, click My Computer, and then locate the folder or drive you want to share.
2. Right-click the folder or drive, and then click Sharing and Security.
3. On the Sharing tab, click Share this folder.
4. To change the share name of the shared folder or drive, type a new name in the Share name box. The new name is what other people see when they connect to this shared folder or drive. The actual name of the folder or drive does not change.
5. To add a comment about the shared folder or drive, type the text in the Comment box.
6. To limit the number of people who can connect to the shared folder or drive at one time, click Allow under User limit, and then type the number of users.
7. To set shared folder permissions on the shared folder or drive, click Permissions.
   
   Note To share folders and drives, you must be logged on as a member of any one of the following groups:
   • Administrators
   • Server Operators
   • Power Users

Troubleshooting

• The Sharing tab is not visible.
  
  Try using the Services snap-in to start the Server service. To do so:
  1. Click Start, and then click Control Panel.
  2. Click Performance and Maintenance, click Administrative Tools, expand Services and Applications, and then double-click Services.
  3. Right-click the Server service, and then click Start.
• The folder is already shared.
  
  Click New Share, and then type the new share name.
• You want to hide the shared folder.
  
  To hide the shared folder, type $ as the last character of the share name. Other uses cannot see this shared folder when they search by using My Computer or Windows Explorer, but they can map to the shared folder.
• Other users occasionally cannot use your shared folder.
  
  No more than 10 other people can connect to your computer at one time if you are using Windows XP Professional. In Windows XP Professional, the maximum user limit is 10, regardless of the number you type in the Allow box.

You can use the Shared Folders snap-in to create and manage shared folders, view a list of all the users who are connected to a shared folder over a network, disconnect one or all of them, view a list of files opened by remote users, and close one or all the open files. To start the Shared Folders snap-in:

1. Click Start, and then right-click My Computer.
2. Click Manage, and then click Shared Folders

KB: 307874

Hive:  HKEY_LOCAL_MACHINE
Key:  Software\Microsoft\WindowsNT\
  Current Version\Winlogon
Name:  LegalNoticeCaption
Data Type: REG_SZ
Value:  Title shown on the logon notice dialog box

Hive:  HKEY_LOCAL_MACHINE
Key:  Software\Microsoft\WindowsNT\
  Current Version\Winlogon
Name:  LegalNoticeText
Data Type: REG_SZ
Value:  Text shown in the logon notice dialog box

Cannot logon after removing the domain

I have a windows 2000 professional laptop workstation. I used to belong to a domain on my network, but I recently
changed by network settings to belong to a workgroup. Once I restarted my machine, it won't let me log into windows 2000 at all!  The error says wrong user name or domain.  For some reason, I think it's trying to access the domain - even though I don't belong to it anymore. Even when I'm not connected to the network, I cannot log into windows 2000 at all.  How can I get into windows 2000?  How can I change this?!

A: After changing the domain to a workgroup, only the member of local administrators can logon the computer. the resolutions: 1. logon the local administrator to local computer and add the users. 2. If you don't have the administrator password, you may need your network administrator to help you.

Can't remove a computer from a domain

Symptom: When trying to move the computer off of the domain and into a workgroup the following error message is displayed, "The computer could not be removed from the domain <domain name>.  The revision level is unknown."

Resolution: the problem is you may logon local administrator instead of domain administrator. Re-logon domain administrator.

Cannot find the WINS server.

SYMPTOMS: After you install the Windows Internet Name Service (WINS) component, you may not be able to gain access to the WINS database on the local WINS server. When you try to gain access to the WINS database, you may receive the following error message: "Cannot find the WINS server", "The WINS server you specified cannot be located", "The WINS server might be down, there might be network problems, or the WINS service might not be installed", and "The network path was not found".

RESOLUTION: When WINS Manager starts, it tries to contact the File Server service on the WINS server. Specifically, WINS Manager checks for NetBIOS suffix 20 on the WINS server. If File and Printer Sharing is disabled, it disables the File Server service and NetBIOS suffix. You must have File and Printer Sharing enabled to use WINS.

Cannot Add Windows 2000 Computer to Domain: The Network Path Was Not Found

SYMPTOMS: When trying to join a Win2K/XP computer to a domain, you receive the following error message: The following error occurred when attempting to join "domain name". The network path was not found.

RESOLUTION: 1) make sure you are using an correct IP for the DNS. 2) make sure you have correct DNS and WINS server on your network. 3) try to enable NetBIOS over TCP/IP on Win2K/XP if this is NT domain controller.

How to access different domain without changing the network settings

 To use a laptop to access to different domain without changing the domain settings, logon local machine (instead of domain) using your domain logon ID that also are created on your local computer. If it is possible, you may create the same logon id and password on all domain so that you always are able to access the domain you are connecting to. Also you may want to create one batch file like logon.bat with domain logon ID and password to map network drives.

How to change the network information for a Domain Controller

When you try to change the network information to a domain comptroller, you find the Network ID and Properties buttons will not be available. The way to change the network information on a domain controller would be to demote the controller to a member server, change the necessary information, and then promote the server back to a domain controller.

How to check who is logging on a particular computer

If you would like to check who is  logging on a particular PC in the (same subnet) network, you can use command nbtstat -a computername. That will show NetBIOS Remote Machine Name Table such as username, <03>, type and status.

How to map a network drive without logon the domain

If you have a laptop used at home and sometimes used in the office, you would  like to map a network drive without logon the domain, you can create a batch file like that  “net use h: \\ervername\sharename password /user:domainname\username".

How to synchronize the time on all the computers in a network

To synchronize the time on all the computers in a network, create a logon script and use net time command, for example, net time \\computername /set /yes.

How to switch network settings without reboot

As a network consultant, I work on different network every day and need to switch network settings such as IP and DNS accordingly. Fortunately, W2K/XP comes with a useful tool, netsh.exe, that can switch network settings quickly.  To copy abc.com network settings, type command netsh -c interface dump >c:\abc.txt. The abc.com network settings will be saved at the root of the C drive. You can create as many network settings as I like. When you work at abc.com next time,  you will load the settings by typing netsh -f abc.txt command and the abc.com network settings will take effect immediately.

How to verify if you are logged on to the domain and  which server you are logging on

To verify if you are logging on to the domain and  which server you are logging on, at a command prompt, type set, and then press ENTER. Look for the LOGONSERVER entry. If it is set to the name of your computer, you were logged on using cached domain credentials. If you are logging on the domain, the LOGONSERVER entry is set to one of the domain controllers.

How can I synchronize all computers' time in the network?

A: You as an Administrators can configure an internal time server as authoritative by using the net time command.

You can also configure the Time Service on the AD to recognize an external Simple Network Time Protocol (SNTP) time server as authoritative. Use the following net time command: net time /setsntp:server_list. Note: 1) The United States Naval Observatory runs several SNTP time servers that are satisfactory for this function, for example, ntp2.usno.navy.mil (at 192.5.41.209) and tock.usno.navy.mil (at 192.5.41.41). 2) that SNTP uses User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers.

After you set the SNTP time server as authoritative, run the following command on computers other than the domain controller to reset the local computer's time against the authoritative time server: net time \\servername /set /yes.

How do I un-synchronize time on my domain network?

Q:  I have an isolated Windows 2000/NT domain for I/O testing. I want to change TIME on one of my W2K server; however after approx. 30min. the TIME of this server was reset back to my domain time.

A:  You can disable the 'Windows Time' service on the computer you don't want to update.

Mapping problem - persistent connection

After you changed net use I: \\serverA\shared  to \\serverB\shared in your logon script, some windows 2000 machines are still mapping to \\serverA\shared. The reason is that net use /persistent:yes is default settings for NT and win2000/XP.   You can disconnect the old mapping and re-logon. That will map to \\cbgntB\shared.  Also you may want to use NET USE I: \\servername\folder /persistent:no so that next time when we change the mapping, it will automatically map to the new settings.

Problem with License Manager
I have followed the instructions in Q153140 and Q194065 on how to reset License Manager information.  Two days later, I am getting warnings in my Event Logs that my Windows Server is out of licenses.  Its finding ghost users that have been deleted from my system for 3-4 years  How do I  really delete their licenses and  make them stop coming back?

A: Many  people have reported the same problem. You may want to disable the License Manager and manage the licenses manually.

Slow Network Performance Occurs while copying file to W2K Domain Control

A: Symptom: when copying files from a client computer to W2K domain controller, network performance is slower. You may notice this problem occurs only if you copy many small files but not copy a few large files. Resolution: 1) apply SP3 on the W2K domain controller; 2) edit the TcpDelAckTicks registry value to adjust the TCP delayed ACK timer (refer to MS Q321098).

Unable to logon domain or experience an extremely slow logon -  Event ID: 1054

First, download the IE6 SP1 setup program from HERE (500kb basic setup program. The full IE package might go as high as ~44mb depending upon your selection). This tip will let you customize the d/l parameters.

Go to the folder where you've placed the above file. Open a Command Prompt (CMD) in that folder, then run the following command in the CMD window:

ie6setup.exe /c:"ie6wzd.exe /d /s:""#E"

Note: Just copy and paste the above line. Don't try to be a wise guy. Copy the damn line! I've received quite a few feedbacks about the accuracy of this tip, and always they got the syntax wrong. Copy and paste! Oh, and yes, this tip works for IE 6 SP1 too, and so will older IE versions. Just replace the "6" in the previous line with a "5" and so on.

You can also choose to download all IE versions in one go. For example, if you choose to download the version for Win9X, the version for NT, the version for W2K, and the version for Win ME - all the files will go to one location - a folder named "Windows Update Setup Files" - and you can then burn this folder to a CD and use it to install IE on any OS version you want.

When you try to establish a dial-up connection after you upgrade your computer to Microsoft Windows XP from Microsoft Windows 98, from Microsoft Windows 98 Second Edition, or from Microsoft Windows Millennium Edition (Me), you may receive an error message that is similar to one of the following:

Error 721: The remote computer is not responding.
Error 678: The remote computer failed to respond.
Error 691: Access was denied because the user name and/or password was invalid on the domain.
Error 777: The connection attempt failed because the modem or other connecting device on the remote computer is out of order.

This issue may occur if the modem driver is not compatible with Windows XP. This issue has been reported to occur with Lucent Win modems that are included with the following Hewlett-Packard (HP) computers:
HP Pavilion 6736
HP Pavilion 6745c
HP Pavilion 7400
HP Pavilion 7800
HP Pavilion 7845
HP Pavilion 7850
HP Pavilion 7855
HP Pavilion 7940
HP Pavilion 8655
HP Pavilion 8756c
HP Pavilion XT846
HP Pavilion XT856
HP Pavilion XT923

To resolve this issue, contact the hardware manufacturer to inquire about how to obtain and install the latest Windows XP-compatible driver for the modem. For more information about how to contact HP, visit the following HP Web site:
http://welcome.hp.com/country/us/eng/software_drivers.htm
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
For more information about how to contact Agere Systems (the manufacturer of the modem chipset) to inquire about a modem driver that is compatible with Windows XP, visit the following Agere Web site:
http://www.agere.com/support

314455 "Error 691" error message when you try to connect to your ISP
308022  Resources for troubleshooting modem problems in Windows XP

• You can modify the SMTP address of, or add a new SMTP address to, the users who are encountering the error described in the "Symptoms" section of this article. You may want to do this if the problem is confined to a few users or only users who have incorrect SMTP addresses.
• Modify the SMTP domain serviced by the Exchange virtual directory. You may want to do this if most or all of the users in your organization are encountering the error described in the "Symptoms" section of this article.
• Create additional virtual directories for additional SMTP domains. You may want to do this if your organization has multiple SMTP domains or if you are using Exchange 2000 for hosting.
  
  NOTE: You can also create additional HTTP Virtual Servers for additional SMTP domains. This process is more involved than the scope of this article. To set up additional HTTP virtual servers, please see the online Help for Exchange 2000 Sever by visiting following Microsoft Web site:

  http://www.microsoft.com/exchange/en/60/exhelp/

  Click Outlook Web Access, then click How To..., , and then click Create a New HTTP Virtual Server.

Method 1: Correct or Add an SMTP Address to a User

1. Start the Active Directory Users and Computers snap-in.
2. Obtain properties of the user in question. (Users can exist in more than one Organizational Unit but, by default, they are created in the Users OU.)
3. Click the E-mail Addresses tab.
4. If you want to add an SMTP address to this user, click New, double-click SMTP Address, and then type an address that matches the Mailboxes For value noted from properties of the Exchange virtual directory.
5. If you want to modify an existing SMTP address, click the address that you want to modify, click Edit, and type an address that matches the Mailboxes For value.
6. Click OK twice.

Method 2: Modify the SMTP Domain Serviced by the Exchange Virtual Directory

1. Start Exchange System Manager.
2. Expand the Recipients container.
3. Select the Recipient Policies object.
4. In the right pane, locate the Default Policy and obtain the properties.
5. Click the E-mail Addresses tab.
6. Double-click the SMTP address. If there is more than one SMTP address listed, double-click the one in bold.
7. Leave the "@" (at sign) at the beginning and type the SMTP domain you want in the Address field.
8. Click OK twice.
9. Start the Services snap-in.
10. Select the Microsoft Exchange Information Store service.
11. Click the Restart Service button on the Microsoft Management Console (MMC) toolbar. When prompted to restart dependent services, click Yes. The Mailboxes For value will be updated to use your new SMTP domain.

Method 3: Create Additional Virtual Directories for Additional SMTP Domains

1. Start Exchange System Manager.
2. Locate the Servers/server name/Protocols/HTTP/Exchange Virtual Server folder.
3. Right-click the Exchange Virtual Server, click New, and then click Virtual Directory.
4. Type the name of the new virtual directory.
   
   This name will appear in the URL used by clients to access this new virtual directory. For example, if you create a new virtual directory named companybmail, clients will have to access a URL similar to http://www.domain.com/companybmail/.
5. To select an SMTP domain, click the Modify button, and then select an SMTP domain from the list.NOTE: This list is generated from all SMTP Address values in all recipient policies defined in your Exchange organization. You cannot supply an SMTP domain that does not appear in this list.

Below is the script to perform this task....

=======================>START

:: DNSdump

:: PURPOSE - Dumps local server's DNS service configuration and zone content. Once dumped, the content
::           can be imported on any other Windows 2000/2003 based DNS server [includes cross OS dumps]

:: DNSdump V2.0 is INCOMPATIBLE with the current public release

:: Supports Windows 2000/2003 members or DCs including Active Directory integrated zones. Application
:: partitions are supported

:: Requires Administrative credentials on local machine. If the DNS server is also a Domain Controller,
:: Domain Administrative credemtials are required in order to export or import Active Directory integrated
:: DNS zones

:: Active Directory integrated zones exported from the domain NC will be translated to the local domain
:: NC in the event of a cross domain export/import. Further behavioral details documented in syntax help

@echo off
setlocal ENABLEDELAYEDEXPANSION

:: Prepare the display
echo.

:: Define environment
set TOOLNAME=DNSdump
set KNOWNPATH=25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,53,79,73,74,65,6d,33,\
set INSTALLROOT=%SystemRoot%\System32\DNS
set DUMP=%~f2
set STDOUT=nul
set STDERR=nul
set WORKING=0
set ERROR=
set domainDN=
set domainDNS=
set SUPPORTEDBUILDS=2195 3790

:: Check local server meets necessary requirements for successful operation

:: Derive operating system version and validate support
for /f "tokens=3 delims=.]" %%v in ('ver') do set BUILD=%%v
for %%s in (%SUPPORTEDBUILDS%) do (
 if not "%%s"=="%BUILD%" (
  if "!ERROR!"=="" set ERROR=1
 ) else (
  set ERROR=0
 )
)
if not "%ERROR%"=="0" (
 call :ERROR unsupported operating system version, build "%BUILD%"
 goto :END
)

:: Check for sufficient arguments
if "%2"=="" (
 call :ERROR insufficient arguments
 call :SYNTAX
 goto :END
)

:: Correct and/or report any errors in the dump directory argument
set DUMP=%DUMP:"=%
set TDUMP=%DUMP: =%
if not "%TDUMP%"=="%DUMP%" (
 call :ERROR dump path CANNOT contain spaces, "%DUMP%"
 goto :END
)

:: Locate critical executables, error and terminate if not found
for %%e in (net.exe findstr.exe ldifde.exe regedit.exe) do (
 set where="%%~$PATH:e"
 if "!where!"=="""" (
  call :ERROR critical executable, "%%e", could not be located 
  goto :END
 )
)
 
:: Determine if DNS service is installed on local machine
regedit /E:A "%TEMP%\DNS-Service.TMP" HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS
if not exist "%TEMP%\DNS-Service.TMP" (
 call :ERROR DNS service does not appear to be installed on "%COMPUTERNAME%"
 goto :END
)

:: Check local credentials
net user "%username%" | findstr /i "Administrators" 1>%STDOUT% 2>%STDERR%
if errorlevel 1 (
 net user "%username%" | findstr /i /c:"Domain Admins" 1>%STDOUT% 2>%STDERR%
 if errorlevel 1 (
  call :ERROR security context is insufficient, administrative credentials required
  goto :END
 )
)

:: Determine if local machine is member or Domain Controller
regedit /E:A "%TEMP%\DCorMember.TMP" "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions"
if not exist "%TEMP%\DCorMember.TMP" (
 call :ERROR unable to determine machine configuration [DC or member]
 goto :END
)
for /f "tokens=2 delims==" %%t in ('type "%TEMP%\DCorMember.TMP" ^| findstr "ProductType"') do (
 if /i "%%t"==""LanmanNT"" (set TYPE=DC) else (set TYPE=MEMBER)
)

:: Get DNS domain name of local machine
if "%TYPE%"=="DC" (
 regedit /E:A "%TEMP%\NTDS-Service.TMP" HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters
 if not exist "%TEMP%\NTDS-Service.TMP" (
  call :ERROR Directory Service configuration could not be determined
  goto :END
 )
 for /f "tokens=1* delims==" %%s in ('type "%TEMP%\NTDS-Service.TMP" ^| findstr "sysvol"') do (
  set SYSVOL=%%t
  set SYSVOL=!SYSVOL:\\=\!
  for /f "tokens=2 delims=>" %%d in ('dir !SYSVOL! /ad ^| findstr "JUNCTION"') do (
   set domainDNS=%%d
   set domainDNS=!domainDNS: =!
  )
 )
 if "!domainDNS!"=="" (
  call :ERROR Directory Service configuration could not be determined
  goto :END
 )
 call :DERIVEDN "!domainDNS!"
 set domainDN=!partDN!
)

:: Begin script body

:: Determine mode of operation
if /i "%1"=="IMPORT" (
 set MODE=IMPORT
)  else (
 if /i "%1"=="EXPORT" (
  set MODE=EXPORT
 ) else (
  call :ERROR invalid mode specified, "%1"
  call :SYNTAX
  goto :END
 )
)

:: React to derived mode and create/verify dump directory structure
if "%MODE%"=="EXPORT" (
 if exist "%DUMP%" (
  call :ERROR dump directory already exists, "%DUMP%"
  goto :END
 ) else (
  md "%DUMP%" 2>%STDERR%
  if errorlevel 1 (
   call :ERROR unable to create dump directory, "%DUMP%"
   goto :END
  )
  md "%DUMP%\InstallRoot" 2>%STDERR%
  if errorlevel 1 (
   call :ERROR unable to create directory, "%DUMP%\InstallRoot"
   goto :END
  )
  md "%DUMP%\Logs" 2>%STDERR%
  if errorlevel 1 (
   call :ERROR unable to create log directory, "%DUMP%\Logs"
   goto :END
  )
 )
) else (
 if not exist "%DUMP%" (
  call :ERROR specified dump directory NOT found, "%DUMP%"
  goto :END
 )
)

:: Define custom DNS service installation root if supplied
if not "%3"=="" (
 set INSTALLROOT=%~f3
 if not exist "%INSTALLROOT%" (
  call :ERROR DNS installation root, "%INSTALLROOT%", is invalid
  goto :END
 )
) else (

:: Query DNS service registry key for install root ... if non-standard, error
 for /f "delims=: tokens=2" %%i in ('type "%TEMP%\DNS-Service.TMP" ^| findstr /i "ImagePath"') do set ACTUALPATH=%%i
 if not "%KNOWNPATH%"=="!ACTUALPATH!" (
  call :ERROR non-standard DNS installation root, specify zone file path
  set ERROR=2
  goto :END
 )
 if not exist %INSTALLROOT% (
  md %INSTALLROOT%
  if errorlevel 1 (
   call :ERROR unable to create DNS installation root, "%INSTALLROOT%"
   goto :END
  )
 )
)

:: Export only the non locally critical DNS service registry keys to dump directory
if "%MODE%"=="EXPORT" (
 regedit /E:A "%DUMP%\DNS-Service-LegacyZones.REG" HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS\Zones
 regedit /E:A "%TEMP%\DNS-Service-Parameters.TMP" HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DNS\Parameters
 if not exist "%TEMP%\DNS-Service-Parameters.TMP" (
  call :ERROR unable to retrieve DNS service configuration
  set ERROR=2
  goto :END
 )
 type "%TEMP%\DNS-Service-Parameters.TMP" | findstr /v /i "PreviousLocalHostname" >"%DUMP%\DNS-Service-Parameters.REG"
 if not exist "%DUMP%\DNS-Service-Parameters.REG" (
  call :ERROR unable to retrieve DNS service configuration
  set ERROR=2
  goto :END
 )
)

:: Set working directory and indicate state
pushd "%DUMP%" 1>%STDOUT% 2>%STDERR%
echo %TOOLNAME% - Ready to proceed, configuration as follows -
echo.
echo    * Security context is "%USERDOMAIN%\%USERNAME%"
echo    * Mode of operation is "%MODE%"

if "%TYPE%"=="DC" (
 echo    * Domain Controller detected
 echo    * Active Directory domain name is "%domainDNS%"
 set /p nul=   * Active Directory integrated zones WILL be %MODE%ED <nul
 if "%BUILD%" GTR "2195" (
  echo - NDNC's supported
 ) else (
  echo - NDNC's NOT supported
 ) 
) else (
 echo    * Non Domain Controller detected
 echo    * Active Directory integrated zones UNAVAILABLE
)

echo    * DNS installation root is "%INSTALLROOT%"
echo    * %TOOLNAME% directory is "%DUMP%"
echo.
echo STATUS - Task progress ...
echo.

:: Set WORKING to TRUE and jump to mode
set WORKING=1
goto :%MODE%

:: Should never get here - FATAL ERROR
call :ERROR a fatal unknown error occurred
set ERROR=2
goto :END

:: Define procedures

:IMPORT

:: Check the import directory for valid dump configuration
if not exist "%DUMP%\DNS-Service-Parameters.REG" (
 call :ERROR unable to retrieve DNS service configuration
 goto :END
)
if not exist "%DUMP%\DNS-Software.REG" (
 echo    - legacy "Zones" configuration detected ... LEGACY USED
)

:: Stop the DNS service
echo    - stopping DNS service
net stop dns 2>&1 | findstr /i /c:"not exist" 1>%STDOUT% 2>%STDERR%
if not errorlevel 1 (
 call :ERROR unable to stop DNS service
)

:: Create .REG file to remove existing registry based DNS service configuration
echo    - removing existing DNS service configuration
echo REGEDIT4>%TEMP%\KillKeys.REG
echo.>>%TEMP%\KillKeys.REG
echo [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters]>>%TEMP%\KillKeys.REG
echo [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Zones]>>%TEMP%\KillKeys.REG

:: Execute the removal
if exist %TEMP%\KillKeys.REG (
 regedit /s %TEMP%\KillKeys.REG
) else (
 call :ERROR existing configuration could NOT be removed
)

:: Delete the temporary registry file
del %TEMP%\KillKeys.REG 1>%STDOUT% 2>%STDERR%

:: Import the registry data
echo    - reconfiguring DNS service
for %%r in ("%DUMP%\DNS-Service-Parameters.REG" "%DUMP%\DNS-Software.REG" "%DUMP%\DNS-Service-LegacyZones.REG") do (
 if exist %%r (
  regedit /s %%r
 ) else (
  if not "%%r"==""%DUMP%\DNS-Service-LegacyZones.REG"" (
   call :ERROR unable to reconfigure DNS service registry settings
  )
 )
)

:: Restore the DNS config./zone files
echo    - restoring DNS service configuration files to "%INSTALLROOT%"
xcopy "%DUMP%\InstallRoot\*.*" "%INSTALLROOT%" /h /y 1>%STDOUT% 2>%STDERR%
if errorlevel 1 (
 call :ERROR unable to export configuration files to "%INSTALLROOT%"
 goto :END
)

:: Restore the Active Directory integrated zones
:: Check the type (DC or member), if member skip, if DC import all files with extension .ADzones
if "%TYPE%"=="DC" if exist "%DUMP%\*.ADzones" (
 echo    - importing Active Directory integrated DNS zones from;
 echo.
 for /f %%z in ('dir /b "%DUMP%\*.ADzones"') do (
  set tmpPART=%%~nz
  if /i "!tmpPART:~0,9!"=="CN=System" (
   call :NCIMPORT !tmpPART!
  ) else (
   if not "%BUILD%" GTR "2195" (
    echo       * !tmpPART!
    echo          - unsupported partition detected ... IGNORED
    set ERROR=1
   ) else (
    call :NCIMPORT !tmpPART!
   )
  )
 echo.
 )
)

:: Start the DNS service
echo    - restarting DNS service
net start dns 2>&1 | findstr "invalid" 1>%STDOUT% 2>%STDERR%
if not errorlevel 1 (
 call :ERROR unable to start DNS service
)

:: Determine level of success
echo.
if "%ERROR%"=="1" (
 echo STATUS - Import partially completed ... ERRORS OCCURRED
) else (
 echo STATUS - DNS service configuration completed
)

goto :END

:: Handles export of DNS configuration and zone content
:EXPORT

echo    - exporting DNS service configuration

if not exist "%DUMP%\DNS-Service-Parameters.REG" (
 call :ERROR unable to retrieve DNS service configuration
 goto :END
)

:: Construct partition information
echo "%domainDNS%">"%DUMP%\PartitionFQDN.DAT"

regedit /E:A "%DUMP%\DNS-Software.REG" "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server"

:: Alert user to legacy storage of zone configuration
:: Else clause derives partitions in which zones exist and assumes domain NC as potential candidate
if not exist "%DUMP%\DNS-Software.REG" (
 echo    - legacy "Zones" key located ... LEGACY CONFIGURATION USED
) else (
 for /f "tokens=2 delims==" %%z in ('type "%DUMP%\DNS-Software.REG" ^| findstr "DirectoryPartition"') do (
  echo %%z>>"%DUMP%\PartitionFQDN.DAT"
 )
)

:: Copy existing DNS install root
echo    - exporting DNS service file structure from "%INSTALLROOT%"
copy "%INSTALLROOT%\*.*" "%DUMP%\InstallRoot" /y 1>%STDOUT% 2>%STDERR%
if errorlevel 1 (
 call :ERROR unable to backup DNS installation root, "%INSTALLROOT%"
 set ERROR=2
 goto :END
)

:: Exports Active Directory integrated zones if running on a DC
:: Removes objectGUID references in order to permit import
if "%TYPE%"=="DC" (
 echo    - exporting Active Directory integrated Zones from;
 echo.
 if not exist "%DUMP%\PartitionFQDN.DAT" (
  call :ERROR unable to derive partitions containing DNS zones
 )
 for /f "tokens=*" %%d in ('type "%DUMP%\PartitionFQDN.DAT"') do (
  call :DERIVEDN %%d
  ldifde -s localhost -d "CN=MicrosoftDNS,!partDN!" -f "%DUMP%\!partDN!.ADtmpZones" -j "%DUMP%\Logs" | findstr /i /c:"No Entries found" 1>%STDOUT% 2>%STDERR%
  if not errorlevel 1 (
   set ERROR=1
   echo       * !partDN! - UNHANDLED ERRORS
  ) else (
   echo       * !partDN!
  )
  echo          - preparing zones for import
  echo.
  type "%DUMP%\!partDN!.ADtmpZones" | findstr /v "objectGUID" >"%DUMP%\!partDN!.ADzones"
  del "%DUMP%\!partDN!.ADtmpZones" 2>%STDERR%
  call :LOGS %!partDN!
 )
)

:: Determine level of success
echo.
if not "%ERROR%"=="0" (
 echo STATUS - Export partially completed ... ERRORS OCCURRED
) else (
 echo STATUS - Export completed successfully
)
goto :END

:: End script body

:: Define procedures and error/syntax routines

:: Receives a fully qualified domain name as argument 1 and converts it to a distinguished name
:DERIVEDN
set partDN=%*
set partDN=%partDN:~1,-1%
set partDN=.%partDN%
set partDN=%partDN:.=,DC=%
set partDN=%partDN:~1%
if /i "%domainDN%"=="%partDN%" (
 set partDN=CN=System,%partDN%
)
goto :EOF

:: Import supplied naming context and handle logged output
:NCIMPORT

:: Translate DN references for domain NC integrated zones such that a zone exported from a DC in one domain
:: can be imported into the domain NC of a DC in another
if /i "%tmpPART:~0,9%"=="CN=System" (
 if not "%tmpPART:~10%"=="%domainDN%" (
  set APPEND=-c %tmpPART:~10% %domainDN%
  set logDN=CN=System,%domainDN%
 ) else (
  set APPEND=
  set logDN=%*
 )
) else (
 set APPEND=
 set logDN=%*
)

ldifde -s localhost -i -k -f "%*.ADzones" -j "%DUMP%\Logs" %APPEND% | findstr /i "error" 1>%STDOUT% 2>%STDERR%
if not errorlevel 1 (
 echo       * %* ... UNHANDLED ERRORS
 set ERROR=1
) else (
 echo       * %*
)

if not "%APPEND%"=="" (
 echo          - cross domain EXPORT/IMPORT detected, domain DN's translated
 echo            ... "%tmpPART:~10%" to "%domainDN%"
)

call :LOGS %logDN%
goto :EOF

:: Rename logged entries for each partition exported or imported in order preserve each log
:LOGS
del "%DUMP%\Logs\*-%MODE%.LOG" 1>%STDOUT% 2>%STDERR%
del "%DUMP%\Logs\*-%MODE%.ERR" 1>%STDOUT% 2>%STDERR%
ren "%DUMP%\Logs\ldif.log" "[%*]-%MODE%.LOG" 1>%STDOUT% 2>%STDERR%
ren "%DUMP%\Logs\ldif.err" "[%*]-%MODE%.ERR" 1>%STDOUT% 2>%STDERR%
goto :EOF

:: Displays errors
:ERROR
if "%WORKING%"=="1" (
 echo    - FAILED ... %*
) else (
 echo ERROR - %*
)
set ERROR=1
goto :EOF

:: Provides assistance with syntax
:SYNTAX
echo.
echo SYNTAX - %TOOLNAME% [IMPORT^|EXPORT] [dump directory] ^<optional install root^>
echo.
echo   * [IMPORT] imports a %TOOLNAME% exported DNS service configuration
echo   * [EXPORT] exports the existing DNS service configuration
echo   * [dump directory] is a local, writable directory path
echo   * [install root] is the local absolute path used by the DNS service
echo.
echo   * %TOOLNAME% requires -
echo     - administrative credentials
echo     - local execution on the DNS server
echo     - Microsoft Windows 2000/2003 server family, builds %SUPPORTEDBUILDS%
echo.
echo   * %TOOLNAME% provides import and export of -
echo     - DNS service configuration
echo     - Active Directory integrated zones and zone configuration
echo     - standard zone files and zone configuration
echo.
echo   * %TOOLNAME% feature notes -
echo     - existing Active Directory zones will NOT be overwritten during IMPORT
echo     - manually erase existing zones IF an authoritative import IS REQUIRED
echo     - ALL zone configuration options WILL be overwritten during IMPORT
echo     - non Active Directory integrated zones WILL be overwritten during IMPORT
echo     - existing DNS service configuration WILL be overwritten during IMPORT
echo     - DNS service WILL be restarted during IMPORT
echo     - detailed logs are preserved beneath the specified DUMP path
goto :EOF

:END

:: Restore previous working directory
popd

:: Clean up
del "%TEMP%\DNS-Service.TMP" 1>%STDOUT% 2>%STDERR%
del "%TEMP%\DNS-Service-Parameters.TMP" 1>%STDOUT% 2>%STDERR%
del "%TEMP%\NTDS-Service.TMP" 1>%STDOUT% 2>%STDERR%
del "%TEMP%\DCorMember.TMP" 1>%STDOUT% 2>%STDERR%

if "%ERROR%"=="2" (
 if "%MODE%"=="EXPORT" (
  del "%DUMP%\InstallRoot" /f /y 1>%STDOUT% 2>%STDERR%
  rd "%DUMP%\InstallRoot" 1>%STDOUT% 2>%STDERR%
  del "%DUMP%\Logs" /f /y 1>%STDOUT% 2>%STDERR%
  rd "%DUMP%\Logs" 1>%STDOUT% 2>%STDERR%  
  del "%DUMP%" /f /q 1>%STDOUT% 2>%STDERR%
  rd "%DUMP%" 1>%STDOUT% 2>%STDERR%
 )
)

=======================>END

This is a utility to (re)set the password of any user that has a valid (local) account on your NT system, by modifying the crypted password in the registrys SAM file. You do not need to know the old password to set a new one.

If you need to reset the DOMAIN admin password see the link below: Reset domain Password

It works offline, that is, you have to shutdown your computer and boot off a floppydisk or CD. The bootdisk includes stuff to access NTFS partitions and scripts to glue the whole thing together. Works with syskey (no need to turn it off, but you can if you have lost the key) Will detect and offer to unlock locked or disabled out user accounts!

NT stores it's user information including crypted versions of the passwords in a file called 'sam', usually found in \winnt\system32\config. This file is a part of the registry, in a binary format previously undocumented, and not easily accessible. But thanks to a German(?) named B.D, I've now made a program that understands the registry. As far as I know, Microsoft provides no way of changing the password if you cannot log in as someone with appropriate privileges, except restoring the registry files from the rescuefloppy.

• You don't forget passwords?
• You never get boxes to admin when someone quits suddenly?
• Your vendor delivers a preconfigured system to you, but never have "freak" accidents and lose the password they've set on it?
• If so, what are you doing reading this?? Go read propaganda from your favourite software vendor instead.

If you have the CD, all drivers are included. If you use the floppy, and you need the SCSI-drivers set, either prepare a floppy with the scsi-drivers .zip file unzipped (in \scsi), or put a selection of the drivers you need in the \scsi folder on the main floppy, there should be enough space for at least 4-5 drivers. In the latter case you don't need to carry around and swap floppies.

Overview
Disk select, tell which disk contains the Windows system. Optionally you will have to load drivers.
PATH select, where on the disk is the system?
File select, which parts of registry to load, based on what you want to do.
Password reset or other registry edit.
Write back to disk (you will be asked)
DON'T PANIC!! - Most questions can usually be answered with the default answer which is given in [brackets]. Just press enter/return to accept the default answer.

1. DISK SELECT
Which disk contains your Windows system?

=========================================================
. Step ONE: Select disk where the Windows installation is
=========================================================
Disks:
Disk /dev/ide/host0/bus0/target0/lun0/disc: 2147 MB, 2147483648 bytes
NT partitions found:
 1 :   /dev/ide/host0/bus0/target0/lun0/part1    2043MB  Boot

Please select partition by number or
a = show all partitions, d = load new disk drivers
l = relist NTFS/FAT partitions, q = quit
Select: [1]

For most machines only one disk and parition is listed, if so, just go with selection 1 (default)
Otherwise select partition
If no disks or not all disks are shown, you may need to load disk drivers, for SCSI-controllers (or some IDE-raid controllers). Select d to go to the driver select menu.
2. HOW TO LOAD DRIVERS
Skip this if it is not needed.
Select: [1] d
==== DISK DRIVER / SCSI DRIVER select ====
You may now insert or swap to the SCSI-drivers floppy
Press enter when done:
Found 1 floppy drives
Found only one floppy, using it..
Selected floppy #0
Mounting it..
Floppy selection done..
SCSI-drivers found on floppy:

1 BusLogic.o.gz
2 aic7xxx.o.gz
3 sym53c8xx.o.gz
[ ... ]

SCSI driver selection:
  a - autoprobe for the driver (try all)
  s - swap driver floppy
  q - do not load more drivers
  or enter the number of the desired driver

SCSI driver select: [q]

Select a for auto-probe, it will try to load all drivers, and stop when one loads properly. Some drivers may need more driver modules, so you may have to redo the auto-probe several times.
Or if you know what you want, just enter it's number or name.
SCSI driver select: [q] a
[ BusLogic.o.gz ]
Using /tmp/scsi/BusLogic.o
PCI: Found IRQ 11 for device 00:10.0

[.... lots of driver / card info ...]

scsi0: *** BusLogic BT-958 Initialized Successfully ***
scsi0 : BusLogic BT-958
  Vendor: FooInc   Model: MegaDiskFoo  Rev: 1.0
  Type:   Direct-Access                      ANSI SCSI revision: 02

[ ... ]

Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 8388608 512-byte hdwr sectors (4295 MB)
Partition check:
 /dev/scsi/host0/bus0/target0/lun0: p1
Driver BusLogic.o.gz loaded and initialized.

You may then quit the selection with q or try for more drivers.
When you quit, you will get back to the disk select (see above) and hopefully see more disks.

3. PATH AND FILE SELECT
Where's the Windows system located?
On the selected partition/disk, the main files for windows can theoretically be anywhere. And we must find the registry files to be able to edit them. There are however some usual places:

winnt35/system32/config - Windows NT 3.51
winnt/system32/config - Windows NT 4 and Windows 2000
windows/system32/config - Windows XP/2003 and often Windows 2000 upgraded from Windows 98 or earlier.
These usual paths will be checked, and if found, they will be suggested as the default.

Selected 1
Mounting on /dev/ide/host0/bus0/target0/lun0/part1
NTFS volume version 3.1.
Filesystem is: NTFS

=========================================================
. Step TWO: Select PATH and registry files
=========================================================
What is the path to the registry directory? (relative to windows disk)
[windows/system32/config] :
-r--------    1 0        0          262144 Jan 12 18:01 SAM
-r--------    1 0        0          262144 Jan 12 18:01 SECURITY
-r--------    1 0        0          262144 Jan 12 18:01 default
-r--------    1 0        0         8912896 Jan 12 18:01 software
-r--------    1 0        0         2359296 Jan 12 18:01 system
dr-x------    1 0        0            4096 Sep  8 11:37 systemprofile
-r--------    1 0        0          262144 Sep  8 11:53 userdiff

Select which part of registry to load, use predefined choices
or list the files with space as delimiter
1 - Password reset [sam system security]
2 - RecoveryConsole parameters [software]
q - quit - return to previous
[1] :

If the directory is correct, something like the above will be listed (it may vary a bit..)
You may then choose some canned answers based on what you want to do.
Password reset is the default, and most used.
Option 2, RecoveryConsole is for setting 2 parameters that the Windows 2000 and newer RecoveryConsole (boot from CD, select Recovery and console mode) uses. One of the parameters allows RecoveryConsole to be run without it prompting for the admin password. If you do not know what RecoveryConsole is, don't bother. Or go search the net..
Or if you want to do manual edit of registry, select your hives to load. Enter all names on one line with space between.
We select 1 to edit passwords..

4. PASSWORD RESET
Everything is set and ready, let's roll!

=========================================================
. Step THREE: Password or registry edit
=========================================================
chntpw version 0.99.2 040105, (c) Petter N Hagen

[.. some file info here ..]

* SAM policy limits:
Failed logins before lockout is: 0
Minimum password length        : 0
Password history count         : 0

<>========<> chntpw Main Interactive Menu <>========<>

Loaded hives:

  1 - Edit user data and passwords
  2 - Syskey status & change
  3 - RecoveryConsole settings
      - - -
  9 - Registry editor, now with full write support!
  q - Quit (you will be asked if there is something to save)

What to do? [1] -> 1

===== chntpw Edit User Info & Passwords ====

RID: 01f4, Username:
RID: 01f5, Username: , *disabled or locked*
RID: 03e8, Username: , *disabled or locked*
RID: 03eb, Username: , *disabled or locked*
RID: 03ea, Username: , *disabled or locked*

Select: ! - quit, . - list users, 0x - User with RID (hex)
or simply enter the username to change: [Administrator]

Here you can enter the username you want to reset the password for. NOTE: It is case-sensitive, write it exact as listed (without the < and > of course)

Or if the name uses some characters that cannot be displayed, enter it's ID number (RID), like this: 0x1f4 would select administrator.

We select the default, which is administrator.

RID     : 0500 [01f4]
Username: Administrator
fullname:
comment : Built-in account for administering the computer/domain
homedir :

Account bits: 0x0210 =
[ ] Disabled        | [ ] Homedir req.    | [ ] Passwd not req. |
[ ] Temp. duplicate | [X] Normal account  | [ ] NMS account     |
[ ] Domain trust ac | [ ] Wks trust act.  | [ ] Srv trust act   |
[X] Pwd don't expir | [ ] Auto lockout    | [ ] (unknown 0x08)  |
[ ] (unknown 0x10)  | [ ] (unknown 0x20)  | [ ] (unknown 0x40)  |

Failed login count: 0, while max tries is: 0
Total  login count: 3

* = blank the password (This may work better than setting a new password!)
Enter nothing to leave it unchanged
Please enter new password: *

Some information is displayed. Also, if the account is locked, you will be asked if you wish to unlock it (not shown here)

We go for the blank password option (*) WHICH IS HIGLY RECOMMENDED over setting a new one.

Please enter new password: *
Blanking password!

Do you really wish to change it? (y/n) [n] y
Changed!

Select: ! - quit, . - list users, 0x - User with RID (hex)
or simply enter the username to change: [Administrator] !

! brings us back to the main menu here.

<>========<> chntpw Main Interactive Menu <>========<>

Loaded hives:  

  1 - Edit user data and passwords
  2 - Syskey status & change
  3 - RecoveryConsole settings
      - - -
  9 - Registry editor, now with full write support!
  q - Quit (you will be asked if there is something to save)

What to do? [1] -> q

5. WRITING OUT THE CHANGES
Everything has been done, time to commit the changes.

Hives that have changed:
 #  Name
 0   - OK

=========================================================
. Step FOUR: Writing back changes
=========================================================
About to write file(s) back! Do it? [n] : y

THIS IS YOUR LAST CHANCE! If you answer y here there will be a write to disk!

Writing  sam

NOTE: A disk fixup will now be done.. it may take some time

Mounting volume... OK

Processing of $MFT and $MFTMirr completed successfully.

NTFS volume version is 3.1.

Setting required flags on partition... OK

Going to empty the journal ($LogFile)... OK

NTFS partition /dev/ide/host0/bus0/target0/lun0/part1 was processed successfully.
NOTE: Windows will run a diskcheck (chkdsk) on next boot.
NOTE: this is to ensure disk intergity after the changes

***** EDIT COMPLETE *****

You can try again if it somehow failed, or you selected wrong
New run? [n] : n

That was all. The disk fixup is only run on NTFS filesystems, and will force chkdsk next time windows boots.

Please answer n here and then reboot, CTRL-ALT-DEL. Remember to remove the floppy or CD.

What can go wrong?
Lots of things can go wrong, but most faults won't damage your system.
The most critical moment is when writing back the registry files to NTFS. Also, the file written back may be corrupt (from chntpw messing it up), preventing your NT system from booting properly. YOU HAVE BEEN WARNED! One indication of a corrupt SAM is that the Netlogon service will fail to start, which again means it's impossible to log in. Or it will simply just reboot forever.

Downloads ( SEE the file download links on this page for these files.
bd040116.zip (~1.1MB) - Bootdisk image, date 040116
sc040116.zip (~1MB) - SCSI-drivers (040116) (only use newest drivers with newest bootdisk, this one works with bd040116)
cd040116.zip (~2MB) - Bootable CD image with same version and drivers as floppies above.

NOTE THAT THE BOOTDISK CONTAINS CRYPTHOGRAPHIC CODE, and that it may be ILLEGAL to RE-EXPORT it from your country.

How to use the floppy
The unzipped image (bdxxxxxx.bin) is a block-to-block representation of the actual floppy, and the file cannot simply be copied to the floppy. Special tools must be used to write it block by block.

Unzip the bd zip file to a folder of your choice.
There should be 3 files: bdxxxxxx.bin (the floppy image) and rawrite2.exe (the image writing program), and install.bat which uses rawrite2 to write the .bin file to floppy.
Insert a floppy in drive A: NOTE: It will lose all previous data!
Run (doubleclick) install.bat and follow the on-screen instructions.
Thanks to Christopher Geoghegan for the install.bat file (some of it ripped from memtest86 however)
Or from unix:

dd if=bd??????.bin of=/dev/fd0 bs=18k

How to use the CD
Unzipped, there should be an ISO image file (cd??????.iso). This can be burned to CD using whatever burner program you like, most support writing ISO-images. Often double-clikcing on it in explorer will pop up the program offering to write the image to CD. Once written the CD should only contain some files like "initrd.gz", "vmlinuz" and some others. If it contains the image file "cd??????.iso" you didn't burn the image but instead added the file to a CD. I cannot help with this, please consult you CD-software manual or friends.

The CD will boot with most BIOSes, see your manual on how to set it to boot from CD. Some will auto-boot when a CD is in the drive, some others will show a boot-menu when you press ESC or F10/F12 when it probes the disks, some may need to have the boot order adjusted in setup.

Soon everyone from major newspapers to individuals who just want to rant over the world wide web will be offering RSS (Rich Site Summary) feeds on the internet, free for the taking. With a simple ASP script and an xml style sheet, you can consolidate as many RSS feed as you want onto a single web page. That way, you can show the latest rantings of a friend or news headlines about your favorite subject, all in one place. This is called news consolidation (not related to the usenet news:// protocol).

RSS is an xml format for encoding information about news headlines. It is quickly becoming the standard method for sending headlines, and related things, across the world wide web. This popularity is primarily due to it's simplicity and the extraordinary growth in the popularity of web logs (daily personal rants published to the web).

RSS defines a number of xml tags suitable for storing news headlines. Here's some of the most important RSS xml tags;

<rss>
    <channel>
        <title>Name of the news feed.</title>
        <link>A url for the source website.</link>
        <description>A short description of the news feed.</description>
        <item>
            <title>Headline #1</title>
            <link>A url for the entire news article under headline #1.</link>
            <description>A short blurb about the news article under headline #1.</description>
        </item>
    </channel>
</rss>

The <item> tag repeats for each news headline in the RSS feed.

ASP Script

Below are a ASP classic and a ASP.net script that load the remote RSS feed and displays it on the page. You can execute this script from an ASP database page containing the url of the RSS xml source or hard code the RSS feeds that you want to include on the page.

ASP Classic

The following ASP function loads the specified an RSS formatted xml file, loads a standard xsl style sheet and returns an HTML table. Place this script at the top of your ASP page;

<%
Function getXML(sourceFile) 
dim styleFile 
dim source, style 
styleFile = Server.MapPath("news.xsl")

Dim xmlhttp
Set xmlhttp = Server.CreateObject("Microsoft.XMLHTTP")
xmlhttp.Open "GET", sourceFile, false
xmlhttp.Send

set source = Server.CreateObject("Microsoft.XMLDOM")
source.async = false 
source.loadxml(xmlhttp.ResponseText) 

set style = Server.CreateObject("Microsoft.XMLDOM")
style.async = false 
style.load(styleFile) 

getXML = source.transformNode(style) 
set source = nothing 
set style = nothing 
End Function 
%>
<html>

The following ASP script displays the specified RSS xml feed as a table on your ASP page. Place it on the page where you want the table to be displayed and change the URL in the getXML function call to point to your RSS xml source file. 

<%= getXML("http://radio.weblogs.com/0106935/rss.xml") %>

ASP.net

The following ASP.net function loads the specified RSS formatted xml file into an xml document when the page loads. Place this script at the top of your ASP page and add the URL to the RSS xml source file in the getXML function call;

<script language="VB" runat="server">
Sub Page_Load (sender As Object, e As EventArgs)
myXml.Document = getXML("http://radio.weblogs.com/0106935/rss.xml")
End Sub

Function getXML(sourceFile As String) 
Dim myRequest As System.Net.WebRequest = System.Net.WebRequest.Create(sourceFile)
Dim myResponse As System.Net.WebResponse = myRequest.GetResponse()
Dim myReader As System.Xml.XmlTextReader = new System.Xml.XmlTextReader(myResponse.GetResponseStream())
Dim doc As System.Xml.XmlDocument = New System.Xml.XmlDocument()
doc.Load(myReader)
getXML = doc
End Function

</script>

The following xml web server control displays the specified RSS xml feed as a table on your ASP page using the xsl style sheet in the TransformSource attribute (NOTE: the xsl source file must be in the server path of the ASP file, not a http: url). Place it on the page where you want the table to be displayed.

<asp:Xml id="myXml" TransformSource="news.xsl" runat="server" />

XSL Style Sheet

An RSS source is rendered as a HTML table on the ASP page using an xsl style sheet. Save this xsl as a text file called news.xsl in the same folder as your ASP page;

<?xml version="1.0" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" omit-xml-declaration="yes" indent="yes"/>
<xsl:template match="*">
<table border="1" width="600" align="center">
<tr><td valign="top" align="center" class="title" bgcolor="silver" >
<a>
<xsl:attribute name="href">
<xsl:value-of select="*[local-name()='channel']/*[local-name()='link']"/>
</xsl:attribute>
<xsl:attribute name="target">
<xsl:text>top</xsl:text>
</xsl:attribute>
<xsl:value-of select="*[local-name()='channel']/*[local-name()='title']"/>
</a>
<xsl:text disable-output-escaping="yes">&nbsp;</xsl:text>
<xsl:value-of select="*[local-name()='channel']/*[local-name()='lastBuildDate']"/>
</td></tr><tr><td valign="top" bgcolor="ghostwhite" class="headlines" >
<ul>
<xsl:for-each select="//*[local-name()='item']">
<li>
<a>
<xsl:attribute name="href">
<xsl:value-of select="*[local-name()='link']"/>
</xsl:attribute>
<xsl:attribute name="target">
<xsl:text>top</xsl:text>
</xsl:attribute>
<xsl:value-of select="*[local-name()='title']"/>
</a>
<xsl:value-of select="*[local-name()='description']" disable-output-escaping="yes"/>
</li>
</xsl:for-each>
</ul>
</td></tr>
</table>
</xsl:template>
<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>
</xsl:stylesheet>

Google .xml Site map

The Sitemap Protocol allows you to inform search engines about URLs on your websites that are available for crawling. In its simplest form, a Sitemap that uses the Sitemap Protocol is an XML file that lists URLs for a site. The protocol was written to be highly scalable so it can accommodate sites of any size. It also enables webmasters to include additional information about each URL (when it was last updated; how often it changes; how important it is in relation to other URLs in the site) so that search engines can more intelligently crawl the site.

Sitemaps are particularly beneficial when users can't reach all areas of a website through a browseable interface. (Generally, this is when users are unable to reach certain pages or regions of a site by following links). For example, any site where certain pages are only accessible via a search form would benefit from creating a Sitemap and submitting it to search engines.

This document describes the formats for Sitemap files and also explains where you should post your Sitemap files so that search engines can retrieve them.

Please note that the Sitemap Protocol supplements, but does not replace, the crawl-based mechanisms that search engines already use to discover URLs. By submitting a Sitemap (or Sitemaps) to a search engine, you will help that engine's crawlers to do a better job of crawling your site.

Using this protocol does not guarantee that your webpages will be included in search indexes. (Note that using this protocol will not influence the way your pages are ranked by Google.)

Create a text file using this template adding each web page as below.
rename the file sitemap.xml
upload to your site and notify Google of its address:
https://www.google.com/webmasters/tools/siteoverview

Example site map:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.google.com/schemas/sitemap/0.84">

   <url>
      <loc>http://www.example.com/</loc>
      <lastmod>2005-01-01</lastmod>
      <changefreq>monthly</changefreq>
      <priority>0.8</priority>
   </url>
   <url>
      <loc>http://www.example.com/catalog?item=12&desc=vacation_hawaii</loc>
      <changefreq>weekly</changefreq>
   </url>
   <url>
      <loc>http://www.example.com/catalog?item=73&desc=vacation_new_zealand</loc>
      <lastmod>2004-12-23</lastmod>
      <changefreq>weekly</changefreq>
   </url>
   <url>
      <loc>http://www.example.com/catalog?item=74&desc=vacation_newfoundland</loc>       <lastmod>2004-12-23T18:00:15+00:00</lastmod>
      <priority>0.3</priority>
   </url>
   <url>
      <loc>http://www.example.com/catalog?item=83&desc=vacation_usa</loc>
      <lastmod>2004-11-23</lastmod>
   </url>
</urlset

The Microsoft Group Policy Management Console (GPMC) with Service Pack 1 (SP1) unifies management of Group Policy across the enterprise. The GPMC consists of a MMC snap-in and a set of programmable interfaces for managing Group Policy.

GPMC simplifies the management of Group Policy by making it easier to understand, deploy, manage, and troubleshoot Group Policy implementations. GPMC also enables automation of Group Policy operations via scripting.

GPMC can be used to manage Windows Server 2003 as well as Windows 2000-based Group Policy implementations. Customers who have at least one valid license of Windows Server 2003 or Windows 2000 Server can obtain and use an unlimited number of copies of GPMC. Please see the End User License Agreement (EULA) provided with the GPMC software for details on licensing terms.

Key features delivered via GPMC include:

• A unified graphical user interface (GUI) that makes Group Policy much easier to use.
• Backup/restore of Group Policy objects (GPOs).
  
• Import/export and copy/paste of GPOs and Windows Management Instrumentation (WMI) filters.
• Simplified management of Group Policy–related security.
• HTML reporting for GPO settings and Resultant Set of Policy (RSoP) data.
• Scripting of Group Policy related tasks that are exposed within this tool (not scripting of settings within a GPO).

Prior to GPMC, administrators were required to use several Microsoft tools to manage Group Policy. GPMC integrates the existing Group Policy functionality exposed in these tools into a single, unified console, along with the new capabilities listed above.

1. Click the Download link BELOW to start the download
   Do one of the following:
2. • To start the installation immediately, click Open or Run this program from its current location.
   • To copy the download to your computer for installation at a later time, click Save or Save this program to disk.
3. To install the GPMC, run the gpmc.msi package. After you accept the End User License Agreement (EULA), all necessary files are installed to the “%Program Files%\GPMC” folder.
4. Prior to starting and using the GPMC, please be sure to read the release notes RelNotes.rtf, which is located in the %Program Files%\GPMC" folder.
5. After installation of the GPMC, you can open the snap-in using either of the following methods:
   • You can open the pre-configured GPMC.msc file. To do this, click Start, click Run, type GPMC.msc and then choose OK. Alternatively, click the Group Policy Management shortcut in the Administrative Tools folder from the Control Panel.
     
   • You can create a custom MMC console that contains the GPMC snap-in. To do this:
     • Open MMC, by clicking Start, clicking Run, typing MMC, and then clicking OK.
     • From the File menu, choose Add/Remove Snap-in, and then click Add.
     • In the Add Standalone Snap-in dialog box, select Group Policy Management and click Add.
     • Click Close, and then OK.
6. GPMC includes several sample scripts. These are installed in the %ProgramFiles%\GPMC\Scripts folder. You should use cscript.exe to execute all of the sample scripts. For more details on scripts, see the ScriptingReadMe.rtf file in the scripts folder. For instructions and usage information for each script, run each script with the “/?” parameter.

In Outlook , click Accounts on the Tools menu.
Click the Mail tab, click the Hotmail account, and then click Properties.

Click the Server tab, and then change the HTTP Server URL to the following Web address:
http://oe.hotmail.com/secure/hmdata
Click Apply, and then click OK.

MORE INFORMATION
The original setting for the HTTP Server URL is:

http://services.msn.com/svcs/hotmail/httpmail.asp

Configuring the Switch for Telnet

The following procedure describes one way to configure a password for Telnet.

Enabling Broadcast-Storm Control on a Port

Broadcast-storm control blocks the forwarding of packets created by broadcast storms, the bursts of broadcast traffic that ports can sometimes generate. When you enable broadcast-storm control on a port, two parameters define the beginning and end of a broadcast storm. The threshold rising parameter determines when the forwarding of broadcast packets from the port is blocked. The threshold falling parameter determines when normal forwarding resumes. You can set the port to generate a trap when these thresholds are crossed (port storm-control trap), and you can disable the port during a broadcast storm (port storm-control filter).

Switch ports are referred to with the constant fastethernet and a module and port number. Fixed ports are module 0, and 1 and 2 refer to the Catalyst 2916M expansion slot ports. The following examples are valid ports:
fastethernet0/8
fa2/2
fa2/1

Task	Prompt	Command
Step 1 Enter privileged EXEC mode.	switch>	enable
Step 1 Enter global configuration mode.	switch#	configure terminal
Step 2 Enter interface configuration mode and define the interface to configure.	switch(config)#	interface interface
Step 3 Enter the port storm-control command and the two threshold parameters.	switch(config-if)#	port storm-control threshold [rising number falling number]
Step 4 Return to EXEC mode to verify the entry.	switch(config-if)#	end
Step 5 Verify that the parameters were entered correctly by using the show command.	switch#	show port storm-control interface

Working with Files in Flash Memory

You can use the file system in Flash memory to copy files and to troubleshoot configuration problems. Use the dir flash: command to display the contents of Flash memory:

Switch# dir flash:
Directory of flash:
 
  2  -rwx      843947   Mar 01 1993 00:02:18  C2900XL-h-mz-112.8-SA
  4  drwx        3776   Mar 01 1993 01:23:24  html
 66  -rwx         130   Jan 01 1970 00:01:19  env_vars
 68  -rwx        1296   Mar 01 1993 06:55:51  config.text
 
1728000 bytes total (456704 bytes free)

The file system uses a URL-based file specification. The following example uses the TFTP protocol to copy the file conffile.txt from the host arno to Catalyst 2900 Flash memory with the name bootfile:

switch# copy tftp://arno/2900/conffile.txt flash:bootfile

You can enter the following parameters as part of a filename:

• TFTP
  
  
• Flash
  
  
• RCP
  
• XMODEM
  

Enter the write memory command to save your configuration changes to nonvolatile random-access memory (NVRAM) so that they are not lost if there is a system reload or power outage. This example shows how to use this command to save your changes:

switch# write mem
Building configuration...
 

It might take a minute or two to save the configuration to Flash NVRAM. After the configuration has been saved, the following appears:

[OK]
switch#

Upgrading Switch Software by Using Telnet

After you have downloaded the new image files to your PC or workstation, you can use Telnet and the switch command-line interface ( CLI) to perform a TFTP transfer of the files to the switch. You can also connect a PC or workstation to the console port and transfer the files via XMODEM.

Because the switch Flash memory can hold only one software image file, you need to change the name of the current image file to the name of the new file you are copying. You then replace the old file with the new file when you copy it into Flash memory.

Follow these steps to upgrade the switch software by using a TFTP transfer:

Step 1 If your PC or workstation cannot act as a TFTP server, copy the files to a TFTP server to which you have access.

Step 2 Start a Telnet session on your PC or workstation, and display the switch CLI by entering the following command:

server% telnet switch_ip_address

Step 3 Enter EXEC mode:

switch> enable
switch#

Step 4 Display the name of the current (default) image file. The following example shows the current name in italics:

switch# show boot
BOOT path-list: flash:current_image
Config file: flash:config.text
Enable Break: 1
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768

Step 5 Rename the current image file to the name of the new image. This does not affect the operation of the switch.

switch# rename flash:current_image flash:new_image
Source filename [current_image]?
Destination filename [new_image]?

Step 6 Display the contents of Flash memory to verify the renaming of the file:

switch# dir flash:
Directory of flash:
-rwx 910426 Mar 06 1993 23:47:28 new_image
-rwx 4800 Mar 01 1993 00:04:14 html
-rwx 159 Jan 01 1970 00:00:34 env_vars
-rwx 1121 Mar 01 1993 18:46:01 config.text

Step 7 Enter terminal configuration mode:

switch# conf terminal
Enter configuration commands, one per line. End with CNTL/Z.

Step 8 Change the name of the default image file:

switch(config)# boot system flash:new_image

Step 9 Verify that the name of the default image file is correct:

switch# show boot
BOOT path-list: flash:new_image
Config file: flash:config.text
Enable Break: 1
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768

Step 10 Use the name of the new image file when you copy it from the TFTP server to the Flash memory:

switch# copy tftp://server_ip_address//path/new_image.bin flash:new_image
Source IP address or hostname [server_ip_address]?
Source filename [path/filename.bin]?
Destination filename [flash:new_image]?
Loading /path/filename.bin from server_ip_address (via!)
[OK - 843975 bytes]

Step 11 Enter the following command to copy the HTML file from the TFTP server to the switch Flash memory:

switch# tar /x tftp://server_ip_address//path/filename.tar flash:html

Loading /path/filename.tar from server_ip_address (via!)
extracting advanced.gif (2648 bytes)
extracting amber.gif (530 bytes)!
extracting bar.gif (4156 bytes)!
extracting cool.gif (530 bytes)
extracting daytona.gif (1470 bytes)
extracting duplgnd.gif (639 bytes)!
. . .

Step 12 The new image file loads the next time you reset the switch. You can load the new software with the following command:

switch# reload
System configuration has been modified. Save? [yes/no]:y
Proceed with reload? [confirm]

Step 13 Press Return to confirm the reload. Your Telnet session ends when the switch resets.

Understanding the CLI

This section describes the Cisco IOS command-mode structure. Each command mode supports specific Cisco IOS commands. For example, the interface type_number command is used only from global configuration mode.

The Catalyst 2900 series switches support the following command modes:

• User EXEC
  
  
• Privileged EXEC
  
  
• Global configuration
  
  
• Interface configuration
  
  
• Line configuration
  
  

Table 5-1 describes how to access each mode, the prompt you see in that mode, and how to exit the mode. The examples in the table use the host name switch.

Getting Help

You can use the question mark (?) and arrow keys to help you enter commands.

For a list of available commands in a command mode, enter a question mark:

switch> ?
 

To complete a command, enter a few known characters followed by a tab (with no space):

switch# sh conf<tab>
switch#sh configuration
 

For a list of command variables, enter the command followed by a space and a question mark:

switch> show ?
 

To redisplay a command you previously entered, press the up-arrow key. You can continue to press the up-arrow key for more commands.

Table 5-1: Command Modes Summary

Modes	Access Method	Prompt	Exit Method	About This Mode1
User EXEC	Begin a session with your switch.	switch>	Enter the logout command or quit.	Use this mode to: Change terminal settings Perform basic tests Display system information
Privileged EXEC	Enter the enable command while in user EXEC mode.	switch#	Enter the disable command to exit.	Use this mode to verify commands you have entered. Access to this mode should be protected with a password.
Global configuration	Enter the configure command while in privileged EXEC mode.	switch(config)#	To exit to privileged EXEC mode, enter the exit or end command, or press Ctrl-Z.	Use this mode to configure parameters that apply to your switch as a whole.
Interface configuration	Enter the interface command (with a specific interface) while in the global configuration mode.	switch(config-if)#	To exit to global configuration mode, enter the exit command.	Use this mode to configure parameters for the Ethernet interfaces.
Line configuration	Specify a line with the line vty or line console command while in the global configuration mode.	switch(config-line)#	To exit to global configuration mode, enter the exit command.	Use this mode to configure parameters for the terminal line.

1For any of the modes, you can see a comprehensive list of the available commands by entering a question mark (?) at the prompt.

Setting Passwords

Because many privileged EXEC commands are used to set operating parameters, you should password-protect these commands to prevent unauthorized use.

You use two commands to do this:

• enable secret password password (a very secure, encrypted password)
  
  
• enable password password (a less secure, unencrypted password)
  
  

You must enter an enable password to gain access to privileged EXEC mode.

For maximum security, the passwords should be different. If you enter the same password for both during the setup process, your switch prompts you to make them different.

An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters. An enable password can contain any number of uppercase and lowercase alphanumeric characters. In both cases, a number cannot be the first character. Spaces are also valid password characters; for example, two words is a valid password. Leading spaces are ignored; trailing spaces are recognized.

If you lose or forget your enable password, refer to the "Troubleshooting" chapter for a recovery procedure.

Abbreviating Commands

You only have to enter enough characters for the switch to recognize the command as unique. This example shows how to enter the show configuration command:

switch# show conf

No Commands

The word no can be used to create a no form of a command. The no form of a command can be used:

• To reset a command to its default values.
  
  
• To reverse the action of a command. For example, the command no shutdown reverses the shutdown of an interface.
  
  

Command-Line Error Messages

Table 5-2 lists some error messages that you might encounter while using the CLI to configure your switch.

Table 5-2: Common CLI Error Messages

Error Message	Meaning	How to Get Help
% Ambiguous command: "show con"	You did not enter enough characters for your switch to recognize the command.	Reenter the command followed by a question mark (?) with no space between the command and the question mark. The possible keywords that you can enter with the command are displayed.
% Incomplete command.	You did not enter all of the keywords or values required by this command.	Reenter the command followed by a question mark (?) with no space between the command and the question mark.
% Invalid input detected at `^' marker.	You entered the command incorrectly. The caret (^) marks the point of the error.	Enter a question mark (?) to display all of the commands that are available in this command mode.

How to Install the DMRC Service Manually...

1. Open your local DameWare Mini Remote Control installation folder.
   Default folders:
   \Program Files\DameWare Development\DameWare NT Utilities
   or
   \Program Files\DameWare Development\DameWare Mini Remote Control
    
2. Locate and copy the DWRCS.exe, DWRCK.dll, DWRCSET.dll and DWRCShell.dlx files to the remote machine.  
   For Windows NT/2000/Xp, place all files in the System32 folder.
   For Windows 95/98/Me place all files in the \Windows\System folder.
    
3. At a command prompt on the remote machine execute the following command:
   
   DWRCS -install
   
   This will install the Mini Remote Client Agent as a service. You can also run the Client Agent as an application by simply executing the DWRCS.exe but when the computer reboots or if the user exits the application, the server will not be available.

Product(s): ACT! 5.0 - PC; ACT! 6.0 - PC; ACT! 2000 - PC; ACT! 3.0 - PC; ACT! 4.0 - PC
Operating System(s):Windows 2000; Windows 95; Windows 98; Windows ME; Windows NT; Windows XP Home; Windows XP Pro

Note: If you have any ACT! add-ons installed, we recommend you uninstall those prior to uninstalling ACT!. Add-ons include the following items:
ACT! Link 2.0 for Palm OS/ACT! PalmPilot Link
ACT! Link for QuickBooks
ACT! for Palm OS
ACT! Link for Pocket PC
ACT! Link for Peachtree

Caution: We strongly recommend that you back up the system registry before making any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Please make sure you modify only the keys specified. See the correct section below for your operating system:

Windows XP/2000/ME/98/95
Windows XP/2000/ME/98/95

Perform the following steps to back up the entire registry:
Click the Windows Start button, then click Run. The Run dialog appears.
Type regedit into the Open window, then click OK. The Registry Editor opens.
Click the Registry menu, then click Export Registry File. (Windows XP users; click the File menu, then click Export) The Export Registry File dialog appears.

Establish the following settings in the Export Registry File dialog:
Save In: Desktop
File Name: Registry Backup
Save as Type: Registration Files (*.reg)
Export Range: All
Click Save.
Exit the Registry Editor.
Verify that an icon labeled with the exact File name you entered is located on your Desktop.
Caution: Do not double-click the registry backup.reg file on the desktop unless you intend to undo changes you've made after the backup was created and restore your current registry settings. .

After Changing the Registry
After making changes to the registry, immediately verify that the results are what you expected. If the results were not what you expected and you want to restore the registry to its previous state, double-click the registry backup.reg file. If the results are accurate and no other issues are apparent, delete (or move) the registry backup.reg file. If you allow this file to remain on the desktop beyond the test period, you may accidentally restore the original registry settings.

Windows NT
Windows NT
Windows NT provides a variety of ways to back up the Windows NT registry. For more information about Windows NT backup methods, see articles Q126464 and Q122857 in the Microsoft Knowledge Base at http://support.microsoft.com/support

This simple method backs up the Windows NT registry files onto a floppy diskette:
Click Start, then click Run. The Run dialog box appears.
Enter RDISK /S, then click OK. The Saving Configuration window opens.
When the process is finished, the Setup window opens. Click Yes to create an Emergency Repair Disk (ERD).
Follow the on-screen prompts. When you are done, label the disk "Emergency Repair Disk" and include the current date.
Locate the three Setup disks that came with your copy of Windows NT. Store them with the Emergency Repair Disk. When used with the Setup disks, the ERD can restore the backup even when Windows NT is not bootable.

Note: If you do not have the three Windows NT Setup Disks, you can make your own. For more information, see article Q131735 in the Microsoft Knowledge Base.

This process also makes a second backup of the current registry files in the \Windows\Repair folder on the hard drive. These files are compressed. This backup might not be accessible later if you cannot boot into Windows NT.

After Changing the Registry
After making changes to the registry, immediately verify that the results are what you expected. If the results are not what you expected and you want to restore the registry to its previous state, boot with the first diskette of the three Windows NT Setup diskettes. When the computer has booted, click Repair, and choose Registry. You will have a choice for which parts of the registry to restore.

Remove ACT! from the Registry
To remove the ACT! keys from the registry, please follow these steps:
Click the Windows Start button, and then click Run. The Run dialog appears.
Type regedit into the Open window, then click OK. The Registry Editor launches.
For each of the keys in the list that follows:
Browse to and select the key.
Press the Delete key on your keyboard, and then click Yes to confirm.
When all keys are deleted, exit the Registry Editor.
Delete the following ACT! keys:

Note: There are different Registry Keys for each ACT! Version, be sure you are selecting the appropriate set of registry keys to delete.
ACT! 6.0
HKEY_CLASSES_ROOT\ACT!.Application
HKEY_CLASSES_ROOT\ACT!.Database
HKEY_CLASSES_ROOT\ACT!.Document
HKEY_CLASSES_ROOT\ACT!.Envelope.Template
HKEY_CLASSES_ROOT\ACT!.Label.Template
HKEY_CLASSES_ROOT\ACT!.Report
HKEY_CLASSES_ROOT\ACT!.Report.Template
HKEY_CLASSES_ROOT\ACT!.WP.Template
HKEY_CLASSES_ROOT\Act.Word6Drv.1
HKEY_CLASSES_ROOT\ACT2000AgentEx.CoACT2000AgentEx.
HKEY_CLASSES_ROOT\ACT30.APPOBJECT
HKEY_CLASSES_ROOT\ActAbout.AboutDlg
HKEY_CLASSES_ROOT\ActAbout.AboutDlg.1
HKEY_CLASSES_ROOT\ActEmail.aActEmailConn
HKEY_CLASSES_ROOT\ActEmail.aActEmailConn.1
HKEY_CLASSES_ROOT\ACTEVENT.ActEventCtrl.1
HKEY_CLASSES_ROOT\ActiveActX.ActiveAct
HKEY_CLASSES_ROOT\Actksn.ksn
HKEY_CLASSES_ROOT\Actksn.ksn.1
HKEY_CLASSES_ROOT\actMHTML.MIMEHTML
HKEY_CLASSES_ROOT\ActMsg.Session
HKEY_CLASSES_ROOT\ACTOLE.APPOBJECT
HKEY_CLASSES_ROOT\ACTOLE.AUXCMDS
HKEY_CLASSES_ROOT\ACTOLE.DATABASE
HKEY_CLASSES_ROOT\ActPicker.coActPicker
HKEY_CLASSES_ROOT\ACTSRC.ACTEVENTSOURCE
HKEY_CLASSES_ROOT\ActWP.Document
HKEY_CLASSES_ROOT\ActWrite
HKEY_CLASSES_ROOT\SideACT!.Document

HKEY_CURRENT_USER\Software\Act Email
HKEY_CURRENT_USER\Software\Symantec\ACT!
HKEY_CURRENT_USER\Software\Symantec\ACT! Alarms
HKEY_CURRENT_USER\Software\Symantec\ACT! Word Processor

HKEY_LOCAL_MACHINE\SOFTWARE\Clients\ACT!
HKEY_LOCAL_MACHINE\SOFTWARE\Interact
HKEY_LOCAL_MACHINE\SOFTWARE\Interact Commerce
HKEY_LOCAL_MACHINE\SOFTWARE\Interact Commerce\ACT!
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\act.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\actdiag.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ACT!
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\ACT!

HKEY_USERS\.DEFAULT\Software\Symantec\ACT!
HKEY_USERS\.DEFAULT\Software\Symantec\ACT! Word Processor

ACT! 5.0 (2000), ACT! 4.x, ACT! 3.x,
HKEY_CLASSES_ROOT\ACT!.Application
HKEY_CLASSES_ROOT\ACT!.Database
HKEY_CLASSES_ROOT\ACT!.Document
HKEY_CLASSES_ROOT\ACT!.Email
HKEY_CLASSES_ROOT\ACT!.Envelope.Template
HKEY_CLASSES_ROOT\ACT!.Label.Template
HKEY_CLASSES_ROOT\ACT!.Report
HKEY_CLASSES_ROOT\ACT!.Report.Template
HKEY_CLASSES_ROOT\ACT!.WP.Template
HKEY_CLASSES_ROOT\Act.Word6Drv.1
HKEY_CLASSES_ROOT\ACT2000AgentEx.CoACT2000AgentEx.
HKEY_CLASSES_ROOT\ACT30.APPOBJECT
HKEY_CLASSES_ROOT\ACTEVENT.ActEventCtrl.1
HKEY_CLASSES_ROOT\ActWrite
HKEY_CLASSES_ROOT\SideACT!.Document

HKEY_CURRENT_USER\Software\Symantec\ACT!
HKEY_CURRENT_USER\Software\Symantec\ACT! Word Processor

HKEY_LOCAL_MACHINE\Software\Symantec\ACT
HKEY_LOCAL_MACHINE\Software\Symantec\ACT! 4.0 for Windows
HKEY_LOCAL_MACHINE\Software\Symantec\ACT!andWinFax
HKEY_LOCAL_MACHINE\Software\Symantec\EMS32\ACT!
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ACT! 2000
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ACT!

HKEY_USERS\.DEFAULT\Software\Symantec\ACT!
HKEY_USERS\.DEFAULT\Software\Symantec\ACT! Word Processor

Remove Leftover Files
How you do this depends upon whether you intend to reinstall ACT!, and whether you have files or data you want to save.

If you do not intend to reinstall ACT!, and do not want to save any databases, files, templates, and so on, follow the instructions under the heading Removing All ACT! Files from the Computer. All files will be deleted, and all data will be lost.
If you intend to reinstall, or you have databases or files that you want to save, follow the steps in the section titled Just removing ACT! Program Files.

Removing All ACT! Files from the Computer

Note: By following this process, ALL files concerning ACT! will be deleted and all data will be lost.

ACT! 6.0/5.0(2000)
Remove these folders
ACT! 6.0/5.0 - C:\Program Files\ACT! and My Documents\ACT.
ACT! 2000/4.0 - C:\Program Files\Symantec\ACT and My Documents\ACT.
Restart the computer

ACT! 4.x/3.x
Remove the following folder:

C:\ACT

Restart the computer

Just Removing ACT! Program Files
Open the \ACT folder. The default location for this is
ACT! 6.0/5.0 - C:\Program Files\ACT
ACT!2000\4.0 - C:\Program Files\Symantec\ACT
In the right pane, select any files that are displayed. If you previously ran the uninstall program, there may be only a few files, or there may be many.
Make sure that only files, not folders, in the \ACT parent folder are selected. Do not select (or remove) any of the yellow subfolders or their contents.
Press the Delete key on you keyboard.
Restart the computer.

Windows 2000 supports both Network Address Translation (NAT) and Internet Confection Shading (ICS) al1ow workgroup users to access to the Internet.. Windows 2000/XP Professional support only ICS. Internet Connection Sharing (ICS) enables a Windows (Win98SE, Win2K and XP) computer to share its Internet connection with computers on local area networks. The computer connecting directly to the Internet and shares its connection with the rest of the computers on the network called the ICS host. In addition, the ICS host provides DHCP to ICS clients. Client computers are protected because they cannot be seen from outside the network. Only the computer running ICS is seen from the public side.

We assume you have all computers physically connected, and the ICS host have two network connections: one (for example Internet in our case) for the Internet such as a dial-up (PPP or ISDN), cable modem, DSL, or other broadband Ethernet connection, and another one (LAN) , for the local area network.

Things you should know about ICS

1. When you enable Internet Connection Sharing, IP address of the Interne NIC in the ICS server is always 192.168.0.1. All clients will be assigned other IP addresses in the 192.168.0.x range.
2. You should not enable ICS on the computer as a domain controller, DHCP server, or DNS server.
3. To enable ICS, you must be logged on as a member of the Administrators
4. You may experience some problems if you use NetMeeting and VPN in your ICS network.

Enabling Host ICS - WinXP

To configure a WinXP ICS host, go to Start>Control Panel>Network Connation. Highline the Internet which connecting to a cable modem in our case. Under Network Tasks, click Change settings of this connection. On the Advanced tab, select the Allow other network users to connect through this computer's Internet connection check box.

Configuring ICS Client

To setup a win9x (in our case) as ICS client to access the internet, you need to do two things. network settings and internet option settings.

Netsh.exe is a tool an administrator can use to configure and monitor Windows-based computers at a command prompt. With the Netsh.exe tool, you can direct the context commands you enter to the appropriate helper, and the helper then carries out the command. A helper is a Dynamic Link Library (.dll) file that extends the functionality of the Netsh.exe tool by providing configuration, monitoring, and support for one or more services, utilities, or protocols. The helper may also be used to extend other helpers.

You can use the Netsh.exe tool to perform the following tasks:

Configure interfaces.
Configure routing protocols.
Configure filters.
Configure routes.
Configure remote access behavior for Windows-based remote access routers that are running the Routing and Remote Access Server (RRAS) Service.
Display the configuration of a currently running router on any computer.
Use the scripting feature to run a collection of commands in batch mode against a specified router.
The syntax for the Netsh.exe tool is:

netsh [-r router name] [-a AliasFile] [-c Context] [Command | -f ScriptFile]

To display a list of subcontexts and commands that can be used in a context, type the context name followed by a space and a ? at the netsh> command prompt. For example, to display a list of subcontext and commands that can be used in the /routing context, type routing ? at the netsh> command prompt, and then press ENTER.

Context strings are appended to the Netsh.exe tool command and are passed to an associated helper. The helper may have one or more entry points that map to contexts. Some of the contexts available in the Netsh.exe tool are:

Context Command: /dhcp
Result: Changes to the Dynamic Host Configuration Protocol (DHCP) context.

Context Command: /ras
Result: Changes to the Remote Access Server (RAS) context.

Context Command: /routing
Result: Changes to the routing context.

Context Command: /wins
Result: Changes to the Windows Internet Name Service (WINS) context.

Contexts may also nest within other contexts. For example, the following contexts operate within the netsh>ras context:

Context Command: /ip
Result: Changes to the Internet Protocol (IP) context.

Context Command: /ipx
Result: Changes to the Internetwork Packet Exchange (IPX) context.

Context Command: /netbeui
Result: Changes to the NetBios Enhanced User Interface (NETBEUI) context.

The following subcontexts operate within the netsh>routing ip context:

Context Command: /autodhcp
Result: Changes to the autodhcp subcontext.

Context Command: /dnsproxy
Result: Changes to the dnsproxy subcontext.

Context Command: /igmp
Result: Changes to the Internet Group Membership Protocol (IGMP) subcontext.

Context Command: /mib
Result: Changes to the Management Information Base (MIB) subcontext.

Context Command: /nat
Result: Changes to the Network Address Translation (NAT) subcontext.

Context Command: /ospf
Result: Changes to the Open Shortest Path First (OSPF) subcontext.

Context Command: /relay
Result: Changes to the relay subcontext.

Context Command: /rip
Result: Changes to the Routing Information Protocol (RIP) subcontext.

Netsh.exe Commands
The following additional commands can be used with the Netsh.exe tool:

NOTE: Optional parameters are shown in brackets ([ ]). Alternative entries are shown with a pipe (|) character between them.

Context Command: /?
Result: Displays help.

Context Command: /abort
Result: Discards any changes made in offline mode. No effect in online mode.

Context Command: /add helper DLL-name
Result: Installs the helper .dll file in netsh.exe.

Context Command: /alias [alias-name] [string1] [string2 ...]
Result: If /alias, lists all aliases. If /alias alias-name, displays the equivalent string. If /alias alias-name string1 string2 ..., sets alias-name to the specified strings.

Context Command: /bye
Result: Exits the program.

Context Command: /commit
Result: Commits any changes made in the offline mode to the router. No effect in the online mode.

Context Command: /delete helper .dll file name
Result: Removes the helper .dll file from Netsh.exe.

Context Command: /dump -file name
Result: Dumps or appends configuration to a text file.

Context Command: /exec script file name
Result: Loads the script file and executes commands from it.

Context Command: /exit
Result: Exits the program.

Context Command: /h
Result: Displays help.

Context Command: /help
Result: Displays help.

Context Command: /offline
Result: Sets the current mode to offline. Any changes made in this mode are saved, but require a "commit" or "online" command to be set in the router.

Context Command: /online
Result: Sets the current mode to online. Any changes in this mode are immediately reflected in the router.

Context Command: /popd
Result: Pops a context from the stack.

Context Command: /pushd
Result: Pushes current context onto the stack.

Context Command: /quit
Result: Exits the program.

Context Command: /set mode [mode =] online | offline
Result: Sets the current mode to online or offline.

Context Command: /show alias | helper | mode
Result: If /show alias, lists all defined aliases. If /show helper, lists all top-level helpers. If /show mode, shows the current mode.

Context Command: /unalias alias name
Result: Deletes the specified alias.

Helper Dynamic Link Libraries Files Available
Routing & Remote Access IP Configuration - Ipmontr.dll
Routing & Remote Access IPX Configuration - Ipxmontr.dll
Interface - Ifmon.dll
RAS - Rasmontr.dll
DHCP - Dhcpmon.dll
WINS - Winsmon.dll

Associated Registry Entries for Helper Dynamic Link Libraries Files
HKEY_LOCAL_MACHINE/Software/Microsoft/NetSh/

REG_SZ: Ipmontr.dll
REG_SZ: Ipxmontr.dll
REG_SZ: Ifmon.dll
REG_SZ: Rasmontr.dll
REG_SZ: Dhcpmon.dll
REG_SZ: Winsmon.dll

NOTE: If attempts to use Netsh dump - to dump configurations to a file does not work,
try using the syntax: netsh dump >filename or path\filename, from a command line.

EXAMPLES....

To change a system from static IP addressing to dynamic DHCP-based addressing:
Open a command prompt and enter the following command:

netsh interface ip set address "<connection name>" dhcp

where connection name is the name of the LAN adapter on which you're making the IP address configuration change. (By default, this adapter is called local area connection, but it might have a different name on machines with multiple LAN adapters or on machines that an administrator has manually renamed.)
To make the reverse change that is, to change a connection or adapter from DHCP-configured addressing to static addressing enter the following command:

netsh interface ip set address "<connectiuon name>" static <IP_address>
<netmask> <gateway> <metric>

Where ip_address is the static IP address you wish to assign to the connection, netmask is the subnet mask (e.g., 255.255.255.0) associated with the IP address, gateway is the default gateway (if any) on the local IP subnet, and metric is an optional numeric value (e.g., 1, 2) that defines the number of hops to the default gateway (if one exists).

For example, to change from DHCP-based addressing to the static IP address 10.1.1.2, mask 255.255.255.0, and gateway 10.1.1.1 (metric 1), you'd enter

netsh interface ip set address "local area connection" static 10.1.1.2 255.255.255.0 10.1.1.1 1

To change the IP address of a remote system on the network ad the required IP address in same command and then the same command can be made to run at the remote system by adding it to the scheduler of the remote system.

Start run - rundll32 setupwbv.dll,IE6Maintenance

To perform a download-only installation from the Internet:

1.        On the following Internet Explorer download page, click the appropriate language version to download the Ie5setup.exe or Ie6setup.exe file:

http://www.microsoft.com/windows/ie/

2.        Click Save to Disk (or Save), and then save the file in a folder on your computer.

3.        Click Start, and then click Run.

4.        Click Browse, browse to the folder in which you saved the Ie5setup.exe file or Ie6setup.exe file, click to highlight the file, and then click Open.

5.        In the Open box, click at the end of the command, add a space, and then type the following command for Internet Explorer 5 or 6.

NOTE: Double quotation marks around the variable #e are required, because #e designates the source path, including executable, of the Ie5setup.exe or Ie6setup.exe as appropriate.

/c:"ieXwzd.exe /d /s:""#E"

For example, if you saved the IE setup file (Ie5setup.exe or Ie6setup.exe) file in the C:\Windows Update Setup Files folder, the command looks like:

"C:\Windows Update Setup Files\ie5setup.exe" /c:"ie5wzd.exe /d /s:""#E"

The following is an explanation of the command line switches used:

·               /d - Downloads Internet Explorer for the current platform only. However, if you would like to download all platforms, you can use the /d:1 switch value to get all platforms. There are only two values for this switch, /d and /d:1.

·               /s:""<#e>"" - Designates the source path of Ie5setup.exe. The ""<#e>"" value refers to the full path and name of the .exe file. Note that two pairs of double quotation marks must surround the path.

6.        Press ENTER. Choose the appropriate items for the operating system.

NOTE: To download Internet Explorer to a network drive, you must map the network drive to a drive letter on your computer. You cannot download Internet Explorer to a Universal Naming Convention (UNC) path.

1. While logged on with administrator privileges, click the Start Settings Control Panel option. Double-click the Modems choice.
2. Follow the Modem Wizard through the modem detection process. When you complete modem installation, you should see a Modem Properties dialog box.
3. While still logged on with administrator privileges, select the Start Settings Control Panel option. Double-click the Network entry to start the Network Control Panel Appli-cation (NCPA).
4. In the Network dialog box, click the Services tab. Then click Add.
5. Under Network Services, select the Remote Access Service option and click OK.
6. NCPA asks for the path to the system files on your Windows NT Server 4.0 CD-ROM. Insert the NT CD-ROM in your CD-ROM drive. Type the path and click Continue.
   Type the drive letter of your CD-ROM and the subdirectory corresponding to your CPU platform.
7. If RAS can’t detect your serial port, modem, or other RAS device, you’ll see the error message shown in Figure 6-1. If you see this message, click OK, then recheck the configuration and connection of your serial ports, modems, ISDN adapters, and so on. Then go back to Step 1. If you don’t see this message, go to Step 8.
8. In the Add RAS Device dialog box, verify that your serial ports, modems, and other RAS devices are listed correctly. Then click OK.
   If you need to install an additional modem, select the Install Modem option and follow the prompts. If you need to install an X.25 device, click the Install X.25 Pad entry and follow the prompts.
9. In the Remote Access Setup dialog box, select the Configure option to establish how RAS will use the device.
10. In the Configure Port Usage dialog box under Port Usage, choose either the Dial out only, Receive calls only, or Dial out and Receive calls options. Then click OK, as shown in Figure 6-2.
    The default entry is Receive calls only. This is the correct setting for a typical RAS server. If you’re going to enable security callback of clients, you should select the Dial out and Receive calls option. Also, if you’re going to act as a RAS client from the RAS server computer, you can enable dial-out capability.
11. In the Remote Access Setup dialog box, select the Network option to configure network protocols used by RAS.
12. In the Network Configuration dialog box, under Server Settings, click to set or clear the check boxes associated with the network protocols that you’re planning to run on RAS clients (see Figure 6-3).
    You can choose any or all of NetBEUI, IPX/SPX, or TCP/IP. Just be sure that you’re already running these protocols on the NT Server computer where you’re installing the RAS server.
    1. If you’ve selected NetBEUI, click the Configure entry next to NetBEUI. If you want to grant NetBEUI clients access to the RAS server only, and not to the entire network, select the This computer only option. Then click OK.
       Otherwise, RAS clients running NetBEUI have access to nodes on the network running the NetBEUI protocol. Unless you have a specific reason for limiting access to just the RAS server, grant these clients access to the entire network.
    2. If you’ve selected TCP/IP, select the Configure entry next to TCP/IP (see Figure 6-4). If you want to grant TCP/IP clients access to the RAS server only, and not to the entire network, click the option for This computer only.
       If you want to control the range of IP addresses assigned to RAS clients, select the Use static address pool option. Then type the range of IP addresses that the RAS server can assign and any IP address ranges to exclude from automatic assignment. Click OK.
    3. If you’ve selected IPX, click the Configure entry next to IPX. If you want to grant IPX clients access to the RAS server only, and not to the entire network, select the This computer only option. Then click OK.
13. In the Network Configuration dialog box, click OK. In the Remote Access Setup dialog box, click Continue.
14. NCPA again asks for the path to the system files on your Windows NT Server 4.0 CD-ROM. Verify that the NT CD-ROM is in your CD-ROM drive. Type the path and click Continue.
15. Click Close. After configuration completes, restart your computer as prompted.
16. Start the Remote Access Admin utility by selecting the Start Programs Administrative Tools Remote Access Admin entry (see Figure 6-5).
17. On the Users menu, click the Permissions check box. In the Remote Access Permissions dialog box (shown in Figure 6-6), select individual user accounts that are used on RAS clients and configure their dial-in and callback permissions. When you’re done, click OK.

1. While logged on with administrator privileges, select the Start Settings Control Panel option. Double-click the Network entry to start the Network Control Panel Application (NCPA).
2. In the Network dialog box, click the Protocols tab. Select TCP/IP Protocol and click Properties.
3. In the Microsoft TCP/IP Properties dialog box, click the IP Address tab. Then click Advanced.
4. Select the adapter you want to participate in PPTP connections and click the Enable PPTP Filtering check box. When you’re done, click OK.
   If you want more than one of your adapters to filter for PPTP packets, repeat this step for each of them.
5. In the Microsoft TCP/IP Properties dialog box, click OK.
6. Click Close and restart the computer as prompted.

This article describes how to install the File Copy tool included with the Microsoft Windows 2000 Resource Kit. The File Copy tool adds file transfer functionality to the clipboard redirection feature in Microsoft Terminal Services. This tool can be used on client computers running Microsoft Windows for Workgroups, Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows NT 4.0, and Windows 2000.

To make the File Copy tool work, you need to make changes on the Windows 2000 Server as well as each client.

Windows 2000 Server

1. Install the Windows 2000 Resource Kit.
2. Download and install "Rdpclip_hotfix.exe" from the following Microsoft Web site:

   http://www.microsoft.com/windows2000/techinfo/reskit/tools/hotfixes/rdpclip-o.asp

3. Check the follow files and version numbers:

   C:\Program Files\Resource Kit\rdpclip.exe    5.0.2205.1
   C:\Program Files\Resource Kit\fxfr.dll       5.0.2064.1
   C:\Program Files\Resource Kit\rdpdr.dll      5.0.2205.1
         

   NOTE: The path that the reskit is installed in can vary.
4. Open Regedt32, and then change the value data in the Name value from RDPCLIP to FXRDPCLP in the following registry key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\Clip Redirector

5. Change the value data in the Startup Programs value from RDPCLIP to FXRDPCLP in the following registry key:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd

   NOTE: If you have installed Drive Share, change the value data in the Startup Programs value to RDPCLIP,DRMAPSRV.
   
   
6. Rename the new Rdpclip.exe file (located in the resource kit folder) included in the Windows 2000 Resource Kit to Fxrdpclp.exe, and then copy the file to the Winnt\System32 folder.
7. Copy the Fxfr.dll file (located in the resource kit folder) to the Winnt\System32 folder.
8. Restart the computer.

For the Windows 95, Windows 98, Windows NT, or Windows 2000 Clients

1. Copy the 32-bit Fxfr.dll file to the "Program Files\Terminal Services Client" folder.
2. Rename the Rdpdr.dll file in the "Program Files\Terminal Services Client" folder to Rdpdr.pss.
3. Copy the 32-bit Rdpdr.dll file to the "Program Files\Terminal Services Client" folder.

IMPORTANT: The files and instructions for installing Rdpclip.exe in this article only apply to the original Windows 2000 Terminal Services client. Do not use these instructions if you are using the Terminal Services client that ships as part of Service Pack 1 (also known as the Terminal Services Advanced client or TSAC) or the Remote Desktop Connection client that can be downloaded from the Web. Please contact Microsoft Product Support for further help.

REFERENCES

For additional information about Drive Share, click the article number below to view the article in the Microsoft Knowledge Base:

244725 Using Drive Share with Terminal Services

For additional information on the Windows 2000 Resource Kit, click the article number below to view the article in the Microsoft Knowledge Base:

257987 Windows 2000 Resource Kit Rdpclip Utility Is Missing Files

Windows 2000 Resource Kit and the URL has been changed to the following:

http://www.microsoft.com/windows2000/techinfo/reskit/default.asp

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

278139 Rdpclip and Drmapsrv Are Unsupported with Terminal Services Advanced Client

This problem occurs when the following conditions are all true:

You install on a Microsoft Windows NT 4.0 or Microsoft Windows 2000.

-and-

The WinNT folder is located on an NTFS partition.

-and-

You have a folder called Installer under the WinNT folder, and you do not have full access permissions to the Installer folder.

To resolve this problem, change the permissions on the Installer folder to:

Everyone - Read (RX)
Administrators - FullControl
SYSTEM - FullControl

The installer folder is a protected folder. To change perms you will have to go to:
Windows Explorer - Tools - Folder Options - Select View.
Un-check: Hide protected Operating System Files.
The Installer folder is now visible under \Winnt

Symptoms: when running IE, you may get the following errors:

• The Page Cannot Be Displayed.  
• Cannot open the Internet site Web address. A connection with the server could not be established.  
• The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.  
• Cannot find server or DNS Error.  
• An internal error occurred in Windows Internet extensions.
• DNS error and Web page cannot found

Resolutions:

1) Make sure you have loaded TCP/IP. If not, go to Control Panel>Network>Configuration>add>Protocol.
2) Verify network settings by using ping and ipconfig. If you can't ping 127.0.0.1, go to back to 1) or remove and re-install TCP/IP. If you can't ping the router ip, use ipconfig to make sure they are in the same subnet. If you can't ping outside ip or public ip, make sure the computer have correct default gateway. If you can ping public ip but not web site like yahoo.com, check the DNS settings.
3) Make sure the Use a Proxy Server check box is unchecked  if you do not use a proxy server. To do this, go to IE>Tools>Internet Options>Connections>LAN Settings.
4) Disable or remove any software like Comet Cursor may cause IE problem. You can use msconfig to disable.
5) Make sure that there are no parental restrictions on the account after installing ICS with AOL.
6)  If you can connect to the site using the IP but not the Fully Qualified Domain Name (FQDN) such as yahoo.com, check for entries in the Hosts file on the local computer, or rename it.
7) Check network properties and look for multiple instances of the TCP/IP protocol bound to the dial-up adapter. If multiple instances of the TCP/IP protocol are bound to the dial-up adapter, unbind the protocol so that only a single protocol (TCP/IP) is bound to the dial-up adapter. To do this, Network Neighborhood>Properties, click one of the TCP/IP dial-up adapter settings, click Remove, and then click OK.
8) Check for multiple instances of the Wsock32.dll, Winsock.dll, and Wsock.vxd files. Also check the dates and versions of these files. Rename any file that is not in the appropriate folder (Wsock32.dll and Wsock.vxd should be in the Windows\System folder, and Winsock.dll should be in the Windows folder).
9) Clean cookies and Internet Temp files.
10) You may want to logon another user if you are running w2k/xp.
11) You may want to use mscomfig disable some software such as Xupiter, Gator and Comet Cursor.
Re-install IE or upgrade it. We may wan torename all Winsock.dll, Wsock.vxd and Wsock32.dll before the installation.

Can't retrieve e-mail from Hotmail through Outlook Express.

Download IE 55 sp2 : http://hidev.com/files/ie55sp2.zip

You should enable conflict detect which will prevent the DHCP server from giving out addresses that are already in use.  You should then investigate the source of the IP conflicts.  The server will not give out an address that it already has as leased in it's database.  This is typically caused by a rouge DHCP server on your network.

To enable conflict detection, open the DHCP MMC. 
Right click on the DHCP server and choose properties. 
Click on the Advanced tab and set the "Conflict detection attempts" value to 3. 
 
To find out if there is a rouge DHCP server, setup a packet sniffer on your network at various locations and see if multiple DHCP servers respond to client DHCP requests.

IP config is not included in Windows XP!

Look below and download the IP config tool for XP.
The file is in .zip format.

You should enable conflict detect which will prevent the DHCP server from giving out addresses that are already in use.  You should then investigate the source of the IP conflicts.  The server will not give out an address that it already has as leased in it's database.  This is typically caused by a rouge DHCP server on your network.

To enable conflict detection:

1. Open the DHCP MMC. 
2. Right click on the DHCP server and choose properties. 
3. Click on the Advanced tab and set the "Conflict detection attmpts" value to 3. 

To find out if there is a rouge DHCP server, setup a packet sniffer on your network at various locations and see if multiple DHCP servers respond to client DHCP requests.

'NOTE: This script must be run locally
'**Start Encode**
Dim strComputer, CRLF
Dim colDrives, strMsg
Dim WSHNetwork

strComputer = "."
CRLF = Chr(13) & Chr(10)
Set NetworkPROP = WScript.CreateObject("WScript.Network")
Set objWMIService = GetObject _
("winmgmts:" & "!\\" & strComputer & "\root\cimv2")
Set colAdapters = objWMIService.ExecQuery _
("Select * from Win32_NetworkAdapterConfiguration Where IPEnabled = True")


For Each objAdapter in colAdapters
Msgbox "UserName " &Chr(9) & "=" & NetworkPROP.UserName & CRLF & _
    "Host name: " &Chr(9) & "=" & objAdapter.DNSHostName & CRLF & _
"IP address: " &Chr(9) & "=" & objAdapter.IPAddress(i) & CRLF & _
"Description: " &Chr(9) & "=" & objAdapter.Description & CRLF & _
    "User Domain: " &Chr(9) & "=" & NetworkPROP.UserDomain & CRLF & _
"Physical address: " &Chr(9) & "=" & objAdapter.MACAddress & CRLF & _
"DHCP enabled: " &Chr(9) & "=" & objAdapter.DHCPEnabled, _
     vbinformation + vbOKOnly + vbmsgboxsetforeground, _
    "Network Properties"
Next


Set colDrives = NetworkPROP.EnumNetworkDrives

'If there are no mapped drives then inform user, else display
'mapped drives
If colDrives.Count = 0 Then
MsgBox "There are no drives to enumerate.", _
vbInformation + vbOkOnly, _
L_Welcome_MsgBox_Title_Text
Else
strMsg = "Current network drive connections: " & CRLF
For i = 0 To colDrives.Count - 1 Step 2
strMsg = strMsg & CRLF & colDrives(i) & Chr(9) & colDrives(i + 1)
Next

MsgBox strMsg, _
vbInformation + vbOkOnly, _
"Mapped Network Drives"

End If

Add this to specify an IP if requested.

Set Adapter = GetObject("winmgmts:Win32_NetworkAdapterConfiguration=0")
'where the zero at the end is the adapter number
ipaddr = array("172.16.1.170")
subnet = Array("255.255.255.0")
gateway = array("172.16.1.1")

Adapter.EnableStatic(ipaddr,subnet)
Adapter.SetDnsServerSearchOrder(DNS)

Add this if you need a remote station to access:

strComputer = Inputbox("Enter PC name")

'And deleting this line:
strComputer = "."

Script:

'kill all non allowed processess !
'To prevent killing this application also taskmgr.exe is not allowed
'If you want to allow different applications.
'Then before running this script.
' Then place a rem ' for the terminate line
' And remove the rem ' from x=x & c &... and from the line wscript.echo(x)
' Then this script will show the full names off all running applications
' And then you can add that programs full name (case sensitive)
'log off to disable.
'And if you don't have this in your login script or startup then its gone.
'This script keeps running, if you can't hide you can't run.

system1 = "System Idle Process System smss.exe csrss.exe winlogon.exe services.exe "
system2 = "svchost.exe spoolsv.exe cisvc.exe regsvc.exe hh.exe MSTask.exe "
system3 = "Explorer.exe WinMgmt.exe WScript.exe lsass.exe cidaemon.exe "
allsystem2000 = system1 & system2 &system3

allowed = allsystem2000 & "Notepad.exe IExplorer.exe" 'now you're only alowed to run Notepad and internet explorer.

Do until c=-1
for each Process in
GetObject("winmgmts:{impersonationLevel=impersonate}").ExecQuery ("select * from Win32_Process")
  c=instr(allowed,process.name)
  if c = 0 then Process.terminate(0)
  'x = x & c & " - " & process.name + chr(10)

Next
Loop

'wscript.echo(x)

How to fix the logon script not running
Where is logon script located

Where is logon script located

By default, on Windows NT 3.x and 4.0 DC and workstations, the %SystemRoot%\System32\Repl\Import\Scripts folder is shared as NETLOGON for saving logon script. On Windows 2000/XP computers, the folder that is shared as NETLOGON is SYSVOL path\SYSVOL\DomainName\Scripts by default. After creating a logon.bat, you should save it in the shared folder NETLOGON and add it in the properties of each user's profile.

How to fix the logon script not running

SYMPTOMS: If a slow network connection is detected during the initial logon process, the logon script may not run. Resolution: try one or more of the following policies. 1) go to MMC>Local Computer Policy>User Configuration>Administrative Templates>System>Group Policy, check Enable Group Policy slow link detection, and then type 0 in the Connection speed box. 2) Enable Scripts policy processing, and then select the Allow processing across a slow network connection check box.

Persistent and Nonpersitent connections.

Start - Run - cmd:
net use Z: \\serverName\share /persistent:no
(The above maps a drive called Z to \\servername\share that will disconnect when not used)

net use Z: \\serverName\share /persistent:yes
(The above maps a drive called Z to \\servername\share that will NOT disconnect when not used)

Scenario:
After you changed net use I: \\serverA\shared  to \\serverB\shared in your logon script, some windows 2000 machines are still mapping to \\serverA\shared. The reason is that net use /persistent:yes is default settings for NT and win2000/XP.   You can disconnect the old mapping and re-logon. That will map to \\cbgntB\shared. 
Also you may want to use NET USE I: \\servername\folder /persistent:no so that next time when we change the mapping, it will automatically map to the new settings.

Note
By using a non persistent connection you will see a red X on the mapped drive icon. This is not a problem.

Understanding Computer Browser and Protocols The computer browser is to display a directory of all known computers or domains that the computer can reach. The purpose of the browser service is to collect and report the existence of other computers on the network that are sharing file, print, and other resources from the active browser or master servers on each of its active endpoints such as each network protocol that is running on each network card. For example, a computer with TCP/IP and NetBEUI installed on the network interface cards A and B would have four endpoints for the computer browser client.

If the browser client is trying to locate a browser server on each endpoint. It waits until it either one receives valid information or times out on each endpoint before returning. This process can be slow if there is an endpoint that does not contain browser servers or  the active network card is not connected to the network. Also Multihomed servers can create unexpected and undesirable effects with the browser service and a master browser cannot be multihomed because the PDC will contact only the master browser on one of its network adapters. In general, computer browser performance improves with fewer protocols or network cards on a computer. All domain controllers must be singlehomed computers for browsing to operate correctly. Also the computer browser is dependent on NetBIOS. Therefore, in a mixed OS network environment (win9x, NT, ME, W2K and XP), you should have a WINS server in a domain network and enable NetBIOS over TCP/IP (instead of loading NetBEUI) on w2k/xp in the home or small network. If you are running a software firewall, make sure you allow ports 137-139 (both TCP and UDP) in and out. If you don't, your computer cannot hear the master browser election going on and may force itself to become the master browser.

Can't see any or only some computers in My Network Places

Symptoms: you can map the remote computers' shared folder, but you are experiencing the following issues:
1. Can't see any or some computers in My Network Places.
2. It takes long time to show networking computers in My Network Places.
3. The networking computers show in My Network Places randomly

Resolutions: this is likely Computer Browser issue.
1.  If there is a multi-homed or RAS machine on your network becoming the browse master for the wrong subnet, disable the Computer Browser service on the computer.
2. Check any errors in Event Viewer, especially Browser error. If you have peer to peer workgroup network, you may want to disable Computer Browser services on w2k/xp.
3. If you can't disable the Computer Browser service because the compute is the PDC, you can unbind NetBIOS from one interface in network advanced settings.
4. If you can't fix the problem, click here to get consulting services

How to check Browser status

To determined the failed protocol_netcard and check the working status of the Browser service on all installed protocols, you can use a tool comes with the Windows NT resource kit program Browstat.exe. At a command prompt, type the following command: browstat status or just browser to see the lists.

This script is used when you need to re-install network printers using a new or different server.

Error 53 when mapping a network drive

SYMPTOMS: When attempting to map a network drive in a mixed OS network, or misspelling the name of the remote computer, you may receive the following error message: System error 53 has occurred. The network path was not found.

Q: Why win9x can't see win2000 shared printer

W98 guys can see and access the XP Shared Documents folder.  He  asked  me to move his old HP LaserJet II to the new XP system.   No problem,  works  fine EXCEPT  it doesn't show up as a shared device on the W98 boxes. There is no ICS on XP.  File and printer sharing is activated. I set the  printer to share on the XP box and it shows up as shared.  (Hand on the icon). Any ideas?   I think I'm losing it!

A: If you can see the shared printer from XP but not win9x, it is because the printer share name is longer than 12 characters. For more information, go to http://hidev.com/contactus.asp, click tips m-r>why win9x cannot see a printer.

Win9x can't see one of the shared folders

Symptom: your peer network with one Win 98SE and some Win 2000 Pro systems on the LAN operates fines except the W98SE machine
sees one W2kPro machine but not one of it's shared folders. Other W2kPro machines can sees the folder. You have set necessary permissions, users, passwords. Resolution: make sure the  folder's name  is shorter then 12 characters.

Why win9x cannot see a printer

Win 2000 can see the print name or folder name but win9x cannot because the name of the printer or folder is too long (more than 12 characters).

Win9x can't see Win2000/XP

By default, Win2000/XP disables NetBIOS over TCP/IP (NetBT) for selected clients. In a peer-to-peer network without WINS, Win9x  will be unable to browse, locate, or create file and print share connections to a Windows 2000 computer with NetBIOS disabled. So, you must setup the Win2000/XP to uses NetBIOS over TCP/IP to communicate with prior versions of Windows NT and other clients, such as Microsoft Windows 95. Alternatively, you may want to add NetBEUI on all workstations in the peer-to-peer network.

Works™ 6.0 Converter for Works™ and Word™ Users
The Works™ 6.0 Converter allows you to convert word processor documents created in Microsoft Works™ 6.0 to Microsoft Word™ and other Works™ programs. Specifically, this converter works with Works™ 2000, 4.5, and 4.x, and Word™ 2002, 2000, and 97

Works™ 2000 Converter for Word™ 2000 Users
Download Details: 789kb / 5 mins. The Works™ 2000 converter allows you to open a Works™ 2000 .wps file in Word™ and to save a Word™ document as a Works™ 2000 .wps file.

Works™ 2000 Converter for Word™ 97 Users
Download Details: 789kb / 5 mins. The Works™ 2000 converter allows you to open a Works™ 2000 .wps file in Word™ and to save a Word™ document as a Works™ 2000 .wps file.

Word™ 97/2000 Converter for Word™ 6 (Windows 16-bit Operating Systems)
Download Details: 1085kb / 7 mins. If you are using Word™ 6 and 95 for Windows 16-bit Operating Systems, this converter will allow you to open files created by people using Word™ 97/2000. The converter has been enhanced to compress pictures inserted into Word™ documents.

Word™ 97/2000 Viewer (Word™ 97) (Windows 95/98/ NT)">
Download Details: 3860kb / 23 mins. With the Microsoft Word™ Viewer 97/2000, Microsoft Word™ users can share documents with those who do not have Word™ and users without Word™ can open and view Word™ documents.

Word™ 97/2000 Converter for Word™ 6 and 95 Users (Windows 32-bit Operating Systems)
Download Details: 1011kb / 7 mins. If you are using Word™ 6 and 95 for Windows 32-bit Operating Systems, this converter will allow you to open files created by people using Word™ 97/2000. The converter has been enhanced to compress pictures inserted into Word™ documents.

To have your licenses re-issued, you must contact the Microsoft Clearinghouse by phone. 

The first thing you need to do is change your Installation Method to Telephone in the Terminal Services Licensing Wizard Properties (from the View menu, select Properties). 

The Clearinghouse phone number for the US is (888) 571-2048; this number and numbers for other locations can be found in the Terminal Services Licensing Wizard by selecting the appropriate Country or Region on the Properties screen.  Call and speak with a representative and explain that you need to reinstall your Terminal Services CALs and why. 

They will walk you through the process and provide you with an actviation code to enter into the wizard when prompted.

1. Mixed Workgroups' Network Lab Analysis
2. Mixed Domains & Workgroups' Network Lab Analysis
3. How to fix "There are currently no logon servers available to service the logon request" problem

All four machines are in the same subnet and can ping each other. All computers are setup file and printer sharing. A and B's  guest accounts are disabled; C' guest account is enabled.

Results and Analysis:

• All A, B and C can see \\D without any problems (because D is Win98 - not real secure authorization model).
• A can see \\C (because of the guest account enabled), but not B with error: \\B is not accessible. Logon failure: account currently disable (because when logging on A with ntdomain/ntdomain.com, you type lab but it logs on as lab@ntdomain.con or ntdomain\lab (UPN) so that lab@ntdomain.con or ntdomain\lab does not match B's local account lab. In the other words, if logging on A with local computer, no domain, A can see \\B. Also, if you disable or remove lab local account from A, only D, Win98 with domain logon, can see \\A).
• B can see all \\A and \\C (because of using same logon).
• C can see both \\A  and \\B  (When clicking  \\A or \\B, the logon screen come out and type lab as logon name with the same password, test).
•  D can see all \\A, \\B and \\C (because of the same logon in all workgroups and domain).

If you disable the C guest account, a logon screen will show with \\C\guest logon when clicking the \\C from B (WinXP) (Enter Network Password screen will show when clicking the \\C from A, Win2000). No matter what logon account and password (even administrator) you will use, you cannot get into it.

Note: by default, WinXP guest account is disabled. After you share a folder or drive, guest account enable automatically.

Workgroups Network Lab Analysis

Environment: there are four NT 4 servers, ten W2K servers, three workgroups and over three hundreds Win9x, Win2K and a few WinXP in this mixed domain/workgroup network lab. The domain has AD, DNS and WINS setup correctly and all clients in the domain work fine without major problems.

Test and analysis: some laptops with workgroup network settings and some desktops logging on local computers may not be able to access some Win2K servers depending on the logon IDs (no problems with NT 4). For example, my WinXP laptop is setup for a workgroup and I could access most network resources if I logon the workgroup using the domain user account (it is the same local user account and password). However, I might need to enter the same user account and password again (the screen may show "Connecting to servername, User name: Password:" "Incorrect password or username" or "IPC$" depending on the OS) when accessing some Win2K servers. I would be able to access the server after entering the same username and password until restarting the computer. Also, I don't have this problem if I logon as administrator.

To figure out the problem, I did spend a lot time to study the situation. I found that most time I had the problem with the new installed servers even I had created the same user account and password on the local computer. My first thought was the server had not cached my id and password. So, I logged on the server locally and then my laptop. I was able to access the server without prompting for the username and password. To make sure it really works. I rebooted the server and the laptop, and re-logged on the server using administrator id and logged on laptop using my regular domain id. Bingo! It works!

I would also like to mention another case that is not only confirming the above solution but also brings us a troubleshooting tip. After above testing, I still had the problem to access one old Win2K server and I had logged on it myself one year ago. My first try is logon the sever locally by using my logon id. I could not. That is great! I could not access to this server because my local account's password in this server was my old password and different from my current domain id's password. It works after changing the password to match the existing domain id's password.

Conclusion: You get "Connecting to servername, User name: Password:" "Incorrect password or username" or "IPC$" screen for asking username and  password in a mixed domains/workgroups network because one or more of the following possible reasons:

• the client is in the mixed domains/workgroups networks environment.
• The user name and password you are using to log on are not contained in the local user accounts database of the Win2K/XP computers.
• The remote computers haven't cached credential (the local user account and password).
• The Win98-based client is configured with user-level authentication to an NT domain.

The resolution is easy and just makes sure you are using the same logon ID and password and/or the remote computers have the logon ID and password cached. To cache the account and password on the remote computer, you need, at least one time,  to logon the same username and password on the computer locally.

How to fix "There are currently no logon servers available to service the logon request" problem

"There are currently no logon servers available to service the logon request", is most popular and difficult troubleshooting problem in MS networks. The following analysis and troubleshooting are based on past years experiences and MS articles such as Q13941, Q297278 and Q310339.

Symptom: 1) When you logon a local computer using cached credentials and attempt to map the network drives, the operation may be unsuccessful, and you may receive "System error 1311 has occurred. There are currently no logon servers available to service the logon request".

2) The server Event Viewer shows Event Source: NETLOGON, Event ID: 5719, Description: No Windows NT or Windows 2000 Domain Controller is available for domain <domain name>. The following error occurred: There are currently no logon servers available to service the logon request.

3) Mostly, it happens on the slower network, WAN network and remote access such as VPN, dial up. When trying to logon, it may prevent logon scripts and group policies from running, as well as access to their roaming profile and home folder.

4) The Win9x/NT and W2K/XP mixed networks have more chances to get this error message.

5) According to MS, this problem can occur if the client is configured to use p-node or m-node for NetBIOS name resolution. The WINS database does not have the proper domain registrations for pass- through authentication. The p-node or m-node causes a timing issue that prevents the RAS client from finding a logon server.

6) In many situations, it jus happens randomly. After getting this error and rebooting the computer, you may not have any problems to logon.

7) Also in many cases, you may be able to ping other computers and use net use to map the shared folders with domain username and password.

Resolutions: 1) Check the DNS settings on both servers and clients, and correct any errors. 2) It is better to load on protocol, TCP/IP only. 3) If you have mixed network, setup WINS server or install NetBIOS over TCP/IP on W2K/XP instead of loading NetBEUI. 4) Also make sure that Domain Controllers register their DOMAIN<1C> NetBIOS names with the WINS Server. 5) The fix is to use hybrid node instead of p-node or m-node. 6)  If the network is configured to use  for NetBIOS name resolution but the client hasn't been set manually, it could be set through a DHCP release option 46.  7) Apply service pack.

1. Mixed Workgroups' Network Lab Analysis
2. Mixed Domains & Workgroups' Network Lab Analysis
3. How to fix "There are currently no logon servers available to service the logon request" problem

All four machines are in the same subnet and can ping each other. All computers are setup file and printer sharing. A and B's  guest accounts are disabled; C' guest account is enabled.

Results and Analysis:

• All A, B and C can see \\D without any problems (because D is Win98 - not real secure authorization model).
• A can see \\C (because of the guest account enabled), but not B with error: \\B is not accessible. Logon failure: account currently disable (because when logging on A with ntdomain/ntdomain.com, you type lab but it logs on as lab@ntdomain.con or ntdomain\lab (UPN) so that lab@ntdomain.con or ntdomain\lab does not match B's local account lab. In the other words, if logging on A with local computer, no domain, A can see \\B. Also, if you disable or remove lab local account from A, only D, Win98 with domain logon, can see \\A).
• B can see all \\A and \\C (because of using same logon).
• C can see both \\A  and \\B  (When clicking  \\A or \\B, the logon screen come out and type lab as logon name with the same password, test).
•  D can see all \\A, \\B and \\C (because of the same logon in all workgroups and domain).

If you disable the C guest account, a logon screen will show with \\C\guest logon when clicking the \\C from B (WinXP) (Enter Network Password screen will show when clicking the \\C from A, Win2000). No matter what logon account and password (even administrator) you will use, you cannot get into it.

Note: by default, WinXP guest account is disabled. After you share a folder or drive, guest account enable automatically.

Mixed Domains and Workgroups' Network Lab Analysis

Environment: there are four NT 4 servers, ten W2K servers, three workgroups and over three hundreds Win9x, Win2K and a few WinXP in this mixed domain/workgroup network lab. The domain has AD, DNS and WINS setup correctly and all clients in the domain work fine without major problems.

Test and analysis: some laptops with workgroup network settings and some desktops logging on local computers may not be able to access some Win2K servers depending on the logon IDs (no problems with NT 4). For example, my WinXP laptop is setup for a workgroup and I could access most network resources if I logon the workgroup using the domain user account (it is the same local user account and password). However, I might need to enter the same user account and password again (the screen may show "Connecting to servername, User name: Password:" "Incorrect password or username" or "IPC$" depending on the OS) when accessing some Win2K servers. I would be able to access the server after entering the same username and password until restarting the computer. Also, I don't have this problem if I logon as administrator.

To figure out the problem, I did spend a lot time to study the situation. I found that most time I had the problem with the new installed servers even I had created the same user account and password on the local computer. My first thought was the server had not cached my id and password. So, I logged on the server locally and then my laptop. I was able to access the server without prompting for the username and password. To make sure it really works. I rebooted the server and the laptop, and re-logged on the server using administrator id and logged on laptop using my regular domain id. Bingo! It works!

I would also like to mention another case that is not only confirming the above solution but also brings us a troubleshooting tip. After above testing, I still had the problem to access one old Win2K server and I had logged on it myself one year ago. My first try is logon the sever locally by using my logon id. I could not. That is great! I could not access to this server because my local account's password in this server was my old password and different from my current domain id's password. It works after changing the password to match the existing domain id's password.

Conclusion: You get "Connecting to servername, User name: Password:" "Incorrect password or username" or "IPC$" screen for asking username and  password in a mixed domains/workgroups network because one or more of the following possible reasons:

• the client is in the mixed domains/workgroups networks environment.
• The user name and password you are using to log on are not contained in the local user accounts database of the Win2K/XP computers.
• The remote computers haven't cached credential (the local user account and password).
• The Win98-based client is configured with user-level authentication to an NT domain.

The resolution is easy and just makes sure you are using the same logon ID and password and/or the remote computers have the logon ID and password cached. To cache the account and password on the remote computer, you need, at least one time,  to logon the same username and password on the computer locally.

How to fix "There are currently no logon servers available to service the logon request" problem

"There are currently no logon servers available to service the logon request", is most popular and difficult troubleshooting problem in MS networks. The following analysis and troubleshooting are based on past years experiences and MS articles such as Q13941, Q297278 and Q310339.

Symptom: 1) When you logon a local computer using cached credentials and attempt to map the network drives, the operation may be unsuccessful, and you may receive "System error 1311 has occurred. There are currently no logon servers available to service the logon request".

2) The server Event Viewer shows Event Source: NETLOGON, Event ID: 5719, Description: No Windows NT or Windows 2000 Domain Controller is available for domain . The following error occurred: There are currently no logon servers available to service the logon request.

3) Mostly, it happens on the slower network, WAN network and remote access such as VPN, dial up. When trying to logon, it may prevent logon scripts and group policies from running, as well as access to their roaming profile and home folder.

4) The Win9x/NT and W2K/XP mixed networks have more chances to get this error message.

5) According to MS, this problem can occur if the client is configured to use p-node or m-node for NetBIOS name resolution. The WINS database does not have the proper domain registrations for pass- through authentication. The p-node or m-node causes a timing issue that prevents the RAS client from finding a logon server.

6) In many situations, it jus happens randomly. After getting this error and rebooting the computer, you may not have any problems to logon.

7) Also in many cases, you may be able to ping other computers and use net use to map the shared folders with domain username and password.

Resolutions: 1) Check the DNS settings on both servers and clients, and correct any errors. 2) It is better to load on protocol, TCP/IP only. 3) If you have mixed network, setup WINS server or install NetBIOS over TCP/IP on W2K/XP instead of loading NetBEUI. 4) Also make sure that Domain Controllers register their DOMAIN<1C> NetBIOS names with the WINS Server. 5) The fix is to use hybrid node instead of p-node or m-node. 6)  If the network is configured to use  for NetBIOS name resolution but the client hasn't been set manually, it could be set through a DHCP release option 46.  7) Apply service pack.

• Remove the "Log on from the network" right from the Administrator’s group as a whole
• Add the "Log on from the network" right for individual accounts that require administrative access
• Adjust user account policies to lock out users after more than three failed logon attempts
• Require passwords be exactly seven characters in length for maximum strength (because of to the algorithm Microsoft uses to encrypt NT passwords, this length is the hardest to crack)

Microsoft KB813970

WORKAROUND
Method 1: Open in Word
To open the document directly in Word, follow these steps:
Start Word 2003.
On the File menu, click Open.
In the Open dialog box, select the document that you want, and then click Open.

Method 2: Remove the Template from Your Startup Folder
To remove a template from your startup folder, follow these steps:
Quit Word 2003.
Click Start, point to Programs, point to Accessories, and then click Windows Explorer.
Locate one of the following folders:
 
Documents and Settings\username\Application Data\Microsoft\Word\Startup
Program Files\Microsoft Office\Office11\Startup folder

Double-click the Startup folder to open it.
In the right Windows Explorer pane, click to select the template that you want to remove, and then press the DELETE key.

Word, Excel, and PowerPoint 2007 have new XML based default file formats (Word -- .docx, Excel -- .xlsx, and PowerPoint -- .pptx).

New formats?! You may be wondering: "How will these new formats affect previous releases of Office?" Or, put a bit more realistically: "If Roger does not have the 2007 Office system and Tim emails him a Word document saved in Word 2007's new default format (.docx), is Roger stuck?"

No.

One of three things will happen when Roger, or anyone with Office 2003 or XP, tries to open a file saved in our new default file formats:

• Case 1: If Roger keeps his computer up-to-date with the updates offered on Microsoft Update or Office Update and has installed the Compatibility Pack, the .docx file will open in his version of Word. He can then edit the file, click save (giving him a .docx file saved where he specified), and can send the edited .docx back to Tim. Check out a quick demo of this here.
• Case 2: If Roger has kept his computer up-to-date but has not yet installed the Compatibility Pack, when he tries to open one of Word, Excel, or PowerPoint's new document formats, he'll be told that he needs to install the Compatibility Pack to open the file, and linked to the Compatibility Pack download site. With the Compatibility Pack he can open, save, and edit the new file formats just like the legacy formats (.doc, .xls, and .ppt) .
• Case 3: If Roger has not kept his computer up-to-date or installed the Compatibility Pack, when he tries to open the file, he will see the generic Windows unrecognized file type dialogue. If he selects to 'use the web service to find the appropriate program', he will be told that he needs the Compatibility Pack and directed to it. He will then be instructed to update his computer via Microsoft Update or Office Update and install the Compatibility Pack. Now he's set.

In addition, the Compatibility Pack enables anyone with Microsoft Office 2000, the Word Viewer 2003, the Excel Viewer 2003, and the PowerPoint Viewer 2003 (the viewers are free web downloads), to open Word, Excel, and PowerPoint 2007's new XML based formats.

Finally, the Compatibility Pack allows anyone with at least Microsoft Windows 2000 SP4 to save the new formats (.docx, .xlsx, .pptx, etc.), as the legacy formats (.doc, .xls, .ppt, etc.), and vice versa, from Windows.

With the help of converters and viewers from Microsoft Office Online, you can share your Microsoft Office files with people who have different versions of Office programs, or even with people who don't have Office installed.

Converters allow you to open files created by people using different versions of your Office programs.

Viewers provide a means for people who don't have Office programs to see your work. You can provide them with the appropriate viewer along with your Office files.

Access viewers

• Access 2002 viewers
• Access 2000 viewers
• Access 97 viewers

Excel converters and viewers

• Excel 2000 converters
• Excel 2000 viewers
• Excel 97 converters
• Excel 97 viewers

Outlook converters and viewers

• Outlook 2000 converters
• Outlook 97/98 converters
• Outlook 97/98 viewers

PowerPoint converters and viewers

• PowerPoint 2003 viewers
• PowerPoint 2002 viewers
• PowerPoint 2000 converters
• PowerPoint 2000 viewers
• PowerPoint 97 converters
• PowerPoint 97 viewers

Microsoft Project converters

• Microsoft Project 2000 converters

Visio converters and viewers

• Visio 2002 viewers
• Visio 2000 converters

Word converters and viewers

• Word 2002 converters
• Word 2000 viewers
• Word 2000 converters
• Word 97 viewers
• Word 97 converters

Converters and viewers for Macintosh users

• Mactopia downloads

This feature requires you to be using a Microsoft Exchange Server e-mail account in Cached Exchange Mode.

Cached Exchange Mode provides you with a better experience when you use a Microsoft Exchange Server e-mail account. A copy of your mailbox is stored on your computer. This copy provides quick access to your data and is frequently updated with the mail server.

If you work offline, whether by choice or due to a connection problem, your data is still available to you instantly wherever you are. If a connection from your computer to the computer running Exchange server isn't available, Outlook switches to Trying to connect or Disconnected. If the connection is restored, Microsoft Outlook automatically switches back to Connected or Connected (Headers). Any changes you make while a connection to the server isn't available are synchronized automatically when a connection is available. You can continue to work while changes are synchronized.

 When data is optimized for an Exchange server connection type, the type of items that are synchronized with your server mailbox are different. For example, when you use a fast connection, Outlook copies the header, body, and attachments of an e-mail item from the e-mail server to your computer. When a slower connection is selected, only headers are automatically downloaded. The body and any associated attachments are downloaded only when requested by you, or as necessary for synchronization with personal digital assistants (PDAs), auto archiving, and some client-side rules. In a slower connection environment, the Offline Address Book is also not automatically updated. However, you do have the option of manually requesting the update.

Note  Downloading headers only is a feature available when you connect to Exchange Server 2003.

Cached Exchange Mode takes advantage of the ability of Outlook to automatically determine the speed of your connection to the Exchange server, and it optimizes data transmissions for that speed. When the On Slow Connections Download Headers Only setting is selected, Outlook stops automatically downloading full items and also leaves attachments on the server.

For example, you may use a laptop computer at your office and connect via a network cable to your corporate local area network (LAN). You have access to headers and full items, including attachments. You have quick access to the computer running Exchange server. If you disconnect the laptop from the LAN, Outlook switches to Trying to connect status. You can continue to work uninterrupted with your data. If the connection remains unavailable, Outlook switches to Disconnected, periodically checking for server availability. If you have wireless access, Outlook could reestablish a connection to the server and switch back to Connected status. You aren't required to change any setting or restart Outlook.

Later that day, you use a modem for dial-up access to your Exchange server. Outlook recognizes your connection is slow and automatically optimizes for that connection by downloading only headers and not updating the Offline Address Book. Additional optimizations are also made to reduce the amount of data sent over the connection.

By offering different levels of optimization, Outlook can adapt to changing connection environments, such as disconnecting from a corporate LAN, going offline, and then reestablishing a connection to the server via a slower dial-up connection. As your Exchange server connection type changes— LAN, wireless, cellular, General Packet Radio Service (GPRS), and offline— transitions are seamless and never require you to change settings or restarting Outlook.

You always have the option to manually set the connection behavior. In some cases, you may want to control your connection behavior and the amount of data transmitted to and from the Exchange server. At the office, when connected to a high-speed local area network (LAN), Download Full Items is probably the best option. If you connect via a service that charges by the amount of data you send and receive, which is common with cellular and GPRS connections, select Download Headers. The amount of data sent over the connection is reduced and your connection time shortened. You can then request only the full items you need.

1. If you do not already have a Hotmail account, go to the following Hotmail Web site and sign up for an account:

   http://www.hotmail.com

2. Start Outlook Express, and then click Accounts on the Tools menu.
3. Click Add, and then click Mail.
4. In the Display name box, type your name, and then click Next.
5. In the E-mail address box, type your Hotmail address, and then click Next.
6. Click HTTP in the My incoming mail server is box. If Hypertext Transfer Protocol (HTTP) is not an available choice, you are using an earlier version of Outlook Express that does not support Hotmail.
   
   To upgrade your version of Outlook Express, view the following Microsoft Update Web site:

   http://windowsupdate.microsoft.com

7. In the My HTTP mail service provider is box, click Hotmail.
8. Confirm that "http://services.msn.com/svcs/hotmail/httpmail.asp" (without quotation marks) is in the Incoming mail (POP3), IMAP or HTTP server box, and then click next
9. In the Account name box, type your Hotmail account name.
10. In the Password box, type your password, click Next, and then click Finish.
    Your new account appears on the Mail tab of the Internet Accounts dialog box.
11. Click Close. At the prompt to download folders from the mail server that you added, click Yes.

Script:

Const olFolderNotes = 12
x = 1

Set out = CreateObject("Outlook.Application")
Set fs = CreateObject("Scripting.FileSystemObject")

Set ns = out.GetNameSpace("MAPI")
Set fldr = ns.GetDefaultFolder(olFolderNotes )
Set txt = fs.CreateTextFile("notes.txt")

For x = 1 to fldr.Items.Count
     txt.WriteLine fldr.Items(x).Body
     txt.WriteLine String(32,"-")
Next

txt.close

MsgBox "Process Complete."

More:
Search for a help file Vbaoutl9.chm .
It should be in the ms office directory or somewhere like that, it has a list of all objects you can use with outlook.

How can I list all hosts?
To list all hosts in the same subnet, leave blank on the host pc or address. Alternatively, you may type the subnet that the computer is on. For example, if the IP address of the computer is 10.0.0.25, then the subnet is 10.0.0.255.

How to remotely verify if a router's ports are open?
If you would like to check to see if the router's ports are open for using pcAnywhere to connect over the Internet to a host that is behind a router, you can use telnet command to do this.

Example:
type: open 10.0.0.1:5631, where the 10.0.0.1 represents the IP address of the router.

If you see the message "Could not open connection" or you see a blank screen with a blinking cursor, then one of the following is true: 1) The ports are closed. 2) You are using the wrong router. 3) The host is not waiting for a connection. 4) You are connecting through a firewall that is blocking the pcAnywhere ports.

If you see the error "Connection to host lost," then the ports are open but the host is refusing the connection for some other reason. Check for entries in the TCP/IP options that limit connections to specific addresses. To do this, open pcAnywhere>Tools>Options>Host Communications tab. Ensure that there are no addresses entered in the "Limit connections to the following names or IP addresses" field. If there are, either delete them or add the address or name of the remote computer you are trying to connect with.

If you see the message "Please press Enter," then the port is open.

Which ports should be open on a router or firewall for accessing pcAnywhere

The default pcAnywhere port numbers are 5631 (Data Port or TCP) and 5632 (Status Port or UDP).
The default ports can easily be changes to any value you like provided that it is not already being used by another client.

Windows XP Internet Connection Firewall prevents pcAnywhere TCP/IP connection

You may not be able to make a TCP/IP connection to a pcAnywhere host running if you are using XP ICF.

FIX:
In order to run a pcAnywhere Host on a system using ICF, you must add pcAnywhere as a service and enable the service. To add and enable the pcAnywhere service, go to

1. Control Panel>Network Connections, right-click the connection that you are using with pcAnywhere and select Properties>Advanced>Settings>Services>Add, type a name for the service such as pcAnywhere in the "Description of Service" field.
2. Type the Host computer's machine name or IP address in the "Name or IP address of computer hosting this service on your network" field. 
3. Type 5631 in the "External Port number for this service" field and 5631 in the "Internal Port number for this service" field. 
4. Check the box next to TCP and click OK