Question about Microsoft Windows Server Standard 2003 for PC

1 Answer

Client login problem.

I have just recovered failed server from system state backup after recovering i found that when users try to login sometimes they recieve unable to logon to domain ,domain controller unavailable errors i tried reseting user and computer accounts and also restarting dns server service but to no avail pls anybody who can help...
thanx in advance

Posted by on

1 Answer

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

    Guru:

    An expert who has written 7 tips or uploaded 3 video tips

  • Expert
  • 161 Answers

It is because you have been infected by viruses,....try to sacan you pc with effective anti-virus..

Posted on Feb 06, 2010

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

Tip

How to recover sql 2000 sa password


Microsoft SQL Server 2000 is a full-featured relational database management system that offers a variety of administrative tools to ease the burdens of database development, maintenance and administration. It operates in one of two authentication modes: Windows Authentication Mode (the default) or Mixed Mode.

When you install the SQL Server 2000, you can log in the server with Windows Authentication and SQL Server Authentication if you select mixed mode authentication. If you select Windows Authentication, you cannot assign a sa password during installation. However, you should set the sa password after installation.

It is very easy for one to set sa password in SQL 2000. Just follow the below steps:

* 1. Expand a server group, and then expand a server.
* 2. Expand Security, and then click Logins.
* 3. In the details pane, right-click SA, and then click Properties.
* 4. In the Password box, type the new password.

The type of client connections determines the choice of security mode. If all of the incoming clients support trusted connections, you can use Windows Authentication Mode. If some clients do not support trusted connections, you can select Mixed Mode.

If you forget the sa password, you will need to use MS SQL Server Password Unlocker to reset sa password SQL 2000. MS SQL Server Password Unlocker is easy yet powerful SQL Server password reset software for you to reset SQL password, including reset SA password and other user passwords. It provides you an easy and safe way to reset SQL Server password for Microsoft SQL Server 2000/2005/2008 in a minute. No need for you to reinstall MS SQL Server on your PC. The file in master.mdf format is enough for you to recover sa password SQL 2000.

Steps to reset sql password 2000 for sa as follows:
* 1. Download and install MS SQL Server Password Unlocker.
* 2. Click the application icon to run it.
* 3. Click Open to import your master.mdf file. All the user names of your MS SQL Server will be displayed.
* 4. Select sa account, click Change password button to reset sa password.
* 5. Type a new password, and then click OK to finish your operation.

Note: This method to reset sa password in sql server 2000 is usually applied when you cannot login SQL Server 2000 by Windows Authentication wile you forget system administrator login password.

More information about sa password:

According to Microsoft, System administrator (sa) is a special login provided for backward compatibility. By default, it is assigned to the sysadmin fixed server role and cannot be changed. Although sa is a built-in administrator login, do not use it routinely. Instead, make system administrators members of the sysadmin fixed server role, and have them log on using their own logins. Use sa only when there is no other way to log in to an instance of Microsoft SQL Server.

on Oct 19, 2010 | Computers & Internet

5 Answers

Need Help to backup SQL database in safe mode


kindly choose the option safe mode with networking and then try.

Sep 10, 2009 | Microsoft Computers & Internet

Tip

Reset sql sa password directly and efficiently


A few days ago, I had a painful experience that I lost SA password on my MS SQL Server database, and I almost took the whole weekend to look for an efficient way to reset SA password. I asked friends, searched on Internet and even bought some book.... Fortunately, I finally got a SQL server password recovery software and it instantly reset SA password without data loss. And I also got a couple of good solutions for sql sa password reset to save your weekend in case you have lost or forgot MS SQL Server passwords (SA password!).



Option 1 : Use MS SQL Server Password Unlocker to Recover/Reset SA Password

The most direct, efficient way to reset SA password is to take use of the third part utility - SQL server password recovery software. Just two steps:

Step 1: Access to master.mdf file, which is default at C:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf

Step 2: Select SA password and reset SA password
So, Reset SA password successfully!



Option 2 : Recover or Reset SA Password with Other SQL Server Login
If there is any other SQL Server Login that is a member of sysadmin role, you can log in using that account and reset SA password of SQL Server. Reset sql sa password as described here :

SQL SERVER - Reset Password of SA Login Using Management Studio.

Login into SQL Server using Windows Authentication.

In Object Explorer, open Security folder, open Logins folder. Right Click on
SA account and go to Properties.

Reset SA password, and confirm it. Click OK.

Make sure to restart the SQL Server and all its services and test new password by log into system using SA login and new password.



Option 3 : Recover or Reset SA Password with Windows Login that is a member of Windows Admin Group

If there is any other Windows Login that is a member of Windows Admin Group, log in using that account. Start SQL Server in Single User Mode as described followings :

SQL SERVER - Start SQL Server Instance in Single User Mode.

There are certain situation when user wants to start SQL Server Engine in "single user" mode from the start up.

To start SQL Server in single user mode is very simple procedure as displayed below.

