Port 6407 BOE-RESSSVR1
Port 6407 is the IANA-assigned boe-resssvr1 port for Business Objects Enterprise internal server (unspecified).
What is port 6407 used for?
Port 6407 is assigned to boe-resssvr1 and uses unspecified. The IANA registry describes the service as “Business Objects Enterprise internal server”. 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. The registry does not name a transport protocol, so the commands cover TCP and UDP as a fallback. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 6407 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.
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [SAP_2].
Check and block port 6407
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 -tulpn 'sport = :6407'Check on Windows
Get-NetTCPConnection -LocalPort 6407 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 6407 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 6407Block with iptables
sudo iptables -A INPUT -p tcp --dport 6407 -j DROP
sudo iptables -A INPUT -p udp --dport 6407 -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. The registry does not name a transport protocol, so the commands cover TCP and UDP as a safe default.
Is port 6407 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 6407 is usually used
Most traffic on port 6407 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Application backends and supporting services that use a fixed registered number.
- Containers or local stacks that publish the port on the host.
- Firewall and exposure reviews before the service goes to production.
Confirm the local listener
The registry does not name a transport protocol, so this lists both TCP and UDP sockets bound to port 6407. Run it on the host that runs the service.
sudo ss -tulpn 'sport = :6407'Common problems with port 6407
No reply from the service
Because UDP has no handshake, a missing reply can mean the service is idle, the packet was dropped, or the client sent it to the wrong interface. Check the listener locally before blaming the network.
Port already in use
Find the process holding the port with sudo ss -ulpn 'sport = :6407' or sudo lsof -i :6407. 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 6407 at a glance
| Port number | 6407 |
|---|---|
| Service name | boe-resssvr1 |
| Transport protocol | unspecified |
| Category | Application services |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [SAP_2] |
| Registry description | Business Objects Enterprise internal server |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 6407 used for?
Port 6407 (BOE-RESSSVR1) uses unspecified. Business Objects Enterprise internal server.
How do I check if port 6407 is open?
On Linux run `sudo ss -tulpn 'sport = :6407'`. On Windows run `Get-NetTCPConnection -LocalPort 6407 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 6407 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 6407; empty output usually means nothing is bound to it.
How do I block port 6407?
With UFW run `sudo ufw deny 6407`. With iptables run `sudo iptables -A INPUT -p tcp --dport 6407 -j DROP` and `sudo iptables -A INPUT -p udp --dport 6407 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 6407 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 6406 · boe-processsvrBusiness Objects Enterprise internal server
- Port 6408 · boe-resssvr2Business Objects Enterprise internal server
- Port 6405 · boe-pagesvrBusiness Objects Enterprise internal server
- Port 6409 · boe-resssvr3Business Objects Enterprise internal server
- Port 6404 · boe-filesvrBusiness Objects Enterprise internal server
- Port 6410 · boe-resssvr4Business Objects Enterprise internal server
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy