Event ID 9011 — TCP/IP Network Connectivity

Event ID 9011 — TCP/IP Network Connectivity

Updated: April 17, 2008

Applies To: Windows Server 2008

Network connectivity allows your computer to communicate with other hosts on your network and the Internet. Connectivity might be full (Internet and intranet), partial (local subnet only), or non-existent.

Event Details

Product: Windows Operating System
ID: 9011
Source: tcpip
Version: 6.0
Symbolic Name: EVENT_TRANSPORT_BAD_PROTOCOL
Message: %2 received an unexpected %3 packet from a remote computer.

Resolve
Initialize TCP/IP

Refresh the protocol configuration on the network interface by disabling it and then enabling it again.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To disable and then re-enable the network interface:

  1. Click Control Panel, double-click Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network interface you want to disable, and then click Disable.
  3. Right-click the network interface again, and then click Enable.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify TCP/IP connectivity:

  1. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Click Continue when prompted by User Account Control, and then provide the administrator password, if requested.
  3. Type ping followed by an IP address of another host on the network.
  4. If the ping command succeeds, connectivity is established.

Note:   Windows Firewall might prevent a succesful ping operation. You might need to configure a port exception for the ping to succeed.

Related Management Information

TCP/IP Network Connectivity

Networking

Related:

Event ID 9009 — TCP/IP Network Performance

Event ID 9009 — TCP/IP Network Performance

Updated: April 17, 2008

Applies To: Windows Server 2008

Network performance encompasses all aspects of data transfer performance, such as download and upload speeds, number of packets dropped versus packets delivered, and the round-trip time of connections.

These aspects of network performance might be affected by congestion in the network. In the case of wireless networks, signal attenuation, electromagnetic interference, and the mobility of the host also affect network performance.

Event Details

Product: Windows Operating System
ID: 9009
Source: tcpip
Version: 6.0
Symbolic Name: EVENT_TRANSPORT_TRANSFER_DATA
Message: %2 could not transfer a packet from the network adapter. The packet was dropped.

Resolve
Reduce the load on the remote computer

If the packets are dropped because of network congestion and poor network performance, reduce the load on, or increase the capacity of, the computer.

 

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To measure network performance, run Performance Monitor:

  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Click Continue when prompted by User Account Control, and then provide the administrator password, if requested.
  3. In the Performance Monitor console tree, click Reliability and Performance.
  4. Network, CPU, and memory utilization data are available in the details pane.

If you have recorded Performance Monitor counters in the past, compare the current load to your average loads over time. If you do not have any baseline readings from past performance monitoring, continue to monitor network, CPU, and memory utilization by looking for large fluctuations in performance that might indicate a heavy traffic load or an attack.

Related Management Information

TCP/IP Network Performance

Networking

Related:

Event ID 9008 — TCP/IP Network Interface Configuration

Event ID 9008 — TCP/IP Network Interface Configuration

Updated: April 17, 2008

Applies To: Windows Server 2008

The network configuration interface settings of your computer determine the way in which it communicates with other computers and devices on the network.

Event Details

Product: Windows Operating System
ID: 9008
Source: tcpip
Version: 6.0
Symbolic Name: EVENT_TRANSPORT_QUERY_OID_FAILED
Message: %2 failed while querying OID %3 on network adapter %4.

Resolve
Remove and add TCP/IP protocol or reset Winsock catalog

The TCP/IP protocol is not properly installed on the network interface.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To remove the protocol from the network interface and add it again:

  1. Click Control Panel, double-click Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network interface you want to repair, click Properties, clear the Internet Protocol Version 4 (TCP/IPv4) check box, and then click OK.
  3. Right-click the same network interface, click Properties, select the Internet Protocol Version 4 (TCP/IPv4) check box, and then click OK.

If the problem persists, reset the Winsock catalog:

  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Click Continue when prompted by User Account Control, and then provide the administrator password, if requested.
  3. At the command prompt, type netsh winsock reset, and then press ENTER.
  4. The output of the netsh winsock reset command should indicate a successful reset.
  5. Restart the computer to complete the reset of the Winsock catalog.

Verify

To verify that an IP address is assigned:

  1. At the DHCP-enabled client computer, click Start, click Run, and then type cmd.
  2. Type ipconfig /all to view lease-status information.
  3. The output of the ipconfig command should show an IPv4 or IPv6 address marked “preferred.”

Related Management Information

TCP/IP Network Interface Configuration

Networking

Related:

Event ID 9006 — TCP/IP Network Interface Configuration

Event ID 9006 — TCP/IP Network Interface Configuration

Updated: April 17, 2008

Applies To: Windows Server 2008