Go to SQL Server Configuration Manager and click on SQL Server 2005 Services. Click on desired SQL Server instance and right click go to properties. On the Advance table enter param '-m;' before existing params in Startup Parameters box.

Make sure that you entered semi-comma after -m. Once that is completed, restart SQL Server services to take this in effect. Once this is done, now you will be only able to connect SQL Server using sqlcmd.

on Oct 05, 2010 | Computers & Internet

Tip

How to Retrieve Shift-Deleted Items in Microsoft Outlook


A. ON THE CLIENT COMPUTER

REGISTRY EDITING
Warning: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Backup the registry first.


By default, the Recover Deleted Items functionality is only enabled on the Deleted Items folder in a user's private folders; items that are hard deleted cannot be recovered. To enable the Recover Deleted Items functionality on mail folders other than Deleted Items (for example, for Sent Items, Drafts, Outbox and Inbox folders), you must make the following changes to the registry:


1. Start Registry Editor (Regedt32.exe).


2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\Options


3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: DumpsterAlwaysOn
Data type: DWORD
Value data: 1


4. Quit Registry Editor.

On MS OUTLOOK


Select the MAILBOX folder, go to INBOX folder.
On the Tools menu, select Recover Deleted Items. (This option will not be available unless you are currently viewing the contents of your Deleted Items folder.)


From the pop-up window, click the message you want to recover. (Note that the date shown next to the message subject is the date that you emptied it from your Deleted Items folder, and not the date of the original message. To see the original message date, you may need to scroll to the right or expand the pop-up window.)
Click the Recover Selected Items button.


The items will be returned to your Deleted Items folder, and then you can move them to other folders.

Note: Deleted items are only available for recovery for a limited period which is based on IRRI exchange server retention policy configuration. You may check it with Kuya Boy.



B. FOR EXCHANGE SERVER ADMIN

CONFIGURING DELETED ITEM RECOVERY


Exchange Server Configuration


1. In the Exchange Server Administrator program, open the properties of the Private Information Store, and select the General tab.


2. Set the number of days that you want messages saved after they have been deleted.

NOTE: You can also set the messages not to be deleted until a backup has been done. You can override this by setting the retention time on individual mailboxes in the Properties for the mailbox by changing the


Deleted Items Retention time on the Limits tab.

on Feb 15, 2010 | Computers & Internet

4 Answers

Restoring files from the database


I suggest you use the Enterprise manager (gui tool to manage SQL).
Restoring a single table is not an option.
You can however restore a file or filegroup.
Make sure to backup before you start and NOT to restore database to its original name or original file location, to avoid acidents.
Normally you will have databases with only 2 files: the data at its Primary file group, and log file.
You may wish to create a new file group and move tables to the new group by recreating them there and exporting data from old table to new table. Then recreate indexes. This may prove to be complex as all tables and indexes have unique names and can't coexist with exact duplicate of them.

oh yea..... did I say backup?
well just in case backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup backup
but dont overwrite that backup

Feb 11, 2008 | Microsoft SQL Server 2000 Standard Edition...

Tip

Here are some of the best practices to take into consideration in any backup &...


Here are some of the best practices to take into consideration in any backup & recovery system:
  • Usually perform system state backups of your servers frequently. Each computer on a Windows network has a corresponding computer account in Active Directory. Like a user account, the computer account has an associated password. The difference is that the password is assigned, and periodically changed, by Windows. If you try to restore a system state backup that is too old, the computer account password that is stored in the backup will no longer match the password that is bound to the computer account in Active Directory. As a result, the machine won't be able to participate in the domain. There are workarounds, but it is usually easier to just make frequent system state backups of your servers, & use these backups to recover the servers when needed.
  • Always backup the data, the server's operating system, & the applications installed on the server. Although it is true that, if a server fails and you need to perform a full recovery, you can reinstall the operating system & the applications & then restore any data. However, time is of the essence when trying to recover from a crash. It is much faster to restore everything from backup than it is to manually install an operating system and a set of applications. More important, it is often difficult to manually configure a server so that it matches its previous configuration. Backing up the entire server ensures that its configuration will be exactly as it was before the crash.
  • Periodically test your backups to make sure you are able to use them for recovery when the disaster strikes. Always remember that we perform backups in order to be able to restore from then when we need to. So, we have to make sure our backups are usable.
  • For some applications (for example, Microsoft SQL Server, Microsoft Exchange Server, Lotus Domino Server, ... etc), a file-level backup is insufficient. These applications usually utilize open databases that need a special backup agent to back them up consistently while they are being in-use. Usually make sure that you are using the correct backup agent needed by your application.
  • While you should keep backups off site, consider waiting until the end of the business day to remove the previous night's tapes from the building. This way, if your server fails early during the day, you will not have to wait for hours till you can get the tapes on-site again & start the recovery.
  • Construct your backup architecture in a way that avoids (at least as much as possible) having a single point of failure. If possible, have a backup for your backups, or configure 2 independent backup schedules to run everyday.
  • Do not rely solely on a disk-to-disk backup solution. Although disk-to-disk backup solutions offer many advantages over traditional tape backups, they should not be the only backup solution to rely upon. In such a scenario, the backup server is prone to the same risks as the servers it protects. A hurricane, lightning strike, fire, or flood could wipe out your backup server along with your other servers. For this reason, it is important to dump the contents of your disk based backups to tape on a frequent basis, and then store those tapes in an off-site secure storage.
  • When deciding to replace your current backup technology with a newer one, do not get rid of the old tapes, tape device(s) & backup software. At least, do not do this unless you are sure that your newer tape device(s) support the older tapes, or that you have moved the older backups to newer media supported by the newer tape device(s). This way, when it is required to retrieve data from the old backups, you will be able easily to retrieve the required data. This also could apply to the older backup software if the newer backup application does not support the older tapes or tape device(s).
  • There is no denying that it is important to secure your backups, but it is equally important to consider the consequences of your security measures. If you find yourself having to restore a backup after a major system failure, the last thing you need is an ill-conceived security mechanism standing in the way of the recovery. For example, if you are planning to use hardware-level encryption, do not forget (when time comes to upgrade your backup hardware) to make sure that your new hardware supports the previously used encryption.
  • Always use a long tape rotation scheme, or at least keeping some of your backup tapes as long-term archives.

