기업에서 방화벽을 사용하다 보면, 작게 보면 윈도우 방화벽을 사용하더라도 특정한 프로그램(서비스)을 위해서 포트를 개방해야 할 경우가 종종 있습니다.

아래 제공하는 자료는 윈도우의 서비스 별로 사용하는 포트를 정리한 문서입니다.

표 축소표 확대
포트 프로토콜 응용 프로그램 프로토콜 시스템 서비스 이름
n/a GRE GRE(IP 프로토콜 47) 라우팅 및 원격 액세스
n/a ESP IPsec ESP(IP 프로토콜 50) 라우팅 및 원격 액세스
n/a AH IPsec AH(IP 프로토콜 51) 라우팅 및 원격 액세스
7 TCP Echo 단순 TCP/IP 서비스
7 UDP Echo 단순 TCP/IP 서비스
9 TCP Discard 단순 TCP/IP 서비스
9 UDP Discard 단순 TCP/IP 서비스
13 TCP Daytime 단순 TCP/IP 서비스
13 UDP Daytime 단순 TCP/IP 서비스
17 TCP Quotd 단순 TCP/IP 서비스
17 UDP Quotd 단순 TCP/IP 서비스
19 TCP Chargen 단순 TCP/IP 서비스
19 UDP Chargen 단순 TCP/IP 서비스
20 TCP FTP 기본 데이터 FTP 게시 서비스
21 TCP FTP 제어 FTP 게시 서비스
21 TCP FTP 제어 응용 프로그램 계층 게이트웨이 서비스
23 TCP 텔넷 텔넷
25 TCP SMTP Simple Mail Transfer Protocol
25 TCP SMTP Exchange Server
42 TCP WINS 복제 Windows Internet Name Service
42 UDP WINS 복제 Windows Internet Name Service
53 TCP DNS DNS 서버
53 UDP DNS DNS 서버
53 TCP DNS 인터넷 연결 방화벽/인터넷 연결 공유
53 UDP DNS 인터넷 연결 방화벽/인터넷 연결 공유
67 UDP DHCP 서버 DHCP 서버
67 UDP DHCP 서버 인터넷 연결 방화벽/인터넷 연결 공유
69 UDP TFTP Trivial FTP 데몬 서비스
80 TCP HTTP Windows Media 서비스
80 TCP HTTP World Wide Web 게시 서비스
80 TCP HTTP SharePoint Portal Server
88 TCP Kerberos Kerberos 키 배포 센터
88 UDP Kerberos Kerberos 키 배포 센터
102 TCP X.400 Microsoft Exchange MTA 스택
110 TCP POP3 Microsoft POP3 서비스
110 TCP POP3 Exchange Server
119 TCP NNTP Network News Transfer Protocol
123 UDP NTP Windows 시간
123 UDP SNTP Windows 시간
135 TCP RPC 메시지 대기열
135 TCP RPC 원격 프로시저 호출
135 TCP RPC Exchange Server
135 TCP RPC 인증서 서비스
135 TCP RPC 클러스터 서비스
135 TCP RPC 분산 파일 시스템
135 TCP RPC 분산 링크 추적
135 TCP RPC Distributed Transaction Coordinator
135 TCP RPC 분산 파일 복제 서비스
135 TCP RPC 팩스 서비스
135 TCP RPC Microsoft Exchange Server
135 TCP RPC 파일 복제 서비스
135 TCP RPC 그룹 정책
135 TCP RPC 로컬 보안 기관
135 TCP RPC 원격 저장소 알림
135 TCP RPC 원격 저장소 서버
135 TCP RPC Systems Management Server 2.0
135 TCP RPC 터미널 서비스 라이선스
135 TCP RPC 터미널 서비스 세션 디렉터리
137 UDP NetBIOS 이름 확인 컴퓨터 브라우저
137 UDP NetBIOS 이름 확인 서버
137 UDP NetBIOS 이름 확인 Windows Internet Name Service
137 UDP NetBIOS 이름 확인 Net Logon
137 UDP NetBIOS 이름 확인 Systems Management Server 2.0
138 UDP NetBIOS 데이터그램 서비스 컴퓨터 브라우저
138 UDP NetBIOS 데이터그램 서비스 메신저
138 UDP NetBIOS 데이터그램 서비스 서버
138 UDP NetBIOS 데이터그램 서비스 Net Logon
138 UDP NetBIOS 데이터그램 서비스 분산 파일 시스템
138 UDP NetBIOS 데이터그램 서비스 Systems Management Server 2.0
138 UDP NetBIOS 데이터그램 서비스 라이선스 로깅 서비스
139 TCP NetBIOS 세션 서비스 컴퓨터 브라우저
139 TCP NetBIOS 세션 서비스 팩스 서비스
139 TCP NetBIOS 세션 서비스 성능 로그 및 경고
139 TCP NetBIOS 세션 서비스 인쇄 스풀러
139 TCP NetBIOS 세션 서비스 서버
139 TCP NetBIOS 세션 서비스 Net Logon
139 TCP NetBIOS 세션 서비스 원격 프로시저 호출 로케이터
139 TCP NetBIOS 세션 서비스 분산 파일 시스템
139 TCP NetBIOS 세션 서비스 Systems Management Server 2.0
139 TCP NetBIOS 세션 서비스 라이선스 로깅 서비스
143 TCP IMAP Exchange Server
161 UDP SNMP SNMP 서비스
162 UDP SNMP 트랩 아웃바운드 SNMP 트랩 서비스
389 TCP LDAP 서버 로컬 보안 기관
389 UDP LDAP 서버 로컬 보안 기관
389 TCP LDAP 서버 분산 파일 시스템
389 UDP LDAP 서버 분산 파일 시스템
443 TCP HTTPS HTTP SSL
443 TCP HTTPS World Wide Web 게시 서비스
443 TCP HTTPS SharePoint Portal Server
443 TCP RPC over HTTPS Exchange Server 2003
445 TCP SMB 팩스 서비스
445 TCP SMB 인쇄 스풀러
445 TCP SMB 서버
445 TCP SMB 원격 프로시저 호출 로케이터
445 TCP SMB 분산 파일 시스템
445 TCP SMB 라이선스 로깅 서비스
445 TCP SMB Net Logon
464 UDP Kerberos Password V5 Kerberos 키 배포 센터
464 TCP Kerberos Password V5 Kerberos 키 배포 센터
500 UDP IPsec ISAKMP 로컬 보안 기관
515 TCP LPD TCP/IP 인쇄 서버
548 TCP Macintosh용 파일 서버 Macintosh용 파일 서버
554 TCP RTSP Windows Media 서비스
563 TCP SSL을 통한 NNTP Network News Transfer Protocol
593 TCP RPC over HTTPS 끝점 매퍼 원격 프로시저 호출
593 TCP RPC over HTTPS Exchange Server
636 TCP LDAP SSL 로컬 보안 기관
636 UDP LDAP SSL 로컬 보안 기관
993 TCP SSL을 통한 IMAP Exchange Server
995 TCP SSL을 통한 POP3 Exchange Server
1067 TCP 설치 부트스트랩 서비스 설치 부트스트랩 프로토콜 서버
1068 TCP 설치 부트스트랩 서비스 설치 부트스트랩 프로토콜 클라이언트
1270 TCP MOM-Encrypted Microsoft Operations Manager 2000
1433 TCP SQL over TCP Microsoft SQL Server
1433 TCP SQL over TCP MSSQL$UDDI
1434 UDP SQL Probe Microsoft SQL Server
1434 UDP SQL Probe MSSQL$UDDI
1645 UDP 레거시 RADIUS 인터넷 인증 서비스
1646 UDP 레거시 RADIUS 인터넷 인증 서비스
1701 UDP L2TP 라우팅 및 원격 액세스
1723 TCP PPTP 라우팅 및 원격 액세스
1755 TCP MMS Windows Media 서비스
1755 UDP MMS Windows Media 서비스
1801 TCP MSMQ 메시지 대기열
1801 UDP MSMQ 메시지 대기열
1812 UDP RADIUS 인증 인터넷 인증 서비스
1813 UDP RADIUS 계정 인터넷 인증 서비스
1900 UDP SSDP SSDP 검색 서비스
2101 TCP MSMQ-DC 메시지 대기열
2103 TCP MSMQ-RPC 메시지 대기열
2105 TCP MSMQ-RPC 메시지 대기열
2107 TCP MSMQ-Mgmt 메시지 대기열
2393 TCP OLAP Services 7.0 SQL Server: 하위 수준 OLAP 클라이언트 지원
2394 TCP OLAP Services 7.0 SQL Server: 하위 수준 OLAP 클라이언트 지원
2460 UDP MS Theater Windows Media 서비스
2535 UDP MADCAP DHCP 서버
2701 TCP SMS 원격 제어(제어) SMS 원격 제어 에이전트
2701 UDP SMS 원격 제어(제어) SMS 원격 제어 에이전트
2702 TCP SMS 원격 제어(데이터) SMS 원격 제어 에이전트
2702 UDP SMS 원격 제어(데이터) SMS 원격 제어 에이전트
2703 TCP SMS 원격 채팅 SMS 원격 제어 에이전트
2703 UPD SMS 원격 채팅 SMS 원격 제어 에이전트
2704 TCP SMS 원격 파일 전송 SMS 원격 제어 에이전트
2704 UDP SMS 원격 파일 전송 SMS 원격 제어 에이전트
2725 TCP SQL Analysis Services SQL Analysis Server
2869 TCP UPNP 범용 플러그 앤 플레이 장치 호스트
2869 TCP SSDP 이벤트 알림 SSDP 검색 서비스
3268 TCP 글로벌 카탈로그 서버 로컬 보안 기관
3269 TCP 글로벌 카탈로그 서버 로컬 보안 기관
3343 UDP 클러스터 서비스 클러스터 서비스
3389 TCP 터미널 서비스 NetMeeting 원격 데스크톱 공유
3389 TCP 터미널 서비스 터미널 서비스
3527 UDP MSMQ-Ping 메시지 대기열
4011 UDP BINL 원격 설치
4500 UDP NAT-T 로컬 보안 기관
5000 TCP SSDP 레거시 이벤트 알림 SSDP 검색 서비스
5004 UDP RTP Windows Media 서비스
5005 UDP RTCP Windows Media 서비스
6001 TCP 정보 저장소 Exchange Server 2003
6002 TCP 디렉터리 조회 Exchange Server 2003
6004 TCP DSProxy/NSPI Exchange Server 2003
42424 TCP ASP.NET 세션 상태 ASP.NET 상태 서비스
51515 TCP MOM-Clear Microsoft Operations Manager 2000
1024-65535 TCP RPC 임의로 할당된 상위 TCP 포트

