The core problem: the connection only works on one machine
Many teams already have one Windows host connected to the network they need through SoftEther / PacketiX / a company VPN client. But that connection only works on this machine — the virtual adapter created by the client belongs to the current machine only.
For 投放、运营、客服、数据分析和财务对账工位 to use the same network, common approaches are:
- Install the same client on every machine and log in on each — double the licensing and maintenance cost
- Share one account — security, concurrency limits, and IP pollution problems
- Keep using inconsistent setups — environment inconsistency is exactly what platform risk control looks at
What NetConfiger does: inherit the network and distribute it to your LAN
NetConfiger runs on the Windows host that already has the network connected. It does two things:
- Inherit: uses the host's connected network (SoftEther / PacketiX / company VPN / any virtual-adapter connection) as the exit
- Distribute: opens HTTP / SOCKS5 proxy ports on the host so other LAN devices can use the same network through those ports
In essence: your software is a proxy
NetConfiger opens a proxy port on the host (HTTP 8080 / SOCKS5 1080 by default). Downstream devices point their proxy settings to the host's LAN IP and port, and their traffic exits through the host's network.
Key point: downstream devices need no VPN client, no account, and no network configuration.
Step-by-step
Step 1: Prepare the host
- Connect your client (SoftEther / PacketiX / company VPN) on the Windows host as usual
- Confirm it is connected: open Network Connections and verify the virtual adapter is connected
- Note the host's LAN IP (e.g. 192.168.1.100) — this is what downstream devices will use
Step 2: Start NetConfiger
- Run NetConfiger as administrator
- Open the Network Distribution tab and enable HTTP and/or SOCKS5
- Set the listen address to the host LAN IP (or all interfaces), keep the default ports
- Click Start Service — the host now serves the network to the LAN
- Confirm Windows Firewall allows the port when prompted (the software configures this automatically)
Step 3: Connect downstream devices
- On other PCs / VMs / browser workstations, open system proxy settings
- Enter: Address = host LAN IP (e.g. 192.168.1.100), Port = 8080 (HTTP) or 1080 (SOCKS5)
- Save, then open a browser and check your IP
- Confirm the IP matches the host's exit — if it does, you are connected
Verification checklist
- Browser IP matches the host's exit
- DNS resolution is consistent with the host (no DNS leak)
- IPv6 is disabled (prevent IPv6 from bypassing the proxy)
- AdsPower / BitBrowser environments use the same exit
- Multiple devices connected simultaneously keep the same IP
Why this beats connecting every device separately
| Comparison | Every device connects | NetConfiger distribution |
|---|---|---|
| Client install | Every machine | Host only |
| Account | Every machine needs access | One host connection |
| Environment consistency | Each machine may differ | All devices share one exit |
| Adding a device | Full reinstall | Just point to the proxy |
| Troubleshooting | Check each machine | Check the host only |
FAQ
Do downstream devices need NetConfiger installed?
No. NetConfiger runs on the host only. Downstream devices point their proxy to the host.
Which networks are supported?
Any connection that creates a virtual adapter on Windows: SoftEther, PacketiX, OpenVPN, WireGuard, L2TP/IPsec, company AnyConnect / GlobalProtect, and similar.
Does the host need to stay on?
Yes. The host is the network exit; downstream devices lose access when it is off. Keep the host online.
Usage boundary: distribute only a network you own or are authorized to use, and only to devices within your organization.
Key points
- Ad operators review campaigns while operations teams maintain products and orders
- Support, analytics, and finance machines can follow the same office entry
- New staff PCs, temporary machines, and VMs can reuse the documented workflow
- Admin records can connect plan, device count, machine code, and license-file status
- Support starts with host status, LAN reachability, port, and client configuration