Port 6602 WSSCOMFRMWK
Port 6602 is the IANA-assigned wsscomfrmwk port for Windows WSS Communication Framework (TCP).
What is port 6602 used for?
Port 6602 is assigned to wsscomfrmwk and uses TCP. The IANA registry describes the service as “Windows WSS Communication Framework”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach wsscomfrmwk connects to port 6602. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 6602 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all Windows networking ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Rong_Yu].
Check and block port 6602
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :6602'Check on Windows
Get-NetTCPConnection -LocalPort 6602 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 6602/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 6602 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 6602 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 6602 is usually used
Most traffic on port 6602 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Windows file sharing, printing and domain services inside a LAN.
- Admin tools enumerating shares, printers or RPC endpoints.
- Incident response checking whether lateral-movement ports are reachable.
Enumerate shares
Run this only from a trusted management host; SMB should never be reachable directly from the internet.
smbclient -L //fileserver -p 6602 -N
Common problems with port 6602
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 6602. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :6602' or sudo lsof -i :6602. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 6602 at a glance
| Port number | 6602 |
|---|---|
| Service name | wsscomfrmwk |
| Transport protocol | TCP |
| Category | Windows networking |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Rong_Yu] |
| Registry description | Windows WSS Communication Framework |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 6602 used for?
Port 6602 (WSSCOMFRMWK) uses TCP. Windows WSS Communication Framework.
How do I check if port 6602 is open?
On Linux run `sudo ss -tlpn 'sport = :6602'`. On Windows run `Get-NetTCPConnection -LocalPort 6602 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 6602; empty output usually means nothing is bound to it.
How do I block port 6602?
With UFW run `sudo ufw deny 6602/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 6602 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 6602 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
- Port 6601 · mstmg-sstpMicrosoft Threat Management Gateway SSTP
- Port 6627 · nexgenAllied Electronics NeXGen
- Port 5445 · smbdirectServer Message Block over Remote Direct Memory Access
- Port 31029 · yawnYaWN - Yet Another Windows Notifier
- Port 5363 · net-projectionWindows Network Projection
- Port 47001 · winrmWindows Remote Management Service
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy