Event ID 18 — Core Functionality
Applies To: Windows Server 2008 R2
.jpg)
In order for a BITS peer caching client to download content from BITS peer caching servers, at least one peer server must be available on the network to serve the content. The client must also be able to receive peer server announcements, to discover available servers. A peer server announces itself after it starts. If more servers are needed for its peer list, the client must be able to broadcast a request for peer servers.
Event Details
| Product: | Windows Operating System |
| ID: | 18 |
| Source: | Microsoft-Windows-Bits-Client |
| Version: | 6.1 |
| Symbolic Name: | EVT_REJECT_SERVER |
| Message: | The peer list rejected an incoming server announcement. This event is generated if the request looks invalid, not if the server is merely in a different Windows domain. |
Resolve
Restart the BITS service
To resolve this issue, stop and then restart the BITS service.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To stop and restart the BITS service:
- Open an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as Administrator.
- Type sc stop bits, and then press ENTER.
- Type sc start bits, and then press ENTER.
Verify
To ensure that the peer caching client is enabled:
From an elevated command prompt, type:
bitsadmin /PEERCACHING /GETCONFIGURATIONFLAGS
Confirm that the output includes:
Enable download from peers: true