The blog of Windows Wally, a Windows Support Technician helping common people solve frustrating computer problems.



How to fix Error 1722

Reader Question:
“Hi Wally, I am using Windows Server 2003. I’m having problems with an error regarding user accounts. Error 1722.”
- Samuel Y., USA

Before addressing any computer issue, I always recommend scanning and repairing any underlying problems affecting your PC health and performance:

  • Step 1 : Download PC Repair & Optimizer Tool (WinThruster for Win 10, 8, 7, Vista, XP and 2000 – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.

Setting up weekly (or daily) automatic scans will help prevent system problems and keep your PC running fast and trouble-free.

Wally’s Answer: The “Error 1722″ error message may appear in Windows Server 2003 sometimes. It appears in relation to the NetUserGetLocalGroups function. Specifically, this issue occurs when a computer tries to access an Active Dictionary using the the Domain Name\User Name format.

What is Error 1722?

The Error message 1722 appears when a program which is running Windows Server 2003, Windows 2000, or a Windows XP tries to use the NetUserGetLocalGroups function. This function is used to search an Active Directory in another domain. This error may occur when the format of the username is in the Domain Name\User Name format. IT may appear as follows:

A system error has occurred: 1722

Why does Error 1722 occur?

Error 1722 occurs when NetBIOS name resolution is not working because the computer may not have defined WINS servers. There may also be some missing entries in the LMHOSTS file, or NetBIOS is disabled over TCP/IP.

How to fix Error 1722?

This error does not appear if the user name does not include the domain name. If the the User Name format is used instead of the Domain Name\User Name format, the the error does not appear. If no WINS server is defined or NetBIOS over TCP/IP is disabled, then the Domain Name portion of the user name in Domain Name\User format should be a fully qualified domain name or FQDN.

So, if username is : testdomain.microsoft.com,

then, it should be : testdomain.microsoft.com\username

This is no longer an issue in Microsoft Windows Server 2003 Service Pack 1 and in Microsoft Windows Server 2000 Service Pack 4, Rollup 1.

If you already have the latest Service Pack of Windows running on your computer than you do not have to worry about this error.

Enabling NetBIOS over TCP/IP

Follow these steps to enable NetBIOS over TCP/IP:

Click Start > Control PanelNetwork Connections

Choose the Local Area Connection that needs to be configured > click Properties.

Internet Protocol (TCP/IP) > Properties > Advanced > WINS tab.

Click Enable NetBIOS over TCP/IP > OK.

I Hope You Liked This Blog Article! If You Need Additional Support on This Issue Then Please Don’t Hesitate To Contact Me On Facebook.

Is Your PC Healthy?

I always recommend to my readers to regularly use a trusted registry cleaner and optimizer such as WinThruster or CCleaner. Many problems that you encounter can be attributed to a corrupt and bloated registry.

Happy Computing! :)

Wally’s Answer Rating

Quick Solution (How fast can you do it?)
Easy Solution (How easy is it?)
Beginner-Friendly (Recommended for beginners?)

Summary: Every Windows Wally blog post is evaluated on these three criteria. The average of all three elements determines an "Overall Rating" for each blog post.

3.6

Overall Rating


Tags: , , , , , , , , ,


About the Author

Windows Wally is a helpful guy. It’s just in his nature. It’s why he started a blog in the first place. He heard over and over how hard it was to find simple, plain-English solutions to Windows troubleshooting problems on the Internet. Enter: Windows Wally. Ask away, and he will answer.