Setting up card sharing on Windows: step-by-step guide 2026

Card sharing allows multiple satellite receivers to use one paid smart card simultaneously over a network. To work with card sharing on a Windows computer, a special client is needed that connects to the server and transmits decryption data to the receiver. Below is a detailed breakdown of the entire process: from choosing the program to the final signal check.

What is card sharing and how does it work on Windows

Card sharing is based on protocolsCCcam, Newcamd, or CS378x. The server reads the Control Word (CW) — the decryption key — from the physical smart card and distributes it to clients over the network every few seconds. The Windows client receives this data and transmits it to the receiver via a local network or USB connection.

Three components are needed for the scheme to work:

• Card sharing server with an active subscription (CCcam server, OScam server)
• Client software on Windows (CCcam Emulator, OScam for Windows, Cccam2Prio)
• Satellite receiver with CS support or computer DVB card

Choosing client software

CCcam Emulator for Windows

CCcam Emulator is one of the most common clients. It works on Windows 10 and Windows 11 without the need to install additional dependencies. The emulator supports the CCcam 2.3.x protocol and allows simultaneous connections to multiple servers with prioritization by latency (hop-count).

Main parameters of the configuration fileCCcam.cfg:

The lineC: specifies the connection to the server: address, port, login, password. The parameterNEWCAMD LISTEN PORT opens a local port to which the receiver will connect via the local network.

OScam on Windows

OScam is a more flexible tool with a web management interface on port 8888. It supports the CCcam, Newcamd, CS378x, and Radegast protocols simultaneously. To run on Windows, the buildoscam-svn-windows.exe is used, which does not require the installation of Cygwin or WSL.

The minimum OScam configuration consists of three files:

• oscam.conf — global settings (logging, web interface)
• oscam.server — description of source servers
• oscam.user — list of local clients (receivers)

Installation and initial setup

Step 1: Preparing the Windows system

Before installation, it is necessary to disable the Windows firewall for the used ports or create exception rules. For CCcam Emulator, typical ports are 12000 (outgoing to the server) and 10000 (incoming from the receiver). Ports can be opened through:

Control Panel → System and Security → Windows Defender Firewall → Advanced settings → Inbound rules → Create rule

Select the type "Port", protocol TCP, specify the desired port number, allow connection for all network profiles.

Step 2: Downloading and unpacking the client

CCcam Emulator is distributed as a ZIP archive without an installer. After unpacking, the folder should contain:

• CCcamEmu.exe — executable file
• CCcam.cfg — configuration file (if missing, it is created manually)
• CCcam.providers — optional list of providers

It is recommended to place the folder in a path without Cyrillic, for exampleC:\CardSharing\CCcam\, to avoid path reading errors in the console.

Step 3: Editing the configuration file

The fileCCcam.cfg opens in any text editor (Notepad++, VS Code). You need to enter the data received from the card sharing provider:

The valueLOG LEVEL = 3 records detailed debug messages — useful during initial setup. After stable operation, the level can be reduced to 1.

Connecting the receiver to the Windows client

Via the Newcamd protocol

Most modern receivers (Dreambox, Vu+, Formuler, Gigablue) support the Newcamd protocol. In the receiver settings, you need to specify:

• Host: IP address of the computer with Windows (for example,192.168.1.100)
• Port: 10000 (corresponds toNEWCAMD LISTEN PORT in the config)
• Login and password: any, if authentication is not specified in CCcam.cfg
• DES key: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 (default standard)

On Vu+ receivers, the setup is done through the Softcam Manager plugin:Menu → Plugins → Softcam Manager → Newcamd → Add server.

Through a DVB card on the computer

When using a DVB-S2 card (for example, TBS 6903, Hauppauge WinTV-Starburst) instead of an external receiver, the card sharing client integrates with the TV viewing application. The MediaPortal and DVBViewer programs support direct connection to OScam via the CS378x protocol on port 9999.

Configuration exampleoscam.conf for DVBViewer:

Diagnostics and troubleshooting common issues

Client does not connect to the server

First, check the logcccam.log. A line likeConnection to cs.myprovider.net:12000 FAILED indicates a network issue or incorrect data. The order of checks:

1. Executeping cs.myprovider.net in the command line — if packets do not reach, the problem is with DNS or routing
2. Check port availability:telnet cs.myprovider.net 12000 — a blank screen without an error means a successful connection
3. Ensure that the antivirus (Windows Defender, Kaspersky) is not blocking the processCCcamEmu.exe

Receiver does not decode channels

If the connection to the server is established but the channels remain encrypted, check the CAID compliance. Each satellite TV provider uses its own encryption system with a unique identifier:

• Viasat / TV Vlaanderen — CAID0500
• Sky Deutschland / Sky Italia — CAID0919
• Canal+ — CAID0500,0604
• Biss — CAID2600

In the OScam log file, the lineno matching entry found for CAID 0919 means that the server does not provide keys for this system. It is necessary to choose another server or plan that covers the required package.

Delays and freezes in the picture

Periodic freezes lasting 1–2 seconds are a sign of high latency between the client and the server. The optimal ping to the card sharing server should not exceed 80 ms. If the delay is higher, you can:

• Connect an additional server with lower latency inCCcam.cfg as the second lineC:
• Enable parameterPREFER SIDS FROM CACHE = yes for caching Control Word
• Switch to CS378x protocol instead of Newcamd — it has less overhead

Auto-start the card sharing client when Windows starts

For continuous operation without manual start, the client is registered as a Windows service using theNSSM (Non-Sucking Service Manager).

Installation via command line with administrator rights:

After this, the client starts automatically when the computer is turned on, even without user login. The service status is checked with the commandsc query CCcamService.

Security when using card sharing

Data transmission between the client and the CCcam server occurs without encryption. To protect traffic from interception, it is recommended to use a VPN tunnel (WireGuard, OpenVPN) between the client and the server. WireGuard on Windows installs in a few minutes and adds minimal latency (usually less than 1 ms in the provider's local network).

It is also advisable not to use the same passwords for multiple card sharing servers — in case one account is compromised, the others will remain protected.

Functionality check and monitoring

OScam provides a web interface athttp://127.0.0.1:8888, where real-time statistics are displayed: the number of successful and failed decryption requests, a list of connected clients, response latency from each server. This allows for quick identification of unstable servers and their replacement.

CCcam Emulator does not have a built-in web interface, but the real-time log can be read with the command:

This PowerShell command outputs the last 50 lines of the log and updates as new entries are added — similar totail -f in Linux.

Final configuration check

The configuration is considered complete when the following conditions are met:

1. The client log contains the linelogin ok orconnection established
2. The receiver or DVB application shows encrypted channels in clear view
3. Switching between channels takes no longer than 2–3 seconds
4. The Windows service automatically starts after the computer is rebooted

If all steps are followed, card sharing on Windows operates stably without constant user involvement. The choice between CCcam Emulator and OScam is determined by requirements: the former is easier to set up, while the latter provides more control over protocols and connection statistics.