Article ID: 891759 - Last Review: January 27, 2005 - Revision: 1.0

Network ports and protocols that are used by services in Windows Services for UNIX 3.5

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

INTRODUCTION

This article lists the network ports and protocols that are used by services on a computer that is running Microsoft Windows Services for UNIX 3.5.

A variety of network ports and protocols are used to communicate with client computers and with other server systems over the network. Dedicated firewalls, host-based firewalls, and Internet Protocol security (IPSec) filters are other important components that are required to help secure your network. However, if these technologies are configured to block ports and protocols that a specific server uses, that server will no longer respond to client requests.

This article contains a table that lists the ports and the protocols that each service requires for correct operation. Use the table to help you identify the ports and the protocols that a particular service uses.

MORE INFORMATION

The following table lists the name of the service, the ports and protocols that are used by the service, the alias of the service, and the comment line for the service.
Collapse this tableExpand this table
Service namePort numberProtocolsComponentComment
echo7TCP, UDPInterix inetidBy default, this service is disabled.
discard9TCP, UDPInterix inetidBy default, this service is disabled.
daytime13TCP, UDPInterix inetidBy default, this service is disabled.
chargen19TCPInterix inetidBy default, this service is disabled.
ftp-data20TCP Interix in.ftpdBy default, this service is disabled.
ftp21TCPInterix in.ftpdBy default, this service is disabled.
telnet23TCPInterix telnetd
Telnet server		By default, the Interix version of this service is disabled.
smtp25TCPInterix sendmailBy default, this service is disabled.
time37TCP, UDPInterix inetdBy default, this service is disabled.
tftp69UDPInterix in.tftpdBy default, this service is disabled.
finger79TCPInterix fingerdBy default, this service is disabled.
pop2109TCPInterix popperBy default, this service is disabled.
pop3110TCPInterix popperBy default, this service is disabled.
sunrpc111TCP, UDPServer for NFS
User Name Mapping		By default, this service is enabled.
exec512TCPInterix in.rexecd By default, this service is disabled.
login513TCPInterix in.rlogind By default, this service is disabled.
cmd514TCPInterix in.rshd, Remote Shell Service By default, Interix rshd is disabled.
syslog514UDPInterix syslogd By default, this service is disabled.
talk517UDPInterix in.ntalkd By default, this service is disabled.
ntalk518UDPInterix in.ntalkd By default, this service is disabled.
nfsd2049TCP, UDPServer for NFSBy default, this service is enabled.
Additionally, Windows Services for UNIX 3.5 can use other ports. For example, the following table lists the Network File System (NFS)-related services that register with the Open Network Computing (ONC) Remote Procedure Call (RPC) service:
Collapse this tableExpand this table
Service name
mapsvcUser Name Mapping service
mountdNFS mount daemon
nlockmgrNFS lock manager
statusNetwork status monitor
The four services that are listed in the table listen for both Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) traffic and do not use designated ports. Instead, the services use a port that is available at that particular time and register the port with the Portmapper service. For example, when you run the rpcinfo - p command, you receive the following output:
program  version  protocol   port
----------------------------------------------
100000       2      udp      111    portmapper
100000       2      tcp      111    portmapper
351455       1      tcp      844    mapsvc
351455       1      udp      845    mapsvc
351455       2      tcp      846    mapsvc
351455       2      udp      847    mapsvc
100005       1      udp     1048    mountd
100005       2      udp     1048    mountd
100005       3      udp     1048    mountd
100005       1      tcp     1048    mountd
100005       2      tcp     1048    mountd
100005       3      tcp     1048    mountd
100021       1      udp     1047    nlockmgr
100021       2      udp     1047    nlockmgr
100021       3      udp     1047    nlockmgr
100021       4      udp     1047    nlockmgr
100021       1      tcp     1047    nlockmgr
100021       2      tcp     1047    nlockmgr
100021       3      tcp     1047    nlockmgr
100021       4      tcp     1047    nlockmgr
100024       1      udp     1039    status
100024       1      tcp     1039    status
100003       2      udp     2049    nfs
100003       3      udp     2049    nfs
100003       2      tcp     2049    nfs
100003       3      tcp     2049    nfs
In this example, only the Portmapper service and the NFS service use standard ports.

Additional notes:
  • Custom Interix applications and third-party Interix applications may bind to additional ports.
  • If you add a "camp-" prefix to the name of the service in the /etc/inetd.conf file, Interix determines the port that the service uses. However, Interix does not the start the service when a request is made. By adding the prefix, you disable the service, and you restrict other applications from using that port.

    Note Do not include the quotation marks in the prefix.
For additional information about the network ports and protocols that are used by the Microsoft Windows server system, click the following article number to view the article in the Microsoft Knowledge Base:
832017  (http://support.microsoft.com/kb/832017/ ) Port requirements for the Microsoft Windows server system
For additional information about the ports that must be open for a Windows Services for UNIX product to work with Microsoft Windows XP Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
883105  (http://support.microsoft.com/kb/883105/ ) Description of the ports that have to be open for a Windows Services for UNIX product to work correctly
APPLIES TO
  • Microsoft Windows Services for UNIX 3.5
Back to the top
Keywords: 
kbinfo kbtshoot KB891759