UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`SIPNET EU S.R.O.
`
`Petitioner
`
`V.
`
`Straight Path IP Group, Inc.
`Patent Owner
`
`Case No. IPR2OI 3-00246
`
`U.S. Patent No. 6,108,704
`
`Before KLAYAN K. DESI-IPANDE, THOMAS L. GIANNETTI, and
`
`TRENTON A. WARD, Administrative Patent Judges.
`
`DECLARATION OF LESLIE EHRLICH RE WINDOWS NT 3.5 USER
`
`GUIDE
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 1
`
`

`
`Case No. IPR20l3—00246
`
`U.S. Patent No. 6,108,704
`
`DECLARATION
`
`1, Leslie Ehrlich, hereby state as follows:
`
`1.
`
`2.
`
`I am over the age of 18 and am competent to make this declaration.
`
`I have personal knowledge of the matters stated herein.
`
`° 3.
`
`I work at Kilpatrick Townsend & Stockton, LLP as a paralegal.
`
`4.
`
`I received the box for Windows NT 3.5 from Yuri Kolesnikov. The
`
`contents include a CD-ROM that includes a digital copy of the Windows NT
`
`Server retail TCP/IP Guide (the “Yuri Guide”).
`
`5.
`
`The Yuri Guide was in the form of help screens.
`
`I printed out all the
`
`help screens, and then scanned them, which are being submitted as Exhibit 1018 in
`
`the above referenced Case, No. IPR20l3-00246.
`
`6.
`
`I had our word processing department run a software comparison of
`
`the printed and scanned copy of the Yuri Guide on the CD-ROM to Exhibit 1004
`
`in the above referenced Case, No. IPR20l3-00246. The two documents are
`
`substantially identical, with the exception of the glossaries which contain different
`
`terms. The main differences besides the different text of the glossary are formatting
`
`type differences due to the help screen format on the CD-ROM. Attached as
`
`Exhibit A is a copy of the redline comparison.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 2
`
`

`
`Case No. IPR20l3-00246
`
`U.S. Patent No. 6,108,704
`
`7.
`
`I compared the portions of Exhibit 1004 included in the claim charts
`
`of the original petition in the above referenced Case, No. IPR2013-00246. Those
`
`portions are identical, with the exception of a few typos in the claims chart.
`
`I declare under the penalty of perjury that the foregoing Declaration is true and
`
`correct.
`
`Date: November 26,2013
`
` @ fi
`
`Leslie Ehrlich
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 3
`
`

`
`GHAPTER—l—9verviewOvewiew of Microsoft TCP/IP for
`Windows NT
`
`Transmission Control Protocol/Internet Protocol
`protocol that provides
`communication across interconnected networks made up of computers with
`diverse hardware
`
`(TCP+;IP)
`
`is a networking
`
`architecturesandvariousoperatingsystems.TCP/IPcan1x2usedto<xmmmnicate
`with
`
`Windows NT systems, with devices that useaother Microsoft.networking products,
`and with
`
`non—Microsoft systems, such as UNIX.
`This chapter introduces Microsoft TCP/IP for Windows NT. The topics in this
`chapter include
`the following:
`4; What is TCP/IP for Windows NT?
`4; What does Microsoft TCP/EP;§ include?
`4; Windows NT solutions in TCP/IP intemetwerksinternetworks
`For more detailed information on TCP/IP and its integration with Microsoft
`Windows NT and
`
`other networking products, see Chapter 3, "Networking Concepts for TCP+;IP."
`Chapter 1 lof8
`
`What Es;§ TCP/IP for Windows NT?
`TheTCP/IPprotocolfamilyij;astandardset<flfnetworkingprotocols,orrules,
`that govern how
`data is passed between computers on a network. TCP/$P;§ is used to connect
`the Internet,
`the
`worldwide internetwerkinternetvvork connecting over two million
`universities, research labs, Ursgg. defense
`installations, and corporations.
`(By convention, "Internet" is capitalized
`when referring to the
`worldwide internetwork.) These same protocols can be used in private
`internetworks that
`connect several local area networks.
`
`Microsoft TCP/IP for Windows NT enables enterprise networking and
`connectivity on
`Windows NT computers. Adding TCP/IP to a Windows NT configuration offers the
`following
`advantages:
`4.-
`
`££fi%H¥$ardA.standard, routable enterprise networking protocol that is theinost
`complete and
`accepted protocol available. All modern operating systems offer TCP/IP
`support, and most
`large networks rely on TCP/IP for much of their network traffic.
`9:.-
`
`AeeehnelegyA technology for connecting dissimilar systems. Many standard
`connectivity utilities are
`available to access and transfer data between dissimilar systems,
`File Transfer
`Protocol
`(FTP) and Terminal Emulation Protocol
`standard
`utilities are included with Windows NT.
`4.-
`
`(Telnet). Several of these
`
`including
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 4
`
`