The network configuration interface settings of your computer determine the way in which it communicates with other computers and devices on the network.

Event Details

Product: Windows Operating System
ID: 9006
Source: tcpip
Version: 6.0
Symbolic Name: EVENT_TRANSPORT_ADAPTER_NOT_FOUND
Message: %2 could not find network adapter %3.

Resolve
Remove and add TCP/IP protocol or reset Winsock catalog

The TCP/IP protocol is not properly installed on the network interface.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To remove the protocol from the network interface and add it again:

  1. Click Control Panel, double-click Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network interface you want to repair, click Properties, clear the Internet Protocol Version 4 (TCP/IPv4) check box, and then click OK.
  3. Right-click the same network interface, click Properties, select the Internet Protocol Version 4 (TCP/IPv4) check box, and then click OK.

If the problem persists, reset the Winsock catalog:

  1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Click Continue when prompted by User Account Control, and then provide the administrator password, if requested.
  3. At the command prompt, type netsh winsock reset, and then press ENTER.
  4. The output of the netsh winsock reset command should indicate a successful reset.
  5. Restart the computer to complete the reset of the Winsock catalog.

Verify

To verify that an IP address is assigned:

  1. At the DHCP-enabled client computer, click Start, click Run, and then type cmd.
  2. Type ipconfig /all to view lease-status information.
  3. The output of the ipconfig command should show an IPv4 or IPv6 address marked “preferred.”

Related Management Information

TCP/IP Network Interface Configuration

Networking

Related:

Event ID 9001 — TCP/IP Network Connectivity

Event ID 9001 — TCP/IP Network Connectivity

Updated: April 17, 2008

Applies To: Windows Server 2008

Network connectivity allows your computer to communicate with other hosts on your network and the Internet. Connectivity might be full (Internet and intranet), partial (local subnet only), or non-existent.

Event Details

Product: Windows Operating System
ID: 9001
Source: tcpip
Version: 6.0
Symbolic Name: EVENT_TRANSPORT_RESOURCE_POOL
Message: %2 could not allocate a resource of type %3 due to system resource problems.

Resolve
Initialize TCP/IP

Refresh the protocol configuration on the network interface by disabling it and then enabling it again.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To disable and then re-enable the network interface:

  1. Click Control Panel, double-click Network and Sharing Center, and then click Manage network connections.
  2. Right-click the network interface you want to disable, and then click Disable.
  3. Right-click the network interface again, and then click Enable.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify TCP/IP connectivity:

  1. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Click Continue when prompted by User Account Control, and then provide the administrator password, if requested.
  3. Type ping followed by an IP address of another host on the network.
  4. If the ping command succeeds, connectivity is established.

Note:   Windows Firewall might prevent a succesful ping operation. You might need to configure a port exception for the ping to succeed.

Related Management Information

TCP/IP Network Connectivity

Networking

Related:

Event ID 8215 — File Screen Enforcement

Event ID 8215 — File Screen Enforcement

Updated: January 27, 2011

Applies To: Windows Server 2008

You can create file screens to prevent users from saving unauthorized files on volumes or folders. There are two types of file screen enforcement: active and passive enforcement. Active file screen enforcement does not allow the user to save an unauthorized file. Passive file screen enforcement allows the user to save the file, but notifies the user that the file is not an authorized file. You can configure notifications, such as events logged to the event log or e-mails sent to users and administrators, as part of active and passive file screen enforcement.

Event Details

Product: Windows Operating System
ID: 8215
Source: srmsvc
Version: 6.0
Symbolic Name: SRM_DS_ACTION_EVENT_MSG
Message: %1

Resolve
Review the event log message and take appropriate action

You can configure File Server Resource Manager (FSRM) to log an event when a user has attempted to save an unauthorized file to a volume or folder that is under file screening management. The event log message will report values specific to the user action, depending on the variables specified in File Server Resource Manager when the event alert is configured (for example, the name and e-mail address of the user, and the name of the unauthorized file). You can use the information reported in the event log message to take appropriate action, according to the storage policies of your organization.

