Home | Troubleshooting |  Quick Setup  |  Cisco How to  |  Data Recovery  |  Forums   | Blog | IT Exam Practice | Services  | About Us | Chicagotech MVP  | Search  | Contact Us  |                 

 

Windows Server 2003 - How to

How to create Mac share folder on 2003
How to disable the Shutdown Event Tracker
How to Install File and Printer Sharing on 2003 Server
How to Perform an Emergency Shutdown in Server 2003
How to prevent to delete the folders.
How to prevent remove folders
How to Roll Back to an Earlier Driver
How to Undo Any Recent Changes to the Computer
How to Use a Parallel Installation to Identify the Cause of the Shutdown Behavior

NAT/Firewall issue

How to create Mac share folder on 2003

To create Mac share folder, you need to install File Service of Macintosh. Then create a share folder under Computer Management.

How to disable the Shutdown Event Tracker

To disable the Shutdown Event Tracker, go to HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Reliability, change a value with the following:

Data Type: DWORD
Value Name: ShutdownReasonOn
Value: 0

How to Install File and Printer Sharing on 2003 Server

By default, a Server 2003 computer is installed with Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and TCP/IP. You can create a Server 2003 file server and print server manually, or you can use the wizards that are provided in the Configure Your Server Wizard administrative tool.

How to Perform an Emergency Shutdown in Server 2003

Press CTRL+ALT+DELETE>Shut down, press and hold down CTRL, and then click Shut down or press ENTER.

How to prevent to delete the folders.

Look at the advanced properties of the folder and look at special permissions. You can prevent certain users deleting folders and/or files.

How to Roll Back to an Earlier Driver

  1. Open Device Manager, and then expand the device type that contains the device that you want.
  2. Right-click the device that you want to roll back to an earlier driver, and then click Properties on the shortcut menu.
  3. Click the Driver tab, and then click Roll Back Driver.
  4. Follow the steps to replace the device driver with an earlier version.
  5. If you are prompted to restart the computer, click Yes.

How to Troubleshoot Shutdown Problems in Server 2003

; 1. Use Task Manager to identify the cause of the shutdown behavior.
2. Undo any recent changes to the computer.
3. Use safe mode to identify the cause of the shutdown behavior.
4. Confirm that the computer's complementary metal oxide semiconductor (CMOS) and basic input/output system (BIOS) settings are correct.

How to Undo Any Recent Changes to the Computer

If the shutdown behavior occurs immediately after you make a change to the computer (for example, you install or upgrade a program, a service, or hardware that has device drivers), undo the last change that you made. For example, remove either the last driver or the last program that you installed, and then shut down and restart the computer to test whether the computer shuts down correctly.

How to Use a Parallel Installation to Identify the Cause of the Shutdown Behavior

  1. Install a new copy of Windows Server 2003 to a separate partition on the computer (create a parallel installation), and then install drivers and programs one at a time on the parallel installation.
  2. Shut down and restart the computer between each program installation and note if the incorrect shutdown behavior occurs.
    If the behavior occurs, the last driver or the program that you installed may be the cause of the incorrect shutdown behavior.
  3. Either remove or update the driver or the program from the original installation, and then test Windows for correct shutdown.

    Note: If the problem is resolved, remove the parallel Windows installation.

    NAT/Firewall issue

    Symptoms: 1. All inside client behind the 2003 server with NAT/Firewall can access the Internet but the server can't.
    2. The server gets time out message when ping any IP.
    3. The server may get destination can't be reached while ping an IP even it has correct routing table.

    Causes: 1. Uncorrected TCP/IP settings.
    2. Uncorrected NAT/Firewall settings.

    Post your questions, comments, feedbacks and suggestions

    Contact a consultant

     

 

Hit Counter   This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.