on Jan 05, 2010 | Computers & Internet

Tip

Backup Best Practices


Here are some of the best practices to take into consideration in any backup & recovery system:
  • Usually perform system state backups of your servers frequently. Each computer on a Windows network has a corresponding computer account in Active Directory. Like a user account, the computer account has an associated password. The difference is that the password is assigned, and periodically changed, by Windows. If you try to restore a system state backup that is too old, the computer account password that is stored in the backup will no longer match the password that is bound to the computer account in Active Directory. As a result, the machine won't be able to participate in the domain. There are workarounds, but it is usually easier to just make frequent system state backups of your servers, & use these backups to recover the servers when needed.
  • Always backup the data, the server's operating system, & the applications installed on the server. Although it is true that, if a server fails and you need to perform a full recovery, you can reinstall the operating system & the applications & then restore any data. However, time is of the essence when trying to recover from a crash. It is much faster to restore everything from backup than it is to manually install an operating system and a set of applications. More important, it is often difficult to manually configure a server so that it matches its previous configuration. Backing up the entire server ensures that its configuration will be exactly as it was before the crash.
  • Periodically test your backups to make sure you are able to use them for recovery when the disaster strikes. Always remember that we perform backups in order to be able to restore from then when we need to. So, we have to make sure our backups are usable.
  • For some applications (for example, Microsoft SQL Server, Microsoft Exchange Server, Lotus Domino Server, ... etc), a file-level backup is insufficient. These applications usually utilize open databases that need a special backup agent to back them up consistently while they are being in-use. Usually make sure that you are using the correct backup agent needed by your application.
  • While you should keep backups off site, consider waiting until the end of the business day to remove the previous night's tapes from the building. This way, if your server fails early during the day, you will not have to wait for hours till you can get the tapes on-site again & start the recovery.
  • Construct your backup architecture in a way that avoids (at least as much as possible) having a single point of failure. If possible, have a backup for your backups, or configure 2 independent backup schedules to run everyday.
  • Do not rely solely on a disk-to-disk backup solution. Although disk-to-disk backup solutions offer many advantages over traditional tape backups, they should not be the only backup solution to rely upon. In such a scenario, the backup server is prone to the same risks as the servers it protects. A hurricane, lightning strike, fire, or flood could wipe out your backup server along with your other servers. For this reason, it is important to dump the contents of your disk based backups to tape on a frequent basis, and then store those tapes in an off-site secure storage.
  • When deciding to replace your current backup technology with a newer one, do not get rid of the old tapes, tape device(s) & backup software. At least, do not do this unless you are sure that your newer tape device(s) support the older tapes, or that you have moved the older backups to newer media supported by the newer tape device(s). This way, when it is required to retrieve data from the old backups, you will be able easily to retrieve the required data. This also could apply to the older backup software if the newer backup application does not support the older tapes or tape device(s).
  • There is no denying that it is important to secure your backups, but it is equally important to consider the consequences of your security measures. If you find yourself having to restore a backup after a major system failure, the last thing you need is an ill-conceived security mechanism standing in the way of the recovery. For example, if you are planning to use hardware-level encryption, do not forget (when time comes to upgrade your backup hardware) to make sure that your new hardware supports the previously used encryption.
  • Always use a long tape rotation scheme, or at least keeping some of your backup tapes as long-term archives.

on Jan 04, 2010 | Computers & Internet

Not finding what you are looking for?
Microsoft Windows Server Standard 2003 for PC Logo

127 people viewed this question

Ask a Question

Usually answered in minutes!

Top Microsoft Computers & Internet Experts

micky dee

Level 3 Expert

2716 Answers

Piyal Perera
Piyal Perera

Level 3 Expert

528 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18390 Answers

Are you a Microsoft Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...