If you would like to change the text or the values that will be reported in the event log message, you must change the notification properties of the file screen. If the file screen derives from a file screen template, and you want to change the event notification for all file screens that derive from that template, you can make the changes to the file screen template and then apply the changes to all file screens that derive from it.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To change the notification properties of a file screen template or of a specific file screen:

  1. Open File Server Resource Manager. Click Start, point to All Programs, click Administrative Tools, and then click File Server Resource Manager.
  2. To list all currently configured file screens, in the console tree, under File Screening Management, click File Screens.
  3. If you want to modify the template a file screen derives from and apply the changes to other file screens that derive from that template:
    1. Identify the template that was used to create the file screen. The name of the template is listed in the Source Template column. If there is no template listed, you need to modify the specific file screen instead.
    2. Ensure that the value in the Match Template column is Yes. If the value is No, you need to modify the specific file screen instead.
    3. In the console tree, click File Screen Templates, right-click the template that you identified, and then click Edit Template Properties.

    –Or–

    If you want to modify a specific file screen and not the template that it derives from, right-click the file screen, and then click Edit File Screen Properties.

  4. To change the text and the variables in an event notification:
    1. To change the text in the event log message, on the Event Log tab, edit the text under Log entry.
    2. To add a variable, place the cursor where you want the variable to be added to the text, select the variable from the drop-down list, and then click Insert Variable. If you want to remove a variable, delete it from the text.
    3. Click OK to save the new event notification text.

    Note: If you want to remove the event notification instead of changing it, on the Event Log tab, clear the Send warning to event log check box.

  5. Click OK to save the changes to the file screen template or to the specific file screen.
  6. If you modified a file screen template, the Update File Screens Derived from Template dialog box will open. Select whether to apply the changes to all file screens that derive from the template, or only to those that still match the original template, and click OK.

Verify

To verify that file screen enforcement is working properly, try to save an unauthorized file in a folder or volume that is screened by File Server Resource Manager (FSRM).

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To see the list of configured file screens and the type of files that they block:

  1. Open File Server Resource Manager. Click Start, point to All Programs, click Administrative Tools, and then click File Server Resource Manager.
  2. In the console tree, expand the File Screening Management node, and then click File Screens. The results pane will show all configured file screens, and the details for each:
    • The File Screen Path column shows the volume or folder where the file screen is enforced. Use this information to determine a volume or folder where you can try to save the unauthorized file.
    • The Screening Type column shows the type of file screen. If available, select an active file screen for your verification.
    • The File Groups column shows the file groups defined for the file screen. If you want to see more details about each file group, on the console tree, click File Groups.

Related Management Information

File Screen Enforcement

File Services

Related:

Event ID 8196 — Terminal Services Per User Client Access License Tracking and Reporting

Event ID 8196 — Terminal Services Per User Client Access License Tracking and Reporting

Updated: January 5, 2012

Applies To: Windows Server 2008

In Windows Server 2008, you can use the TS Licensing Manager tool to create (generate) reports to track the Terminal Services Per User client access licenses (TS Per User CALs) that have been issued by a Terminal Services license server. TS Per User CAL tracking and reporting is supported only in domain-joined scenarios because the information about the TS Per User CAL that has been issued to a user is stored as part of the user account in Active Directory Domain Services (AD DS).

For TS Per User CAL tracking and reporting to work, the computer account for the license server must be a member of the Terminal Server License Servers group in AD DS. If the license server is installed on a domain controller, the Network Service account must also be a member of the Terminal Server License Servers group.

Event Details

Product: Windows Operating System
ID: 8196
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.0
Symbolic Name: TLS_I_TLSARW_ROLE_TSLS_SUCCESS
Message: The computer account for the Terminal Services license server was successfully added to the Terminal Server License Servers group in Active Directory Domain Services during the installation of TS Licensing.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Terminal Services Per User Client Access License Tracking and Reporting

Terminal Services

Related:

Event ID 8195 — Terminal Services Per User Client Access License Tracking and Reporting

Event ID 8195 — Terminal Services Per User Client Access License Tracking and Reporting

Updated: January 5, 2012

Applies To: Windows Server 2008

In Windows Server 2008, you can use the TS Licensing Manager tool to create (generate) reports to track the Terminal Services Per User client access licenses (TS Per User CALs) that have been issued by a Terminal Services license server. TS Per User CAL tracking and reporting is supported only in domain-joined scenarios because the information about the TS Per User CAL that has been issued to a user is stored as part of the user account in Active Directory Domain Services (AD DS).

For TS Per User CAL tracking and reporting to work, the computer account for the license server must be a member of the Terminal Server License Servers group in AD DS. If the license server is installed on a domain controller, the Network Service account must also be a member of the Terminal Server License Servers group.

Event Details

Product: Windows Operating System
ID: 8195
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.0
Symbolic Name: TLS_W_TLSARW_ROLE_TSLS_FAIL
Message: The computer account for the Terminal Services license server could not be added to the Terminal Server License Servers group in Active Directory Domain Services during the installation of TS Licensing. The action failed with Win32 error code %1!s!.

Resolve
Add the license server to the Terminal Server License Servers group and restart the Terminal Services Licensing service