보다 자세한 사항은  http://support.microsoft.com/kb/832017 을 참고하십시오. 이 문서에는 윈도우 뿐만 아니라 SQL Server와 같이 자주 사용하는 프로그램에 대한 자료도 포함하고 있습니다.
reTweet
Posted by 문스랩닷컴
blog comments powered by Disqus


    사이게이트(Sygate) 프로그램에서 제공하는 서비스(애플리케이션) 별 포트 사용 현황 목록입니다.

    ISA Server에서 자주 사용하는 서비스가 미리 정의되어 있지만, 그 외의 포트들도 사용해야 할 경우가 있으므로 따로 목록을 정리해 두는 것도 좋습니다.

    <hr>

    ##############################################################################
    # Sybergen Access Server and SyGate Application Rule Configuration File
    # version 1.9
    # Copyright(c) 2000 by Sybergen Networks Inc., all rights reserved.
    #
    ##############################################################################
    #
    # For details, please visit:  http://www.sybergen.com/support/conf_sg.htm
    #                             http://www.sybergen.com/support/applications.htm
    #
    #  Overview:
    #
    # This file defines a list of rules for Sybergen Access Server or SyGate to
    # follow when processing packets.   According to each rule, Sybergen Secure
    # Desktop or SyGate will dynamically create a serias of tunnels to provide
    # the path for packets to flow through.
    #
    #
    #  ----------------------------------------------------------------------------------------
    #  An application rule consists of:
    #
    #  :INIT <Rule Name>
    #  Triggering Transaction
    #  :SUB
    #  Sub-trans-1
    #  Sub-trans-2
    #  ........
    #  :END
    #
    #  Where: <Rule Name> is the name of the application. This could be any name. See example
    #         for detail.
    #         Triggering transaction is the first traffic the application generates
    #
    #  Sub-trans-x and Triggering Transaction could be "Inbound Trans" and "Outbound Trans"
    #  defined below respectively.
    #
    #  ----------------------------------------------------------------------------------------
    #  Inbound Trans Syntax:
    #
    #  Direction  ProtocolType  DestinationPortLow DestinationPortHigh ClientIP ClientPort MaxIdleTime Options

    #  Description:
    #  ===========
    #
    #  Filed Name  Valid Value
    #  ==========  ===========
    #
    #  Direction:   IN
    #  ProtcolType:  "TCP" or "UDP"
    #
    #  DestinationPortHigh: The upper bound of the destination port range
    #  DestinationPortLow:  The lower bound of the destination port range
    #
    # (note: INIT Trans have and only have one port. The current version doesn't support
    # a range of ports on INIT trans. In the other words, PortHigh shall be equal to
    # PortLow on INIT trans.
    #
    #  ClientIp:  This field tells Sybergen Access Server or SyGate where to pass the
    #                       incoming packet with the destination port in the range defined by
    #                       DestinationPortHigh and DestinationPortLow.
    #                      
    #                       This field has to be set to 0.0.0.0 for Sub-trans-x.
    #                       For Triggering Transaction, this field must be set to the IP
    #                       of one of the clients.
    #
    #  ClientPort:         This field tells Sybergen Access Server or SyGate which port of the
    #                       ClientIp to send the incoming packet with the destination port in
    #                       the range defined by DestinationPortHigh and DestinationPortLow.
    #
    #                       If this value is 0, the packet will be send to the port same
    #                       as the destination port of the incoming packet.
    #    If this value is not zero, the packet will be sent to the defined
    #                       port instead of the original destination port. By doing this, we
    #                       can redirect the packets sent to
    #    port 8080 of Sybergen Access Server or SyGate PC to port 80 of
    #                       Sybergen Access Server or SyGate client by using
    #                       following line:
    #
    #                       IN TCP 8080 8080 192.168.0.2 80 0 -
    #
    #
    #  MaxIdleTime:  This field tells Sybergen Access Server or SyGate to close the tunnel
    #                       after certain idle milliseconds.
    #
    #                       Set to 0 for Sybergen Access Server or SyGate to use the default
    #                       idle timeout value. 
    #                     
    #
    #  Options:    
    #   - ----- None
    #
    #   M ----- This value tells Sybergen Access Server or SyGate
    #                             to close all Sub-tunnels if the triggering connection no
    #                             longer exists due to either timeout or user application disconnect,
    #                             etc.
    #     This option is only valid in Triggering Transaction.
    #
    #   H ----- H.323 specfic rule. Sybergen Access Server or
    #                             SyGate will process the packets according to H.323 protocol.
    #                             Users should not use this option to define new rules.
    #
    #   A ----- This option tells Sybergen Access Server or SyGate
    #                             to pass packets from any remote hosts to specific port defined
    #                             in the rule. If this option is not specified, only the packets
    #                             from the remote host that the Triggering Transaction visited
    #                             can be passed to the ClientPort of the triggering client. See
    #                             "DirectPlay" rule for more details.
    #
    #   D ----- This option can only be used in Sub-Trans-x. It tells
    #                             Sybergen Access Server or SyGate to keep creating tunnels for
    #                             each connection between the triggering Sybergen Access Server
    #                             or SyGate client and remote hosts. Without this option, only one
    #                             tunnel can be created for each Sub-Trans-x rule. See "DirectPlay"
    #                             rule for more details.
    #
    #  ----------------------------------------------------------------------------------------
    #
    #  Outbound Trans Syntax:
    #
    #  Direction  ProtocolType  DestinationPortLow DestinationPortHigh ClientIp MaxIdleTime Options
    #
    #  Description:
    #  ===========
    #
    #  Direction:   OUT
    #
    #  ProtcolType:  "TCP" or "UDP"
    #
    #  DestinationPortHigh: The upper bound of the destination port range
    #  DestinationPortLow:  The lower bound of the destination port range
    #
    # (note: INIT Trans have and only have one port. The current version doesn't support
    # a range of ports on INIT trans. In the other words, PortHigh shall be equal to
    # PortLow on INIT trans.
    #
    #  ClientIp:  This field tells Sybergen Access Server or SyGate which client
    #                       can trigger the rule.  In Trigger Tansaction, 0.0.0.0 means any
    #                       client can trigger.   In Sub-Trans-x, ClietnIP has to be 0.0.0.0
    #
    #  MaxIdleTime:  This field tells Sybergen Access Server or SyGate to close the
    #                       tunnel after certain idle milliseconds.
    #
    #                       Set to 0 for Sybergen Access Server or SyGate to use the default
    #                       idle timeout value. 
    #                     
    #  Options:    
    #   - ----- None
    #
    #   M ----- This value tells Sybergen Access Server or SyGate
    #                             to close all Sub-tunnels if the triggering connection no longer
    #                             exists due to either timeout or user application disconnect, etc.
    #     This option is only valid in Triggering Transaction.
    #
    #   R ----- This option tells Sybergen Access Server or SyGate
    #                             to use a different source port to send the packet. See
    #                             "DirectPlay" rule for more details.
    #    
    #   H ----- H.323 specfic rule. Sybergen Access Server or SyGate
    #                             will process the packets according to H.323 protocol. Users
    #                             should not use this option to define new rules.
    #
    #   F ----- FTP activity mode specfic. Users should not use this
    #                             option to define new rules.
    #
    #   I ----- IRC DCC mode specifc. Users should not use this option
    #                             to define new rules.
    #
    #   D ----- This option can only be used in Sub-Trans-x. It tells
    #                             Sybergen Access Server or SyGate keep creating tunnels for each
    #                             connection between the triggering Sybergen Access Server or
    #                             SyGate client and remote hosts. Without this option, only one
    #                             tunnel can be created for each Sub-Trans-x rule. See "DirectPlay"
    #                             rule for more details.
    #
    # Note: 1)  After making any changes to this file, you MUST stop and restart the
    #     Sybergen Access Server or SyGate service for your changes
    #                               to be in effect. 
    #  2) Un-installing or re-installing Sybergen products may remove or update
    #                               this file.
    #    Please save a copy of any change you made in this file.
    #############################################################################
    #
    # TROUBLESHOOTING
    #
    #
    # For the apprule to work, there are certain way to check for error.
    # Example:
    #
    # #
    # # :INIT "Our FTP server"
    # # IN TCP 21 21 192.168.0.2 0 86400000 -
    # # :SUB
    # # :END
    # #
    #
    # 1) No "#" sign and blank space in front of this rule.
    # 2) No error initialing the previous rule
    #
    # :INIT "Our FTP server"
    # IN TCP 21 21 192.168.0.2 0 86400000 -
    # :SUB
    # :END
    #
    # 3) Check the log file in the Sybergen Access Server or SyGate Manager under
    #               troubleshooting to see if the rule is being properly executed.
    #
    #
    #############################################################################


    ##### SYSTEM DEFINITION ##################################################

    # FTP Active mode
    :INIT "FTP Active mode"
    OUT TCP 21 21 0.0.0.0 86400000 MRF
    :SUB
    :END

    # IRC DCC. The IRC port is usually 6660-6670, 7000, 8888, or 9999
    # If you are using a different port number just change one of
    # these apprules to the port number you are using.
    :INIT "mIRC port 6660"
    OUT TCP 6660 6660 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6661"
    OUT TCP 6661 6661 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6662"
    OUT TCP 6662 6662 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6663"
    OUT TCP 6663 6663 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6664"
    OUT TCP 6664 6664 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6665"
    OUT TCP 6665 6665 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6666"
    OUT TCP 6666 6666 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6667"
    OUT TCP 6667 6667 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6668"
    OUT TCP 6668 6668 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6669"
    OUT TCP 6669 6669 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 6670"
    OUT TCP 6670 6670 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 7000"
    OUT TCP 7000 7000 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 8888"
    OUT TCP 8888 8888 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC port 9999"
    OUT TCP 9999 9999 0.0.0.0 0 MRI
    :SUB
    IN TCP 59 59 0.0.0.0 0 0 -
    IN TCP 113 113 0.0.0.0 0 0 -
    :END

    :INIT "mIRC Chat"
    OUT TCP 100 100 0.0.0.0 0 MRI
    :SUB
    IN TCP 101 101 0.0.0.0 0 0 -
    :END

    :INIT "mIRC Fserve"
    OUT TCP 110 110 0.0.0.0 0 MRI
    :SUB
    IN TCP 111 111 0.0.0.0 0 0 -
    :END

    :INIT "mIRC Send"
    OUT TCP 120 120 0.0.0.0 0 MRI
    :SUB
    IN TCP 121 121 0.0.0.0 0 0 -
    :END

    :INIT "mIRC Get"
    OUT TCP 130 130 0.0.0.0 0 MRI
    :SUB
    IN TCP 131 131 0.0.0.0 0 0 -
    OUT TCP 132 132 0.0.0.0 0 -
    :END

    ##### USER DEFINITION ########


    # CU-SeeMe
    #
    # This will allow you to connect to the CU-SeeMe network.
    # You will need to have the H.323 apprule in order to video
    # conference with anyone.
    :INIT "CU-SeeMe"
    OUT UDP 24032 24032 0.0.0.0 0 R
    :SUB
    IN UDP 1414 1414 0.0.0.0 0 0 ADH
    IN UDP 1424 1424 0.0.0.0 0 0 ADH
    IN TCP 1503 1503 0.0.0.0 0 0 AD
    IN TCP 1720 1720 0.0.0.0 0 0 ADH
    IN UDP 1812 1813 0.0.0.0 0 0 AD
    IN TCP 7640 7640 0.0.0.0 0 0 AD
    IN TCP 7642 7642 0.0.0.0 0 0 AD
    IN UDP 7648 7648 0.0.0.0 0 0 AD
    IN TCP 7648 7648 0.0.0.0 0 0 AD
    IN TCP 7649 7649 0.0.0.0 0 0 AD
    IN UDP 24032 24032 0.0.0.0 0 0 AD
    IN UDP 56800 56800 0.0.0.0 0 0 AD
    OUT UDP 1414 1414 0.0.0.0 0 DH
    OUT UDP 1424 1424 0.0.0.0 0 DH
    OUT TCP 1503 1503 0.0.0.0 0 D
    OUT TCP 1720 1720 0.0.0.0 0 DH
    OUT UDP 1812 1813 0.0.0.0 0 D
    OUT TCP 7640 7640 0.0.0.0 0 D
    OUT TCP 7642 7642 0.0.0.0 0 D
    OUT UDP 7648 7648 0.0.0.0 0 D
    OUT TCP 7648 7648 0.0.0.0 0 D
    OUT TCP 7649 7649 0.0.0.0 0 D
    OUT UDP 56800 56800 0.0.0.0 0 D
    :END


    # Internet Phone
    :INIT "Internet Phone 5"
    OUT UDP 22555 22555 0.0.0.0 0 -
    :SUB
    :END


    # Net2Phone
    :INIT "Net2Phone"
    OUT UDP 6801 6801 0.0.0.0 0 R
    :SUB
    IN UDP 1 30000 0.0.0.0 0 0 AD
    IN TCP 1 30000 0.0.0.0 0 0 AD
    :END


    # Calista Incoming
    :INIT "Calista IP Phone"
    OUT TCP 4099 4099 0.0.0.0 R
    :SUB
    IN UDP 3000 3000 0.0.0.0 0 0 D
    :END


    # BAYVPN
    :INIT "BAYVPN"
    OUT UDP 500 500 0.0.0.0 0 -
    :SUB
    :END


    # FW1VPN
    :INIT "FW1VPN"
    OUT UDP 259 259 0.0.0.0 0 -
    :SUB
    :END


    # Shiva VPN
    # (set the mobile option in the Shiva VPN client software
    # to be your public IP address)
    # :INIT "Shiva VPN"
    # OUT UDP 2233 2233 0.0.0.0 0 -
    # :SUB
    # IN UDP 2233 2233 0.0.0.0 0 0 AD
    # :END


    # CITRIX Metaframe
    :INIT "CITRIX Metaframe"
    OUT TCP 1494 1494 0.0.0.0 0 R
    :SUB
    IN TCP 1494 1494 0.0.0.0 0 0 AD
    :END


    # MS Terminal Server
    :INIT "MS Terminal Server"
    OUT TCP 3389 3389 0.0.0.0 0 R
    :SUB
    IN TCP 3389 3389 0.0.0.0 0 0 AD
    :END


    # NTP (Network Time Protocol)
    :INIT "Network Time Protocol"
    OUT UDP 123 123 0.0.0.0 0 R
    :SUB
    IN UDP 123 123 0.0.0.0 0 0 AD
    :END


    # CrisNet
    :INIT "CrisNet"
    OUT TCP 32760 32760 0.0.0.0 0 R
    :SUB
    IN TCP 1367 1367 0.0.0.0 0 0 AD
    IN TCP 32760 32760 0.0.0.0 0 0 AD
    :END


    # RealAudio on Port 7070
    :INIT "RealAudio 7070"
    OUT TCP 7070 7070 0.0.0.0 0 R
    :SUB
    IN UDP 6970 7170 0.0.0.0 0 0 AD
    :END


    # QuickTime 4 Client & RealAudio on Port 554
    :INIT "QuickTime"
    OUT TCP 554 554 0.0.0.0 0 R
    :SUB
    IN UDP 6970 32000 0.0.0.0 0 0 AD
    :END


    # QuickTime 4 Server - Modification tested on 8/9/99
    # (change 192.168.0.2 to correct IP address)
    # :INIT "QuickTime Server"
    # IN TCP 6970 6970 192.168.0.2 0 0 -
    # :SUB
    # IN UDP 6970 7000 0.0.0.0 0 0 AD
    # :END


    # Napster
    :INIT "Napster"
    OUT TCP 6699 6699 0.0.0.0 0 R
    :SUB
    IN TCP 6699 6699 0.0.0.0 0 0 AD
    :END


    # Netop Remote control
    :INIT "Netop Remote control"
    OUT UDP 6502 6502 0.0.0.0 0 R
    :SUB
    IN UDP 6502 6502 0.0.0.0 0 0 AD
    :END

    # Netop Remote control
    # (change 192.168.0.2 to correct IP address of your Netop server)
    # :INIT "Netop Remote control Server"
    # IN UDP 6502 6502 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Timbuktu
    :INIT "Timbuktu"
    OUT TCP 407 407 0.0.0.0 0 R
    :SUB
    IN TCP 1024 65534 0.0.0.0 0 0 D
    :END


    # Virtual Network Computing - VNC
    :INIT "VNC"
    OUT TCP 5900  5900  0.0.0.0 0 R
    :SUB
    IN TCP 5900  5900  0.0.0.0 0 0 AD
    :END


    # Virtual Network Computing - VNC Server
    # (change 192.168.0.2 to correct IP address of your VNC server)
    # :INIT "VNC Server"
    # IN TCP 5900  5900  192.168.0.2 0 0 -
    # :SUB
    # :END


    # GUNtelle
    :INIT "GNUtella"
    OUT TCP 6346 6346 0.0.0.0 0 R
    :SUB
    IN UDP 6346 6346 0.0.0.0 0 0 AD
    :END


    # Dialpad
    :INIT "Dialpad"
    OUT TCP 7175 7175 0.0.0.0 0 R
    :SUB
    IN UDP 51200 51201 0.0.0.0 0 0 AD
    IN TCP 51210 51210 0.0.0.0 0 0 AD
    IN TCP 1584 1585 0.0.0.0 0 0 AD
    OUT TCP 8680 8686 0.0.0.0 0 D
    :END


    # How To Use ICQ with Sybergen Access Server and SyGate
    # This apprule is needed because ICQ needs to listen to some TCP ports
    # to receive incoming events.
    #
    # By default, the machines behind Sybergen Access Server or SyGate can
    # send messages, and create chat but others on Internet cannot send messages
    # create chat rooms or send files directly to Sybergen Access Server or
    # SyGate clients.
    # ---------------------------------------------------------------------
    # ICQ99 for one client
    #
    # One User version, only one user can be supported behind SyGate or
    # Sybergen Access Server with this apprule. In ICQ under
    # 'Preferences & security', click 'Preferences' and then goto Connections,
    # click on 'I am behind a firewall or proxy' then click on
    # 'Firewall Settings' then click 'I don't have a SOCKS Proxy
    # server on my firewall or I am using another Proxy server' then click
    # Next then click 'Use the following TCP listen ports for incoming event'
    # and set the TCP ports for 20000 to 20019.
    #
    :INIT "ICQ99"
    OUT UDP 4000 4000 0.0.0.0 18000000 R
    :SUB
    IN TCP 20000 20019 0.0.0.0 0 0 AD
    :END
    #
    #
    # ---------------------------------------------------------------------
    # ICQ99 for multiple clients
    #
    # On the following appules, change the IP address to the IP address of the
    # ICQ client.  Then enable the following apprules, one for each ICQ client.
    # Then in ICQ under 'Preferences & security', 'Preferences' and Connections,
    # click on 'I am behind a firewall or proxy' then click on 'Firewall Settings'
    # then click 'I don't have a SOCKS Proxy server on my firewall or I am using
    # another Proxy server' then click Next then click 'Use the following TCP
    # listen ports for incoming event' and set the TCP ports for the corresponding
    # port numbers (20000 to 20019; 20020 to 20039; 20040 to 20059).
    #
    # Note: ICQ99 single client apprule must be disabled for these ones to work.
    #
    # :INIT "ICQ99 client 1"
    # OUT UDP 4000 4000 192.168.0.2 18000000 R
    # :SUB
    # IN TCP 20000 20019 0.0.0.0 0 0 AD
    # :END
    #
    # :INIT "ICQ99 client 2"
    # OUT UDP 4000 4000 192.168.0.3 18000000 R
    # :SUB
    # IN TCP 20020 20039 0.0.0.0 0 0 AD
    # :END
    #
    # :INIT "ICQ99 client 3"
    # OUT UDP 4000 4000 192.168.0.4 18000000 R
    # :SUB
    # IN TCP 20040 20059 0.0.0.0 0 0 AD
    # :END
    #
    #
    # ---------------------------------------------------------------------
    # ICQ2000 for one client
    #
    # One User version, only one user can be supported behind SyGate or
    # Sybergen Access Server with this apprule. In ICQ under
    # 'Preferences & security', click 'Preferences' and then goto Server, set
    # the Server port number to 4000.  Then goto Connections, click on User,
    # click on 'Not using Proxy' then click 'Use the following TCP listen
    # ports for incoming event' and set the TCP ports for 20000 to 20019.
    #
    :INIT "ICQ2000"
    OUT TCP 4000 4000 0.0.0.0 18000000 R
    :SUB
    IN TCP 20000 20019 0.0.0.0 0 0 AD
    :END
    #
    #
    # ---------------------------------------------------------------------
    # ICQ2000 for multiple clients
    #
    # On the following appules, change the IP address to the IP address of the
    # ICQ client.  Then enable the following apprules, one for each ICQ client.
    # In ICQ under 'Preferences & security', click 'Preferences' and then goto
    # Server, set the Server port number to 4000.  Then goto Connections, click
    # on User, click on 'Not using Proxy' then click 'Use the following TCP listen
    # ports for incoming event' and set the TCP ports for the corresponding
    # port numbers (20000 to 20019; 20020 to 20039; 20040 to 20059).
    #
    # Note: ICQ2000 single client apprule must be disabled for these ones to work.
    #
    # :INIT "ICQ2000 client 1"
    # OUT TCP 4000 4000 192.168.0.2 18000000 R
    # :SUB
    # IN TCP 20000 20019 0.0.0.0 0 0 AD
    # :END
    #
    # :INIT "ICQ2000 client 2"
    # OUT TCP 4000 4000 192.168.0.3 18000000 R
    # :SUB
    # IN TCP 20020 20039 0.0.0.0 0 0 AD
    # :END
    #
    # :INIT "ICQ2000 client 3"
    # OUT TCP 4000 4000 192.168.0.4 18000000 R
    # :SUB
    # IN TCP 20040 20059 0.0.0.0 0 0 AD
    # :END


    # BuddyPhone - with GameRouter
    #
    # Each computer using BuddyPhone will use a unique listoning port
    # number, use port number 710 and up for each client.  In BuddyPhone,
    # set the first client to 710, the next to 711, the next to 712 and
    # so on.  Then change the IP address of the following apprules to
    # corespond with the IP address of the BuddyPhone client.  And then
    # enable the apprule.
    #
    # :INIT "BuddyPhone client1"
    # OUT TCP 700 700 192.168.0.2 0 R
    # :SUB
    # IN TCP 710 710 0.0.0.0 0 0 AD
    # :END
    #
    # :INIT "BuddyPhone client2"
    # OUT TCP 700 700 192.168.0.3 0 R
    # :SUB
    # IN TCP 711 711 0.0.0.0 0 0 AD
    # :END
    #
    # :INIT "BuddyPhone client3"
    # OUT TCP 700 700 192.168.0.4 0 R
    # :SUB
    # IN TCP 712 712 0.0.0.0 0 0 AD
    # :END


    # Abbott Chat
    :INIT "Abbott Chat"
    OUT UDP 18236 18236 0.0.0.0 0 R
    :SUB
    IN UDP 18231 18231 0.0.0.0 0 0 AD
    IN TCP 18232 18235 0.0.0.0 0 0 AD
    :END


    # PalTalk
    :INIT "PalTalk1"
    OUT TCP    5001    5001    0.0.0.0    0    R
    :SUB
    IN UDP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2095    2095    0.0.0.0    0    0    AD
    IN TCP     5200    5203    0.0.0.0    0    0    AD
    OUT UDP    2090    2091    0.0.0.0    0    D
    OUT TCP    2090    2091    0.0.0.0    0    D
    OUT TCP    2095    2095    0.0.0.0    0    D
    OUT TCP    5200    5203    0.0.0.0    0    D
    :END

    :INIT "PalTalk2"
    OUT TCP    5002    5002    0.0.0.0    0    R
    :SUB
    IN UDP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2095    2095    0.0.0.0    0    0    AD
    IN TCP     5200    5203    0.0.0.0    0    0    AD
    OUT UDP    2090    2091    0.0.0.0    0    D
    OUT TCP    2090    2091    0.0.0.0    0    D
    OUT TCP    2095    2095    0.0.0.0    0    D
    OUT TCP    5200    5203    0.0.0.0    0    D
    :END

    :INIT "PalTalk3"
    OUT TCP    5003    5003    0.0.0.0    0    R
    :SUB
    IN UDP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2095    2095    0.0.0.0    0    0    AD
    IN TCP     5200    5203    0.0.0.0    0    0    AD
    OUT UDP    2090    2091    0.0.0.0    0    D
    OUT TCP    2090    2091    0.0.0.0    0    D
    OUT TCP    2095    2095    0.0.0.0    0    D
    OUT TCP    5200    5203    0.0.0.0    0    D
    :END

    :INIT "PalTalk4"
    OUT TCP    5004    5004    0.0.0.0    0    R
    :SUB
    IN UDP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2095    2095    0.0.0.0    0    0    AD
    IN TCP     5200    5203    0.0.0.0    0    0    AD
    OUT UDP    2090    2091    0.0.0.0    0    D
    OUT TCP    2090    2091    0.0.0.0    0    D
    OUT TCP    2095    2095    0.0.0.0    0    D
    OUT TCP    5200    5203    0.0.0.0    0    D
    :END

    :INIT "PalTalk5"
    OUT TCP    5005    5005    0.0.0.0    0    R
    :SUB
    IN UDP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2090    2091    0.0.0.0    0    0    AD
    IN TCP     2095    2095    0.0.0.0    0    0    AD
    IN TCP     5200    5203    0.0.0.0    0    0    AD
    OUT UDP    2090    2091    0.0.0.0    0    D
    OUT TCP    2090    2091    0.0.0.0    0    D
    OUT TCP    2095    2095    0.0.0.0    0    D
    OUT TCP    5200    5203    0.0.0.0    0    D
    :END

    :INIT "PalTalk Video"
    OUT TCP    8080    8080    0.0.0.0    0    -
    :SUB
    IN TCP     8080    8080    0.0.0.0    0    0    AD
    :END


    # ICUII Client
    :INIT "ICUII Client"
    OUT TCP 2019 2019 0.0.0.0 0 R
    :SUB
    IN TCP 2000 2038 0.0.0.0 0 0 AD
    IN TCP 2050 2051 0.0.0.0 0 0 AD
    IN TCP 2069 2069 0.0.0.0 0 0 AD
    IN TCP 2085 2085 0.0.0.0 0 0 AD
    IN TCP 3010 3030 0.0.0.0 0 0 AD
    OUT TCP 2000 2038 0.0.0.0 0 D
    OUT TCP 2050 2051 0.0.0.0 0 D
    OUT TCP 2069 2069 0.0.0.0 0 D
    OUT TCP 2085 2085 0.0.0.0 0 D
    OUT TCP 3010 3030 0.0.0.0 0 D
    :END


    # AIM Talk
    :INIT "AIM Talk"
    OUT TCP 5190 5190 0.0.0.0 18000000 R
    :SUB
    IN TCP 5190 5190 0.0.0.0 0 0 D
    :END


    # MSN Messenger
    :INIT "MSN Messenger"
    OUT TCP 1863 1863 0.0.0.0 18000000 R
    :SUB
    IN TCP 1863 1863 0.0.0.0 0 0 AD
    :END


    # Powwow 4.0
    #
    # This apprule must be used with the MSN Messanger apprule
    :INIT "Powwow 4.0"
    OUT TCP 13224 13224 0.0.0.0 0 R
    :SUB
    IN TCP 13223 13224 0.0.0.0 0 0 AD
    IN TCP 23213 23214 0.0.0.0 0 0 AD
    IN UDP 13223 13223 0.0.0.0 0 0 AD
    :END


    # Ultima Online
    :INIT "Ultima Online"
    OUT TCP 7775 7775 0.0.0.0 0 R
    :SUB
    IN TCP 5001 5010 0.0.0.0 0 0 AD
    IN TCP 7775 7777 0.0.0.0 0 0 AD
    IN TCP 8888 8888 0.0.0.0 0 0 AD
    IN TCP 8800 8900 0.0.0.0 0 0 AD
    IN TCP 9999 9999 0.0.0.0 0 0 AD
    IN TCP 7875 7875 0.0.0.0 0 0 AD
    OUT TCP 5001 5010 0.0.0.0 0 D
    OUT TCP 7775 7777 0.0.0.0 0 D
    OUT TCP 8888 8888 0.0.0.0 0 D
    OUT TCP 8800 8900 0.0.0.0 0 D
    OUT TCP 9999 9999 0.0.0.0 0 D
    OUT TCP 7875 7875 0.0.0.0 0 D
    :END


    # H.323 compliant video player, NetMeeting 2.0, 3.0, Intel Video Phone
    # Incoming calls are not possible due to NetMeeting assigning ports
    # dynamically. - Modification tested 1-12-2000
    :INIT "Netmeeting"
    OUT TCP 1720 1720 0.0.0.0 0 RH
    :SUB
    IN UDP 1024 65534 0.0.0.0 0 0 DH
    OUT UDP 1024 65534 0.0.0.0 0 DH
    IN TCP 1024 1502 0.0.0.0 0 0 DH
    OUT TCP 1024 1502 0.0.0.0 0 DH
    IN TCP 1504 1730 0.0.0.0 0 0 DH
    OUT TCP 1504 1730 0.0.0.0 0 DH
    IN TCP 1732 65534 0.0.0.0 0 0 DH
    OUT TCP 1732 65534 0.0.0.0 0 DH
    OUT TCP 1503 1503 0.0.0.0 0 D
    OUT TCP 1731 1731 0.0.0.0 0 D
    IN TCP 1503 1503 0.0.0.0 0 0 D
    IN TCP 1731 1731 0.0.0.0 0 0 D
    :END


    # Battle.net (Diablo, WarCraft II)
    #   Notice: we added StarCraft built-in support
    #
    # Because of some limitations with Blizzards battle.net only one person
    # at a time can play Diablo or WarCraft.  StarCraft, however supports
    # multiple Sybergen Access Server clients and SyGate clients playing at
    # the same time.  But the Sybergen Access Server and SyGate server can
    # not join a game with any of its client computers.
    :INIT "Battle.net"
    OUT TCP 6112 6112 0.0.0.0 0 R
    :SUB
    IN UDP 6112 6112 0.0.0.0 0 0 AD
    :END


    # Everquest
    #
    # 1. Make sure you're using the latest build of SyGate
    # 2. Install the EverQuest game on the SyGate server. It doesn't need
    # to be running, just installed on the server.
    #
    # Everquest will work on SyGate.  However, few customers have reported
    # it will freeze after playing the game for limited time and must reboot
    # the system.  The only solution to it for now is to start the game on
    # SyGate server first, then let the client PC join the game, that will
    # solve the problem.  We are still waiting for solution from the Sony
    # Interactive regarding this matter.


    # Abuse.net
    :INIT "Abuse.net"
    OUT     TCP     43      43      0.0.0.0 0       R
    :SUB
    IN      TCP     43      43      0.0.0.0 0       0       AD
    IN      TCP     113     113     0.0.0.0 0       0       AD
    OUT     TCP     113     113     0.0.0.0 0       D
    :END


    # ActiveWorld
    :INIT "ActiveWorld"
    OUT TCP 7777 7777 0.0.0.0 0 R
    :SUB
    IN TCP 7000 7100 0.0.0.0 0 0 AD
    :END


    # DirectPlay (Game Zone, Mplayer, Boneyards) - Modification tested on 8/16/99
    # Most DirectPlay games use this rule
    :INIT "DirectPlay"
    OUT TCP 47624 47624 0.0.0.0 0 R
    :SUB
    IN TCP 47624 47624 0.0.0.0 0 0 AD
    IN UDP 2300 2400 0.0.0.0 0 0 AD
    IN TCP 2300 2400 0.0.0.0 0 0 AD
    OUT UDP 2300 2400 0.0.0.0 0 D
    OUT TCP 2300 2400 0.0.0.0 0 D
    IN TCP 9110 9110 0.0.0.0 0 0 AD
    OUT TCP 9110 9110 0.0.0.0 0 D
    IN TCP 9113 9113 0.0.0.0 0 0 AD
    OUT TCP 9113 9113 0.0.0.0 0 D
    IN TCP 28800 29000 0.0.0.0 0 0 AD
    OUT TCP 28800 29000 0.0.0.0 0 D
    IN UDP 8000 9000 0.0.0.0 0 0 AD
    IN TCP 8000 9000 0.0.0.0 0 0 AD
    OUT UDP 8000 9000 0.0.0.0 0 D
    OUT TCP 8000 9000 0.0.0.0 0 D
    :END


    # For hosting on the MSN Gaming Zone
    :INIT "The Zone"
    OUT UDP 28800 28800 0.0.0.0 0 R
    :SUB
    IN TCP 47624 47624 0.0.0.0 0 0 AD
    OUT TCP 47624 47624 0.0.0.0 0 D
    IN UDP 2300 2400 0.0.0.0 0 0 AD
    IN TCP 2300 2400 0.0.0.0 0 0 AD
    OUT UDP 2300 2400 0.0.0.0 0 D
    OUT TCP 2300 2400 0.0.0.0 0 D
    IN TCP 28800 29000 0.0.0.0 0 0 AD
    OUT TCP 28800 29000 0.0.0.0 0 D
    IN UDP 28800 28800 0.0.0.0 0 0 AD
    :END


    # Westwood Online - C&C Tiberian Sun & Dune 2000
    #   Note: Westwood Online supports only one user per public IP
    # address at any given time. Apprule courtesy of Quantus' World
    :INIT "Westwood Online"
    OUT TCP 4000 4000 0.0.0.0 0 R
    :SUB
    IN TCP 4000 4000 0.0.0.0 0 0 AD
    IN UDP 1140 1234 0.0.0.0 0 0 AD
    IN TCP 1140 1234 0.0.0.0 0 0 AD
    OUT UDP 1140 1234 0.0.0.0 0 D
    OUT TCP 1140 1234 0.0.0.0 0 D
    :END


    # Rainbow Six
    :INIT "Rainbow Six"
    OUT TCP 2346 2346 0.0.0.0 0 R
    :SUB
    IN TCP 2346 2346 0.0.0.0 0 0 AD
    :END


    # Rainbow Six server
    # (Change 192.168.0.2 to the IP address of your Rainbow Six server)
    # :INIT "Rainbow Six Server"
    # IN TCP 2346 2346 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Delta Force
    :INIT "Delta Force"
    OUT UDP 3568 3568 0.0.0.0 0 R
    :SUB
    IN TCP 3100 3999 0.0.0.0 0 0 AD
    IN UDP 3100 3999 0.0.0.0 0 0 AD
    OUT UDP 3100 3999 0.0.0.0 0 D
    OUT TCP 3100 3999 0.0.0.0 0 D
    :END


    # Delta Force Server
    # Where 192.168.0.2 is your Delta Force server
    # :INIT "Delta Force Server"
    # OUT UDP 3568 3568 192.168.0.2 0 -
    # :SUB
    # IN TCP 3100 3999 0.0.0.0 0 0 AD
    # IN UDP 3100 3999 0.0.0.0 0 0 AD
    # OUT UDP 3100 3999 0.0.0.0 0 D
    # OUT TCP 3100 3999 0.0.0.0 0 D
    # :END


    # Soldier Of Fortune
    :INIT "Soldier Of Fortune"
    OUT TCP 28910 28910 0.0.0.0 0 R
    :SUB
    IN TCP 28910 28910 0.0.0.0 0 0 AD
    :END


    # Half Life
    :INIT "Half Life"
    OUT TCP 27015 27015 0.0.0.0 0 R
    :SUB
    IN TCP 27015 27015 0.0.0.0 0 0 AD
    :END


    # Half Life Server
    # (change 192.168.0.2 to correct IP address of your Half Life server)
    # :INIT "Half Life Server"
    # IN TCP 27015 27015 192.168.0.2 0 0 -
    # :SUB
    # :END


    # KALI
    # Built-in supported.


    # Quake2
    # (change 192.168.0.2 to correct IP address of your Quake2 server)
    # :INIT "Quake2 Server"
    # IN UDP 27910 27910 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Bungie.net, Myth, Myth II Server
    # (Change 192.168.0.2 to correct IP address)
    # :INIT "Bungie.net Server"
    # IN TCP 3453 3453 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Unreal server
    # (Change 192.168.0.2 to the IP address of your Unreal server)
    # :INIT "Unreal Server"
    # IN TCP 7777 7777 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Unreal Tournament Server
    # Apprule made possible by: MutantKiller@planetunreal.com
    # (Change 192.168.0.2 to the IP address of your Unreal Tournament server)
    # Unreal Game Data
    # :INIT "UT Game Data"
    # IN UDP 7777 7777 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    # Unreal Query Data
    # :INIT "UT Server Query"
    # IN UDP 7778 7778 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    # Unreal Uplink
    # :INIT "UT Server Uplink"
    # OUT TCP 27900 27900 0.0.0.0 60000 -
    # :SUB
    # IN UDP 7779 7781 0.0.0.0 0 0 A
    # :END
    #
    # Unreal Admin Webserver
    # :INIT "UT Webserver"
    # IN TCP 8888 8888 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Nullsoft Shoutcast Server
    # :INIT "Nullsoft Shoutcast Server"
    # IN TCP 8000 8000 192.168.0.2 0 0 -
    # :SUB
    # IN TCP 8001 8001 0.0.0.0 0 0 -
    # :END


    # Fuse Server
    # (change 192.168.0.2 to correct IP address of your Fuse server)
    # :INIT "Fuse Server"
    # IN TCP 4500 4500 192.168.0.8 0 0 -
    # :SUB
    # :END


    # Heretic II Server
    # (change 192.168.0.2 to correct IP address of your Heretic server)
    # :INIT "Heretic II Server"
    # IN TCP 28910 28910 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Hexen II
    # Each computer behind Sybergen Access Server or SyGate,
    # hosting Hexen II must have a different port number.
    # Below is an EXAMPLE of three apprules for hosting Hexen II
    # - Player 1 has IP address of 192.168.0.2, with a port number 26900
    # - Player 2 has IP address of 192.168.0.3, with a port number 26901
    # - Player 3 has IP address of 192.168.0.4, with a port number 26902
    # Just change the IP address to the IP address of the computer hosting
    # Hexen II, and set the Port number to a unique number
    # To connect to Hexen II from outside of your LAN you must put the IP
    # address if your external Network Card/Modem and the prot number of
    # the game you wish to join.
    #
    # Hexen II server 1
    # (change 192.168.0.2 to correct IP address of your Hexen II server)
    # :INIT "Hexen II Server 1"
    # IN UDP 26900 26900 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    #
    # Hexen II server 2
    # (change 192.168.0.3 to correct IP addres of your Hexen II server)
    # :INIT "Hexen II Server 2"
    # IN UDP 26901 26901 192.168.0.3 0 0 -
    # :SUB
    # :END
    #
    #
    # Hexen II server 3
    # (change 192.168.0.4 to correct IP address of your Hexen II server)
    # :INIT "Hexen II Server 3"
    # IN UDP 26902 26902 192.168.0.4 0 0 -
    # :SUB
    # :END


    # Laplink Server
    # (change 192.168.0.2 to correct IP address)
    # :INIT "Laplink server"
    # IN TCP 1547 1547 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Remotely Possible Server
    # (Change 192.168.0.2 to the IP address of your Remotely Possible server)
    # :INIT "Remotely Possible Server"
    # IN TCP 799 799 192.168.0.2 0 0 -
    # :SUB
    # :END


    # Lotus Notes Server (Port 1352)
    # (Change 192.168.0.2 to the IP address of your Notes server)
    # :INIT "Lotus Notes Server"
    # IN TCP 1352 1352 192.168.0.2 0 0 -
    # :SUB
    # :END


    # pcANYHWERE host inside.
    # You need replace the 192.168.0.2 in the following line to
    # your client's IP address and remove the comments flag '#' from
    # following two rules
    #
    # :INIT "pcANYWHERE Use"
    # IN TCP 5631 5631 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    # :INIT "pcANYWHERE Seek"
    # IN UDP 5632 5632 192.168.0.2 0 0 -
    # :SUB
    # IN UDP 22 22 0.0.0.0 0 0 -
    # :END


    ########################################################################
    # Following demos how to make servers on Sybergen Access Server
    # or SyGate client visiable to outside.
    #
    # Demo Web Server1 on Sybergen Access Server or SyGate client,
    # use http://<sygate's ip>:80 to access 192.168.0.2:80
    #
    # You need replace the 192.168.0.2 in the following line to
    # your client's IP address and remove the comments flag '#' from
    # following rule.
    #
    # :INIT "Our WEB Server"
    # IN TCP 80 80 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    # Demo FTP Server1 on Sybergen Access Server or SyGate client
    # You need replace the 192.168.0.2 in the following line to
    # your client's IP address and remove the comments flag '#' from
    # following rule.
    #
    # :INIT "Our FTP server"
    # IN TCP 21 21 192.168.0.2 0 86400000 -
    # :SUB
    # :END
    #
    # Demo TELNET Server on Sybergen Access Server or SyGate client
    # You need replace the 192.168.0.2 in the following line to
    # your client's IP address and remove the comments flag '#' from
    # following rule.
    #
    # :INIT "Our TELNET server"
    # IN TCP 23 23 192.168.0.2 0 36000000 -
    # :SUB
    # :END
    #
    # Demo Mail Server on Sybergen Access Server or SyGate client
    # You need replace the 192.168.0.2 in the following line to
    # your client's IP address and remove the comments flag '#' from
    # following rule.
    # Generally, you receive mail with POP3 protocol,
    # send mail with SMTP protocol.
    #
    # :INIT "Our Mail(POP3) server"
    # IN TCP 110 110 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    # :INIT "Our Mail(SMTP) server"
    # IN TCP 25 25 192.168.0.2 0 0 -
    # :SUB
    # :END
    #
    #
    # www.sygate.co.kr
    # Wowcall
    :INIT "Wowcall"
    OUT TCP 8000 8000 0.0.0.0 0 R
    :SUB
    IN UDP 4000 4020 0.0.0.0 0 0 AD
    IN TCP 8000 8000 0.0.0.0 0 0 AD
    :END
    # Telefree
    :INIT "Telefree"
    OUT UDP 32000 32000 0.0.0.0 0 -
    :SUB
    IN UDP 32000 32000 0.0.0.0 0 0 AD
    IN TCP 9001  7777 0.0.0.0 0 0 AD
    :END
    #
    # Sorbada
    :INIT "soribada"
    OUT TCP 8765 8765 0.0.0.0 0 R
    :SUB
    IN UDP 9001 9004 0.0.0.0 0 0 AD
    :END
    #


    ###################### End Of APPRULE.CFG #########################

    reTweet
    Posted by 문스랩닷컴
    blog comments powered by Disqus


      Web Analytics Blogs Directory