Open File Manager
Open File Manager

Knowledgebase

What Ports does Open File Manager Require?

Return to Knowledgebase

For security reasons, many OFM customers today disable NetBIOS protocols in their servers. Windows operating systems implement a network protocol called NetBIOS. By default, Windows machines advertise their existence and their names, domain and usernames without requiring user authentication. A server may not have any public shares, or all shares may be password protected, but the server will still advertise its login name and workgroup name to other parties. The NetBIOS protocol provides name service, datagram service (Mailslot), and browser service etc. The unsecured NetBIOS protocol uses the well-known ports 137, 138 and 139.


The following table is a summary of commonly used ports. You may run "netstat -an" to confirm which ports are open and listening on a particular machine.


Port

Protocol

Network Service

System Service

Service Name

53

TCP

DNS

DNS Server

DNS

67

UDP

DHCP Server

DHCP Server Internet Connection

DHCPServer

67

UDP

DHCP Server

Firewal/Internet Connection Sharing

ShareAccess

135

TCP

RPC

Message Queuing

Msmq

135

TCP

RPC

Remote Procedure Call

RpcSs

135

TCP

RPC

Exchange Server

Not Applicable

137

TCP and UDP

NetBIOS Name Resolution (Name Service)

Computer Browser

Browser

137

TCP and UDP

NetBIOS Name Resolution

Server

LanManServer

137

TCP and UDP

NetBIOS Name Resolution

Windows Internet Name Service

WINS

137

TCP and UDP

NetBIOS Name Resolution

Net Logon

NetLogon

138

UDP

NetBIOS Datagram Service

Computer Browser

Browser

138

UDP

NetBIOS Datagram Service

Messenger

Messenger

138

UDP

NetBIOS Datagram Service

License Logging Service

LicenseService

139

TCP

NetBIOS Session Service (NET USE)

Computer Browser

Browser

139

TCP

NetBIOS Session Service

Server

LanManServer

139

TCP

NetBIOS Session Service

Remote Procedure Call Locator

RpcLocator

139

TCP

NetBIOS Session Service

Performance Logs and Alerts

SysmonLog

445

TCP and UDP

SMB

License Logging Service

LicenseService

445

TCP and UDP

SMB

Server

LanManServer

445

TCP and UDP

SMB

Remote Procedure Call Locator

RpcLocator

OFM 9.0 and Prior Versions

Prior to 9.1, OFM service uses Mailslot and Named pipes for service-to-service communication and license checking. The OFM UI also communicates to the service using Named pipe. Mailslot is a simple mechanism for sending a message from one NetBIOS name to another over UDP. Mailslot messages can be broadcast on a subnet or directed to a remote host. A NetBIOS session over TCP/IP requires NetBIOS-to-IP address name resolution, requiring a client LMHOSTS file entry for each server, or a WINS server to provide this name resolution.


Other Port Requirements

All versions of OFM require SMB (Server Message Block) support. Microsoft SMB provides file and print sharing using TCP/UDP port 445. The SMB protocol is used among other things for file sharing in Windows NT/2000/XP. In Windows NT, it ran on top of NetBT (NetBIOS over TCP/IP), which used ports 137, 138 (UDP) and 139 (TCP). In Windows 2000/XP/2003, Microsoft enhanced SMB to run directly over TCP/IP, without the extra layer of NetBT.


Currently, OFM service maintains its persistent log file (OFMNT.LOG) and TCP/IP port information (OFMNT.ADR) via the OFMLOG$ file share. Without file share support, OFM UI cannot retrieve log file information and the UI cannot open the address file.

 

 

 

 

 

 

 

 

 

Resource Center