To resolve this issue, do the following:

  • Add the computer account for the license server to the Terminal Server License Servers group in Active Directory Domain Services (AD DS).
  • Restart the Terminal Services Licensing service on the Terminal Services license server.

To perform these tasks, refer to the following sections.

Note:  If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.

Add the computer account for the license server to the Terminal Server License Servers group

You can add the computer account for the license server to the Terminal Server License Servers group in AD DS either by using TS Licensing Manager or by using Active Directory Users and Computers. To perform these tasks, refer to the following sections.

Add the computer account by using TS Licensing Manager

To perform this procedure, you must have membership in the local Administrators group on the license server and membership in the Domain Admins group in AD DS, or you must have been delegated the appropriate authority.

To add the account to the group:

  1. On the license server, open TS Licensing Manager. To open TS Licensing Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, click All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.
  4. In the Configuration dialog box, click Add to Group.

    Note:  If Add to Group does not appear in the Configuration dialog box, the computer account for the license server (and the Network Service account) are already members of the Terminal Server License Servers group and no further action is required.

  5. Click Continue, and then click OK.
  6. Restart the Terminal Services Licensing service on the license server. To restart the Terminal Services Licensing service, see the section titled “Restart the Terminal Services Licensing Service.”

Add the computer account by using Active Directory Users and Computers

To perform this procedure, you must have membership in the Domain Admins group in AD DS, or you must have been delegated the appropriate authority.

To add the account to the group:

  1. Open Active Directory Users and Computers. To open Active Directory Users and Computers, log on to a computer where Active Directory Users and Computers is installed (for example, an AD DS domain controller), click Start, click Run, type dsa.msc, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Locate the Terminal Server License Servers group. By default, the Terminal Server License Servers group is located in the Builtin container.
  4. Right-click Terminal Server License Servers, and then click Properties.
  5. On the Members tab, click Add.
  6. Click Object Types, select the Computers check box, and then click OK.
  7. In the Enter the object name to select box, type the name of the license server that you want to add to the Terminal Server License Servers group. If the license server is installed on a domain controller, add the Network Service account.
  8. Click OK, and then click OK.
  9. Restart the Terminal Services Licensing service on the license server. To restart the Terminal Services Licensing service, see the section titled “Restart the Terminal Services Licensing service.”

Restart the Terminal Services Licensing service

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To start the Terminal Services Licensing service:

  1. Open the Services snap-in on the license server. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, right-click Terminal Services Licensing, and then click Restart.
  4. Confirm that the Status column for the Terminal Services Licensing service now displays Started.

Verify

To verify that TS Per User CAL tracking and reporting is configured and working properly, do the following:

  • Use Review Configuration in TS Licensing Manager.
  • Create a report by using TS Licensing Manager.

To perform these tasks, refer to the following sections.

Use Review Configuration in TS Licensing Manager

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To use Review Configuration:

  1. On the license server, open TS Licensing Manager. To open TS Licensing Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, click All Servers.
  4. In the right pane, in the Configuration column, an entry of OK should appear in the row for the license server.
  5. To review the configuration details of the license server, right-click the license server that you want to review, and then click Review Configuration.
  6. There should not be any error or warning messages related to TS Per User CAL tracking and reporting in the Configuration dialog box.

Create a report by using TS Licensing Manager

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To create a report:

  1. On the license server, open TS Licensing Manager. To open TS Licensing Manager, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Licensing Manager.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, expand All Servers, and then select the license server.
  4. On the Action menu, point to Create Report, and then click Per User CAL Usage.
  5. In the Create Per User CAL Usage Report dialog box, select the scope for the report, and then click Create Report. The report will be created and a message will appear to confirm that the report was successfully created. Click OK to close the message.
  6. In the left pane, expand the node for license server, and then click Reports. The report will be listed in the right pane.
  7. Right-click the report, click Save As, and then specify the file name and location to save the report, and then click Save.
  8. Open the report and ensure that the report contains the appropriate information.

Related Management Information

Terminal Services Per User Client Access License Tracking and Reporting

Terminal Services

Related:

Event ID 12301 — Volume Shadow Copy Service Operations

Event ID 12301 — Volume Shadow Copy Service Operations

Updated: January 27, 2011

Applies To: Windows Server 2008

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.

Event Details

Product: Windows Operating System
ID: 12301
Source: VSS
Version: 6.0
Symbolic Name: VSS_ERROR_WRITER_NOT_RESPONDING
Message: Volume Shadow Copy Service error: Writer %1 did not respond to a GatherWriterStatus call.

Resolve
Use VssAdmin to determine the cause of the error condition and then take appropriate action