`
`Aeekfigfiflkrobust, scalable, cross—platforn1client—server framework. Microsoft
`TCP/IP supports the
`Windows Sockets 1.1 interface, which is ideal for developing client—server
`applications that
`can run with Windows Sockets—compliant stacks from other vendors. Many
`public—domain Internet
`internet tools are also written to the Windows Sockets standard. Windows
`Sockets
`
`applications can also take advantage of other networking protocols such as
`Microsoft
`
`the Microsoft
`NWLink,
`Novell® NetWare®
`networks. I
`
`implementation of the IPX;£§/SPX protocols used in
`
`The enabling technology necessary to connect Windows NT to the global
`Internet. TCP/IP,
`Point to Point Protocol (PPP), and.Windows Sockets 1.1 provide the foundation
`needed to
`connect and use Internet services.
`
`Ghapter—l—Overview of Microsoft TGPnPTCP[IP for Windows NT 2of8
`
`What Does Microsoft TCP/IP Include?
`Microsoft TCP/IP provides all the elements necessary to implement these
`protocols for netwerking
`nebvvorking. Microsoft TCP/IP includes the following:
`._____
`
`Core TCP/IP protocols,
`Internet
`
`including the Transmission Control Protocol
`
`(TCP),
`
`(UDP), Address Resolution Protocol
`
`(IP), User Datagram Protocol
`Protocol
`(ARP), and Internet
`(I€MPlClVlP). This suite of
`lnternet Control Message Protocol
`Interneeinternet protocols provides aseea set of
`standards for how computers communicate and.how networks are interconnected.
`Support
`is also provided for PPP and Serial—Line IP (SLIP), which are protocols used
`for dial—up
`access to TCP/IP networks,
`
`including the Internet.
`
`gn
`
`Support for application interfaces, including Windows Sockets 1.1 for network
`programming, remote procedure call (RPC) for communicating between systems,
`NetBIOS
`
`for establishing logical names and sessions on the network, and network
`dynamic data
`exchange (Network GDEQQE) for sharing information embedded in documents
`across the
`network.
`
`._____
`
`Basic TCP/IP connectivity utilities,
`rexec,
`rsh,
`telnet, and
`tftp . These utilities allow Windows NT users to interact with and use resources
`on
`
`including finger, ftp,
`
`lpr, repggp,
`
`non—Microsoft hosts, such as UNIX workstations.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 5
`
`

`
`-Ia
`
`TCP/IP diagnostic tools,
`netstat, ping,
`route, and tracert. These utilities can be used.to detect and resolve TCP/IPIP
`networking
`—_
`problems.
`
`lpq, nbtstat,
`
`including arp, hostname,
`
`ipconfig,
`
`-Ia
`
`Services and related administrative tools,
`service for transferring
`files between remote computers, Windows-Ineernetinternet Name Service (WINS)
`for dynamically
`registering and querying computer names on an internetwork, Dynamic Host
`Configuration
`Protocol
`(DHCP) service for automatically configuring TCP/IP on Windows NT
`computers,
`
`including the FfP—ServerFTP Sewer
`
`and.TCP/IP;§ printing for accessing printers connected to a UNIX computer or
`connected
`
`directly to the network via TCP/IP.
`
`-OT
`
`(SNMP) agent. This component allows a
`Simple Network Management Protocol
`Windows NT computer to be administered remotely using management tools such
`as Sun®
`
`Net Manager or HP® Open.View. SNMP can also be use to monitor and.manage DHCP
`servers and WINS servers.
`
`4—————The client seftwaresoMare for simple network protocols,
`Character Generator, Daytime,
`Discard, Echo, and Quote of the Day. These protocols allow a Windows NT
`computer to
`respond to requests from other systems that support these protocols. When
`these
`
`including
`
`protocols are installed, asamplea sample QUOTES files is also installed in
`the *SYSEemreet%lsysfemrootl
`SYSTEM32\ DR VERS\ETC directoiy.
`ojPath MTU Discovery, which provides the ability to determine the datagram
`size for all
`
`routers between Windows NT computers and any other systems on the WAN.
`Microsoft
`
`TCP/IP also supports the Internet Gateway Multicast Protocol
`is used by
`new workgroup software products.
`The following diagram shows the elements of Microsoft TCP/IP alongside the
`variety of
`additional applications and.connectivity utilities provided by Microsoft and
`other developers.
`Overview of Microsoft TCP/IP for Windows NT 3of8
`
`(IGMP), which
`
`Gcpllefg
`wms
`
`..f
`
`Enhaneed—eenneetivity—applieatiens—Da mel opment tools
`[t€Llb,
`ot—lcrRl=c]
`fl
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 6
`
`

`
`J*
`
`applicshona
`fsx@&8®a 4eae§§mn;F=.»1¥2:§@¢=» 315
`"if
`Integrated wiehu .i1i1
`;windows N¥—B—flI
`Developed by E§;rd—partiesihird pa"tiea or the researeh—eemmeni%yraaeawch
`oo rn m. nity
`Microsoft TCP/IP+ Core Technology and Third—Party Add—ons
`Ghapter—I—GVerView—ef—Miereseft—T€PnP—fer—Windews—NT
`TCP/IPIP standards are deeineddefined.in.Requests for Comments (RFCs), which
`are published by the
`Internet Engineering Task Force (IETF) and.other working groups. The relevant
`RFCs
`
`supported.in.this version.of Microsoft TGPIIPTCP[IP (and.for Microsoft Remote
`Access Service) are
`
`described in the following table.
`Requests for Comments
`(RFCs) Supported by Microsoft TCP/IP
`RFC Title
`768
`783
`791
`792
`793
`826
`854
`862
`863
`864
`
`865 864—894—9é97922—959—l99&7—é992—é9347—é9Q5—lG42—逧5—&&&2—&&227—&&2%—ll%4
`
`W(
`
`‘D k0 rl>
`KO |—' 9
`i 959
`
`(UDP)
`User Datagram Protocol
`Trivial File Transfer Protocol
`Ineerneeinternet Protocol
`(IP)
`
`(TFrPTFTP)
`
`Interneeinternet Control Message Protocol
`Transmission Control Protocol
`(TCP)
`Address Resolution Protocol
`(ARP)
`Telnet Protocol
`(TELNET)
`Echo Protocol
`(ECHO)
`Discard Protocol
`(DISCARD)
`Character Generator Protocol
`
`(CHARGEN)
`
`(QUOTE)
`Quote of the Day Protocol
`Daytime Protocol
`(DA¥fiMEDAYTIME)
`IP over Ethernet
`
`(ICMP)
`
`(broadcasting with subnets)
`922 IP Broadcast Datagrams
`File Transfer Protocol
`(FTP)
`J\»\v\.<>.>»,~:~\><,\/¢.f..wL
`.|l"ff?~"iH. m"|il I
`I
`1
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 7
`
`

`
`">$—4<»E/:n>‘9*>~<if6
`\:,E,;'..:.:.:.:.::,.:.:.
`\4\-VS/:'V'>44»\»<>\f
`
`lid“LU
`
`.»<,\/M/.».nw.<.\»w\.—y..—><—.
`rI*EG*"Ff?"if."iTi'?T?'?i?"%fi
`
`L21
`WWW fr:fm=
`VIII
`
`?>/¥$'52*r*lé\/\\'*S!§f»**'l4\P$?v*'\~'*r'
`96
`
`/2S*P**‘
`
`'v'ulndow HFS] J
`
`9*i'5‘i'§zlT1l$§4‘5=l—l'l~l&§Ki|2§=3§l1§i1§:
`Enhanced
`
`iial§fi§69|*$&u Ef
`
`cnnnacxii vitgr
`
`1001,1002
`1034,1035
`1042
`1055
`1112
`
`1122,1123
`1134
`1144
`1157
`1179
`1188
`1191
`1201
`1231
`1332
`1334
`1533
`1534
`1541
`1542
`1547
`1548
`1549
`1552
`1553
`1570
`Draft RFCs
`NetBIOS Service Protocols
`
`Domain Name System (DOMAIN)
`IP over Token Ring
`Transmission of IP over Serial Lines (IP—SLIP)
`
`(IGMP)
`Internet Gateway Multicast Protocol
`Host Requirements (communications and applications)
`Point to Point Protocol
`(PPP)
`
`Compressing TCP/IP Headers for Low—Speed Serial Links
`Simple Network Management Protocol
`(SNMP)
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 8
`
`

`
`
`
`II49——Line Printer Daemon Protocol
`&&88——IP over FDDI
`
`ll9l——Path MTU Discovery
`1-2-9J_:IP over ARCNET
`
`3_—2—3—]_—IEEE 802.5 Token Ring MIB (MIB—3_—l-E)
`I332——PPP Internet Protocol Control Protocol
`&334——PPP Authentication Protocols
`
`(IPCP)
`
`I533——DHCP Options and BOOTP Vendor Extensions
`&534——Intereperatienlnteroperation Between DHCP and BOOTP
`&54&——Dynamic Host Configuration Protocol
`(DHCP)
`&542——Clarifications and Extensions for the Bootstrap Protocol
`&544——Requirements for Point to Point Protocol
`(PPP)
`I548——Point to Point Protocol
`(PPP)
`
`(HDLC) Framing
`l549——PPP in High—level Data Link Control
`I552——PPP Internetwork Packet Exchange Control Protocol
`&55%——IPX Header Compression
`I549——Link Control Protocol
`
`(LCP) Extensions
`
`(IPXCP)
`
`Braft—RE€s—4fletBIOS Frame Control Protocol
`x.2J5—,—i
`Compression Control Protocol
`All RFCs can be found on the Internet via ds.ineemieinternic.net.
`
`(NBFCP)¢¥:PPP over ISDN¢1_PPP over
`_
`
`In this version of Windows NT, Microsoft TCP/IP does not include aeempleteg
`complete suite of TCP/IP
`connectivity utilities, Network File System (NFS) support, or some TCP/IP
`server servieessen ices
`
`(daemons) such as routed and telnetd. Many such applications and utilities
`that are available
`
`in the public domain or from third—party vendors work with Microsoft TCP/IP.
`Tip
`For Windows for Workgroups computers and MS—BGS—basedDOSbased computers on
`a Microsoft
`
`network, you can install the new version of Microsoft TCP/IP;§—32 for Windows
`for Workgroups
`and.thelMicrosoft.Network:Client'version.2.0-ferMS—for‘MS—DOS fronithetflindows
`NT Server 3.5
`
`compact disc. This software includes the DHCP and WINS clients and other
`elements of the
`
`new Microsoft TCP/IP software. For information about installing these
`clients, see Chapter 9,
`"Network Client AdministratorTé" in the Windewsvwgvdows NT Serversenger
`Installation Guide.
`
`Ghapter—&—Overview of Microsoft TGPnPTCP[IP for Windows NT 4 of8
`Windows NT Solutions in TCP/IP lneerneewerkslnternetworks
`When TCP/IP is used as a transport protocol with Windows NT, Windows NT
`computers can
`communicate with other kinds of systems without additional networking
`software. Microsoft
`
`TCP/IP;§ in combination with other parts of Windows NT provides a scalable
`solution for
`
`enterprise networks that include a mix of system types and software on many
`platforms.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 9
`
`

`
`This section summarizes hewggg TCP/IP works with Windows NT to provide
`enterprise networking
`solutions. For information about how the elements discussed in this section
`fit within the
`
`networking architecture, see "TCP+4IP and.Windows NT Networking" in Chapter
`3,
`"Networking
`Concepts for TCP/IPi§."
`
`Windows NT Solutions in TCPIIP lnternetworks
`
`Using TCP/IP for Scalability in Windows Networks
`TCP/IP delivers a scalable intemetwerkinginternetworking technology widely
`supported by hardware and
`software vendors.
`
`When TCP/IP;§ is used as the enterprise networking protocol,
`networking solutions
`from.Microsoft can be used on an existing internetwork to provide client and
`server support for
`
`the Windows
`
`TCP+IPL;§ and connectivity utilities. TheSt~These solutions include:
`.31
`
`;=Microsoft Windows NT‘Workstation.3.5, with enhancements to support wide area
`networks
`
`(WAN), TCP+4IP printing, extended LMHOSTS, Windows Sockets 1.1, FTP Server
`service
`
`software, and DHCP and WINS client software.
`
`-Ia
`
`;=Microsoft Windows NT Server 3.5, with the same enhancements as Windows NT,
`plus
`DHCP server and WINS serversenger software to support the implementation of
`these new
`
`protocols.
`
`-Ia
`
`
`;=Microsoft TCP/IP—32 for Windows for Workgroups 3T11T3.1 1 with Windows
`Sockets support,
`can.be used to provide access for Windows for Workgroups computers to Windows
`NT,
`
`LAN Manager, and other TCP+IP;;§ systems. Microsoft TCP/IP—32 includes DHCP
`and WINS
`client sef%wareT—soMare.
`
`-Ia
`
`;=Microsoft LAN Manager, including both.client and.server support for Windows
`Sockets,
`
`and MS—DOS®—based connectivity utilities. The Microsoft Network Client 2.0
`software on the
`
`Windows NT Server compact disc includes newlwicrosoft TCP/IP support with_DHCP
`and
`WINS clients.
`
`The current version of TCP/IP for Windows NT also supports IP routing in
`systems with
`multiple network adapters attached to separate physical networks
`(meltihemedmultlhomed systems).
`N1—tuori-"'
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 10
`
`

`
`B N
`
`et~ of"* *
`
`Ovewiew of Microsoft TCP/IP for Windows NT 5of8
`IP router.
`,rTo other"
`1n9tgOfk5
`IP mmék *'iP rcuter
`Other
`netuorls
`
`Ec
`
`lL£l§ill1H§§
`
`Researchers "
`
`‘ii
`HQbi1L D3*Jid,
`'§fisua]i‘iai:iu11
`'1"cI3t, Jeffat*;,
`C1l11131. Praducers
`
`I
`
`
`Wam*efr::=nt Tec
`
`DescripHuIl
`
`*
`
`l ¢
`
`ThE L£Jrer1z8tt1'act=31f is 3 *sfilxitinxx trzajset nf differential
`equatiljxiswlmifzlz displays s\:»1*11»3 rather
`remarkable 6eh31fi¢i11.a11d.1*epr&se11ts 0:118 of the 1ar1dfn3¢rl::3irf1tha
`Eelfl QfCh3fjs. The 6qL1:ati¢:=11s
`ciescribc t1i€
`2D Haw ufHuid3;1asiinp1e 1fe1:ta11gi 1131*
`1:}i3§€32Sf1';i1311isheateclalungthéljnttofn.
`siff1I31¢ mntielwas it1tei'1|:1ef1.¢tasi1'nL11ate rf1e;1iu11i—$0318
`f3t11'i§rsIj1416fil3i:un'i;€ctinn.
`i
`MESA Mnsaicfnr M5 Windnws "fr *
`
`file Edit Qptiuns Llavigate hnnutate Starting Paints Quad Kill Heat3tutt
`Help
`Qummands Qptiuns Quukrnarks Help
`l I
`
`Erevious Menu if Lakeside School, Seattle, Washington 1
`Congressional Committee Assignments for 1Il3rd Congress (U
`Electronic Mail Addresses for Members of Congress
`Government Manual: Legislatiue Branch {UMich]'
`List of Firsts for 1ll3rd Congress {UMd)
`
`3 W
`
`indows NT Solutions in TCPIIP Internetworks
`
`Using ¥€PaPTCP[IP for Connectivity to the Internet
`Microsoft TCP/IP provides Windows networking with aseta set of
`ineemeewerkiaginternetvvorking protocols based
`on open standards.
`Microsoft TCP/IP for Windows NT includes many common connectivity
`applications such as
`ftp, rsh, and telnet that support file transfer,
`and terminal emulation
`for communication.on the Tneerneeinternet and between.non—Microsoft network
`
`remote process execution,
`
`systems.
`J
`
`;.E. E;
`
`E
`
`.3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 11
`
`

`
`TCP/IP applications created by researchers and other users, such as Gopher
`and NCSA
`
`Mosaic, are in the public domain or are available through other vendors as
`both 16-bit and
`
`32-bit Windows—based.applications. Any of these applications that follow the
`Windows Sockets
`
`1 . 1 standard are compatible with Windows NT. Such applications allow a Windows
`NT
`
`computer to act as a powerful Internetinternet client using the extensive
`intemetwerkinginternetworking components
`with public—domain viewers and applications to access Internet resources.
`Tipfri,
`Public—domain.Windows—based.utilities such as LPR.and.Gopher can be obtained
`on the
`
`Internet via ftp.cica.indiana.edu in the /pub/win3/nt or
`/pub/winvvin3/winsock directory, or via the
`same directories on ftp.cdrom.com.
`Overview of Microsoft TCP/IP for Windows NT 6of8
`
`M CFO aoft TG p;||:'
`HFS loat
`x
`for UH
`
`loat
`
`Q § K‘ urlm host 1
`Windows NT Solutions in TCP/IP lnternetworks
`TCP/IP for Heterogeneous Networking
`Because most medemmodern operating systems (in addition to Windows NT) support
`TCP/IP
`protocols, an.internetworkzwittimixed.systenitypes can share information using
`simple
`networking applications and utilities. With TCP+4IP as aeenneetivieyg
`connectivity protocol, Windows NT can
`communicate with many non—Microsoft systems,
`.31
`
`including:
`
`Internet hosts
`
`a—————
`
`Apple® Macintosh® systems
`
`.31
`
`IBM® mainframes
`
`-Ia
`
`UNIX systems
`
`-Ia
`
`Open VMS® systems
`
`.31
`
`Printers with network adapters connected directly to the network
`
`NFS—hes%
`Mieresef%—T€PnP
`fhhemat re—anuroea)
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 12
`
`

`
`U$X—hest—[Pat|l\nx:»rka for '—mlSL
`Microsoft TCP/IP Connectivity
`Microsoft TCP/IP provides aframewerka framework for interoperable
`heterogeneous networking. The
`modular architecture of Windows NT‘networking with.its transport—independent
`services
`
`contributes to the strength of this framework. For example, Windows NT
`supports these
`transport protocols, among many others:
`
`L I
`
`PX/SPX for use in NetWare environments, using the Microsoft NWLink transport .
`Besides
`
`providing interoperability with.NetWare networks,
`transport for
`Windows networking as well.
`
`IPX/SPX is afasta fast LAN
`
`-Ia
`
`TCP+4IP for internetworks based on IP technologies. TCP+4IP is the preferred
`transport for
`
`internetworks and provides interoperability with UNIX and other TCP-!-4IP—based
`networks.
`
`J
`a—————
`
`;.E. E;
`
`E
`
`.3
`
`NetBEUI as the protocol for local area networking on smaller networks and
`compatibility
`with existing LAN Manager and Lan Server networks.
`
`a—————
`
`AppleTalk® for connecting to and sharing resources with Macintosh systems.
`Other transport protocols provided by third—party vendors, such as
`DEGne%¢iDECnetfM and OSI, can also
`be used by Windows NT networking services.
`Windows NT provides standard network programming interfaces through the
`Windows
`
`Sockets, RPC, and NetBIOS interfaces. Developers can take advantage of this
`heterogeneous
`client—server~sen[er platform to create custoniapplications that will run on
`any system in the
`Ovewiew of Microsoft TCP/IP for Windows NT 7of8
`
`4 L
`
`:'3~.T.l
`
`Mmsgsr
`Windovua NT LAN Malage°:F"
`_liQQluQlfl9_EA§i
`Windows for
`
`Wori—cgroupa
`
`enterprise. An example of such a servieesengice is Microsoft SGL—ServerSQL
`Sewer, which uses Windows
`Sockets lTl1.1 to provide access to NetWare, MS—BeS—basedDOSbased, Windows
`NT, and UNIX clients.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 13
`
`

`
`Windows NT Solutions in TCP/IP Internetworks
`Using ¥€PaPTCP[IP with Third—Party Software
`TCP/IP is aeemmena common denominator for heterogeneous networking, and
`Windows Sockets is a
`
`standard used by application developers. Together they provide a framework
`for cross—platform
`
`client—server development. TCP+EPL;§—aware applications from vendors that
`comply with the
`Windows Sockets standards can.run.over'virtually'any'TCP+4IP implementation.
`The Windows Sockets standard ensures compatibility with.Windows—based TCP/IP
`utilities
`
`developed.byInore than.30 vendors. This includes third—party applications for
`the XWindew—X Window
`
`System, sophisticated terminal emulation software, NFS, electronic mail
`packages, and more.
`Because Windows NT offers compatibility with 16-bit Windows Sockets,
`applications created
`for Windows 3.x Windows Sockets will run.over Windows NT without modification
`or
`
`recompilation.
`For example,
`third—party applications for Xwindewx Window provide strong
`connectivity solutions by
`means efeflflindewofx Window servers, database servers, and terminal emulation.
`With such
`
`applications, a Windows NT computer can work as an Xwindewx Window server
`platform while
`retaining compatibility with applications created for Windows NT, Windows
`3.1, and MS§;§—DOS
`mnthesamesystem.Otherthird—partysoftwareincludesXwindewxwindowclient
`libraries for
`
`Windows NT, which allow developers to write Xwiaéewx Window client
`applications on Windows NT
`that can be run and displayed remotely on Xwindewx Window server systems.
`The Windows Sockets API is a networking API used by programmers creating
`applications for
`both the Microsoft Windows NT and Windows operating systems. Windows Sockets
`is an open
`standard.that is part of the Microsoft Windows Open.Systen1Architecture (WOSA)
`initiative. It
`
`is a public specification based on Berkeley UNIX sockets, which means that
`UNIX applications
`can be quickly ported to Microsoft Windows and Windows NT. Windows Sockets
`provides a
`single standard programming interface supported by all the major vendors
`implementing
`TCP+4IP for Windows systems.
`The Windows NT TCP/IP utilities use Windows Sockets, as do 32-bit TCP/IP
`applications
`developed by third parties . Windows NT also uses the Windows Sockets interface
`to suppertsuppoit
`Services for Macintosh and $PX;§§/SPX in NWLink. Under Windows NT, 16-bit
`Windows—based
`
`applications created under the Windows Sockets standard will run without
`modification or
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 14
`
`

`
`recompilation. Most TCP/IP users will use programs that comply with the
`Windows Sockets
`
`standard, such as ftp or telnet or third—party applications.
`The Windows Sockets standard allows a developer to create an application with
`a single
`common interface and a single executable that can run.over many of the TCP/IP
`implementations provided by vendors. The goals for Windows Sockets are the
`following:R
`
`;=Provide a familiar networking API to programmers using Windows NT, Windows
`for
`
`Workgroups, or UNIX
`
`-Ia
`
`l Offer binarybinaw compatibility between vendors for heterogeneous
`Windows—based TCP/IP
`stacks and utilities
`
`-Ia
`
`lzsupport both connection—oriented and connectionless protocols
`Typical Windows Sockets applications include graphic connectivity utilities,
`terminal emulation
`
`software, Simple Mail Transfer Protocol
`network printing
`utilities, SQL client applications, and corporate client—server
`applications.
`Ifyeulf you are interested in developing a Windows Sockets application,
`specifications for Windows
`Sockets are available on the Internet from ftp.microsoft.com, on.CompuServe®
`in the MSL
`
`(SMTP) and electronic mail clients,
`
`Cverview of Microsoft TCP/IP for Windows NT 8of8
`
`O‘\U'1IJ>L»J[\)|-'-
`
`library, and in the Microsoft Win32® Software Developers Kit.
`—¢7———To get a copy of the Windows Sockets specification via anonymous FTP
`Make sure you have write permission in your current working directory.
`Start ftp and connect to ftp.microsoft.com (or 198.105.232.1).
`Log on as anonymous.
`
`Type your electronic mail address for the passwordT£
`Type cd \advsys\winsock\speellspec11 and press ENTER.
`Use the dir command to see the list of available file types. Ifyeugg
`ygu want binary data such as
`type bin and press ENTER.
`in the Microsoft Word version,
`6e—1Zé=Determine the file with the format you.want [for example, ASCII (.TXT),
`PostScript® (.PS),
`or Microsoft Word (.DOC)], and then type get winsock.ext§§; where extgég is
`the format that you
`want, such as winsock.doc for the Microsoft Word version.
`A
`E
`.
`E
`.
`E
`E
`E
`.
`3
`
`——7———To get a copy of the Windows Sockets specification from
`GempuServeCompuSeNe
`lT——1. Type go msl and press ENTER.
`2.
`Browse using the keywords windows sockets.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 15
`
`

`
`Choosethefilewiththeformatyouwant[ASCII(TTXT),PostScript(.PS),
`3.
`or Microsoft Word
`
`(.DOC)], and then type get winsock.extg§£.
`for Windows
`There is also an electronic mailing list designed for discussion of Windows
`Sockets pregrammmg
`programming.
`—:7———To subscribe to the Windows Sockets mailing list
`0
`Sendelectronicmailto4éstservIistserv@sunsite.unc.eduwitheamessage
`body that contains
`subscribe winsock user's—email—address.
`
`You can use the same procedure to subscribe to two mailing lists called
`winsock—hackers
`and winsock—users.
`
`EQBLLE
`
`*
`
`: <>><=
`
`Installing and Configuring Microsoft T€P%IP
`and SNMP
`
`This chapter explains how to install TCP/IP and the SNMP service for Windows
`NT and how to
`
`configure the protocols on your computer.
`The TCP/IP protocol family can.be installed as part of Custom Setup when you
`install Windows
`
`following the steps described in this chapter. Also, if you upgrade to
`NT,
`anewa new version of
`
`Windows NT, Setup automatically installs the new TCP/IP protocol and preserves
`your
`
`previous TCP/IP settings. This chapter assumes that Windows NT has been
`successfully
`installed on your computer but TCP/IP has not been installed.
`The following topics appear in this chapter:
`4; Before installing Microsoft TCP/IP
`41 Installing TCP/IP
`4' Configuring TCP/IP
`4' Configuring TCP/IP to use DNS
`4' Configuring advanced TGPliPTCP[IP options
`41 Configuring SNMP
`4' Removing TCP/IP components
`for use with TCP/IP
`4; Configuring Remote Access Service (RAS)
`You must be logged on as a member of the Administrators group to install and
`configure all
`elements efTGPof TCP/IP.
`. Chapter 2
`lofl3
`
`Installing and Configuring Microsoft TCP/IP and SNMP 2<>fl3
`Before Installing Microsoft TCP/IP
`Important
`The values that you will use for manually configuring TCP/IP and SNMP must
`be supplied by
`the network administrator.
`
`Check with your network administrator to find out the following information
`before you installinstali
`Microsoft TCP/IP on a Windows NT computer:
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 16
`
`

`
`Igiwhether you can use Dynamic Host Configuration.Protocol (DHCP) to configure
`TCP/IP.
`You can choose this option if a DHCP server is installed.on.your internetwork.
`You cannot
`
`choose this option if this computer will be a DHCP server. For information,
`see "Using
`Dynamic Host Configuration Protocol" later in this chapter.
`I; Whether this computer will be a DHCP server. This option is available only
`for
`
`Windows NT Server . For information, see Chapter 4 , "Installing and Configuring
`DHCP
`
`Servers.l;
`
`I ;
`
`;Whether this computer will be aiflindows Internet Name Service (WINS) server.
`This
`
`option is available only for Windows NT Server. For information, see Chapter
`5, "Installing
`and Configuring WINS Servers."
`
`heeher" Whetner this computer wIIIwil! be a WINS proxy agent. For
`information, see "Windows
`Internet Name Service and Broadcast Name Resolution" in Chapter 3 , "Networking
`Concepts for TCP/IP."
`If you cannot use DHCP for automatic configuration, you need to obtain these
`values from the
`
`I W
`
`network administrator so you can configure TCP/IP manually:
`I; The IP address and subnet mask for each network adapter card installed on
`the computer.
`For information, see "IP;§ Addressing" in Chapter 3.
`I; The IP address for the default IeeaIIocal gateways (IP routers).
`
`hether' Wnether your-eemputerIwIIIcomputerwill use Domain Name System (DNS)
`and,
`if so,
`the IP addresses
`
`and DNS domain.name of the DNS servers on the internetwork. For informationT;
`see
`
`"Domain Name System Addressing" in Chapter 3.
`I; The IP addresses for WINS servers, IfWINSif WINS servers are available on
`your network.
`5]
`
`.
`
`E
`
`E
`
`3;
`
`H.
`
`3;
`
`E.
`
`.
`
`You need to know Eheggg following information before you install the Simple
`Network Management
`
`Protocol (SNMP) servicecn1your‘computer7Q;=as described.in "Configuring SNMP"
`later in this
`chapter:I
`
`' Community names in your network
`
`i l
`
`Trap destination for each community
`
`i '
`
`IP addresses or computer names for SNMP management hosts
`
`Installing and Configuring Microsoft TCP/IP and SNMP 30fl3
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 17
`
`I W
`
`

`
`Installing TCP/IP
`I—————You must be logged on as a member of the Administrators group for the
`local computer to
`install and configure TCP/IP. _.,
`To install Microsoft TCP/IP on a Windows NT computer
`l7——;é=Start the Network option in Control Panel.
`2.
`In the Network Settings dialog box, choose the Add Software button.
`3.
`In the Add Network Software dialog box, select TCP+4IP Protocol And
`Related Components
`
`from the Network Software listT£ and then choose thetne Continue button.
`4.
`In the Windows NT TCP+4IP Installation Options dialog box, check the
`options for the
`TCP/IP components you.want to install, as described in the table that follows
`this
`
`procedure, and then choose the Continue button.
`If any TCP/IP elements have been installed previously, thesetnese are dimmed
`and not
`
`available in the Windows NT TCP+IPL;§ Installation Options dialog box.
`You can read the hint bar at the bottom of each TCP+4IP dialog box for
`information about a
`
`selected item, or choose the Help button to get detailed online information
`while you are
`installing or configuring TCP/IP.
`5.
`Windows NT Setup displays a message asking for the fellfuii path.to the
`Windows NT
`
`distribution files. Provide the appropriate location, and choose the Continue
`button.
`
`You can specify adrivea drive letter for-fleppyftoppy disks, a CD—ROM drive,
`or a shared network
`
`directory, or you can specify the Universal Naming Convention.(UNC) path.name
`for a
`
`network resource, such as \\NTSETUP\MASTER.
`All necessary files are copied to your hard disk.
`Note
`
`If you are installing from floppy disks, Windows NT Setup may request disks
`more than
`once. This is normal and is not an error condition.
`
`6. Ifyeelf you.selected.the options for installing the SNMP and EfP§g§ Server
`services, you are
`automatically asked to configure these services. Follow the directions
`provided in the
`online Help for these dialog boxes. For additional details, see "Configuring
`SNMP" later in
`
`this chapter, and see also Chapter 7,
`Service."
`
`"Using the Microsoft FfP£g§ Server
`
`In the Network Settings dialog box, choose OK.
`7.
`Ifyeelf you.checked.the Enable.Automatic DHCP Configuration option and a DHCP
`server is
`
`available on your network, all configuration settings for TCP+4IP are
`completed
`automatically, as described in "Using Dynamic Host Configuration Protocol"
`later in this
`
`chapter.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 18
`
`

`
`Ifyeelf you did not check the Enable Automatic DHCP Configuration option,
`continue with the
`
`configuration procedures described in "Configuring TCP+4IP Manually" later
`in this chapter.
`TCP+4IP must be configured in order to operate.
`Ifyealf you checked the DHCP Server Service or WINS Server Service options,
`you must
`complete the configuration steps described in Chapters 4 and 5.
`Windows NT TCP+4IP Installation Options
`Gietivefie
`TCP/IP Intemetwerking—Internetworking
`Connectivity Utilities
`SNMP Service
`
`TCP/IP Network Printing
`Su ort
`FTP Server Service
`
`Simple TCP/IP Services
`DHCP Server Service
`WINS Server Service
`Enable Automatic DHCP
`
`Configuration
`Usage
`
`Includes the TCP+4IP protocol, NetBIOS over TCP/IP and Windows
`Sockets interfaces, and the TCP/IP;§ diagnostic utilities. These
`elements are installed automatically.
`Ins