To troubleshoot this error condition, you first need to determine what caused it by using the VssAdmin command line tool. After determining the cause of the error condition, follow the steps indicated for each possible cause.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To use VssAdmin to determine the cause of the error condition:

  1. Open an elevated Command Prompt. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type vssadmin list writers, and then press Enter.

The output of this command will tell you that the cause of the error condition is one of the following:

  • If the command does not respond, the Volume Shadow Copy Service (VSS) writer encountered an internal problem which caused it to stop responding to incoming requests. To fix this problem, you should restart the service or process that hosts the writer. If this does not resolve the issue, restart the computer.
  • If the command reports the state of the writer as Retryable error, then the writer encountered a temporary error that can be resolved by retrying the backup. To fix this error, run the backup again. If this does not resolve the issue after one or two attempts, restart the computer.
  • If the command reports the state of the writer as Non-retryable error, then the writer encountered a permanent error that can be resolved by restarting the service or process that hosts the writer. If this does not resolve the issue, restart the computer. If restarting the computer does not resolve the issue, open Event Viewer as described in the “Open Event Viewer and view events related to VSS” section and look for events related to the service or process that hosts the writer, and provide this information to the vendor that is responsible for the writer.
  • If the command fails, event ID 8194 with source VSS will be logged in the Application log. Use Event Viewer to determine if this event has been logged. For more information, see the “Open Event Viewer and view events related to VSS” section. If this event has been logged, save the Event Log information related to event ID 8194, and provide this information to the vendor that is responsible for the writer.

Open Event Viewer and view events related to VSS

To open Event Viewer and view events related to VSS:

  1. If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click Application.
  3. To filter the events so that only events with a Source of VSS are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources drop-down list, select the checkbox for VSS. Select other options as appropriate, and then click OK.
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time heading.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Volume Shadow Copy Service is started:

  1. Click Start, point to Administrative Tools, and then click Services.
  2. In the results pane, double-click Volume Shadow Copy.
  3. In Service status, make sure that the status is Started. If the status is not Started, click Start.
  4. Make sure Startup type is set to Manual.
  5. Click OK.

Related Management Information

Volume Shadow Copy Service Operations

File Services

Related:

Event ID 11166 — DNS Client Registration

Event ID 11166 — DNS Client Registration

Updated: November 13, 2007

Applies To: Windows Server 2008

A computer that is configured to use Dynamic Host Configuration Protocol (DHCP) to obtain IP addresses can automatically register its IP address and Domain Name System (DNS) name with the DNS server that is authoritative for the zone that hosts its domain. This eliminates the need for an administrator to manage host (A or AAAA) resource records for client computers. Problems with automatic registration do not prevent a computer from accessing the network, but they can prevent other network computers from being able to locate the computer.

Event Details

Product: Windows Operating System
ID: 11166
Source: DnsApi
Version: 6.0
Symbolic Name: EVENT_DNSAPI_REGISTRATION_FAILED_SECURITY_PRIMARY_DN
Message: The system failed to register host (A) resource records for the network adapter with these settings:Adapter Name: %1Host Name: %2Primary Domain Suffix: %3DNS server list: %4Sent update to server: %5IP Address(es): %6The system could not register these resource records because of a security-related problem. Possible causes are that your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.You can retry DNS registration of the network adapter and its settings by typing “ipconfig /registerdns” at a command prompt. If the problems persists, contact your network administrator.

Resolve
Retry DNS registration

When your computer is assigned a new network address automatically, it attempts to notify the DNS server of the change of address. A problem occurred when your computer made this attempt. Often, this is a transient condition, although it can indicate a problem with the DNS server. This condition rarely causes problems for your computer unless you share resources such as folders or printers.

Although it is not necessary, you can direct your computer to try the DNS registration again.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To register your computer’s address with the DNS server:

  1. On the DNS client computer, open a command prompt. To open an elevated Command Prompt window, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. At the command prompt, type ipconfig /registerdns, and then press ENTER.

If the problem persists, contact your network administrator and provide the information in the event message. If you are a network administrator, see Troubleshooting Dynamic Updates (http://go.microsoft.com/fwlink/?LinkId=103842) for information about troubleshooting DNS registration.

Verify

Use the ipconfig /registerdns command to register the computer’s network name and address with a DNS server and then check the event log for errors.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To register the computer’s network name and address with a DNS server:

  1. On the DNS client, open a command prompt. To open an elevated Command Prompt window, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type the following command, and then press ENTER:

    ipconfig /registerdns

Wait 15 minutes, and then check the event log to verify that a DNSapi event with an ID in the range 11150 through 11167 was not logged after you ran the command.

Related Management Information

DNS Client Registration

DNS Infrastructure

Related: