Unique Registrations/Second
`Unique Renewals/Second
`Using Performance Monitor with TCP/IP Sen/ices
`Monitoring WINS Sewer Performance
`lOoflO
`
`G
`
`Internetwork Printing with TCP/IP
`Users on.any Microsoft networking computer can print to direct—connect TCP/IP
`printers or to
`printers that are physically attached to UNIX computers if at least one Windows
`NT computer
`has Microsoft TCP+IP[lP printing installed.
`(RFC) 1179.
`Microsoft TCP+4IP printing conforms with Request for Comment
`This chapter describes how to create a TCP+IPé;§ printer when TCP+4IP is
`installed on I;
`Windows NT computer and.how to print to a Windows NT print server from.a UNIX
`computer.
`The topics in this chapter include:
`
`&——;=Overview of TCP+4IP printing
`l——;=Setting up Windows NT for TCP/IP printing
`&——;=Creating a printer for TCP+4IP printing
`&——;=Printing to Windows NT from UNIX clients
`For complete information.about working with printers, see Chapter 6, "Print
`Manager," in the Windews
`Vwndows NT System Guide.
`9verview—ef—T€PnP—Print&fig
`Chapter 9 lof5
`
`In_a Windows NT internetwork with multiple kinds of computers and operating
`systems, users
`can take advantage of Microsoft TCP/IP to easily print to computers that are
`connected
`
`through a UNIX computer or that are connected directly to the network (via
`abuilta built—in network
`
`adapter card or through a serial/parallel ethernet print server).
`Such an internetwork might ineladeinciude computers running Windows NT
`Workstation and
`
`Windows NT Server, plus computers with only Microsoft Windows for Workgroups
`3.11 or
`
`MS—DOS with IAQQE Manager networking software.
`To take advantage of the printing capabilities of Microsoft TCP/IP, only the
`single Windows NT
`computer that defines aT€Pa TCP/IP printer needs to have TCP/IP installed.
`The other client
`
`computers do not need to have TCP/IP installed” All other computers can.print
`to the TCP/IP
`printers over any protocol they share with.the Windows NT'TCP/IP print server.
`That is,
`the
`
`computer acting as the Windows NT TCP/IP;§ print serversenger must be
`configured with all protocols
`used by any clients that will be printing to the TCP+4IP printer.
`Any Windows NT computer with TCP/IP printing iflstalledinstalied can print
`directly to these kéadsKinds of
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 181
`
`

`
`printers and can function as a gateway for other network users.
`In the following sample configuration of a Microsoft network, all computers
`can connect to
`
`printers named.\\nt\plp; and \\nt\p2 on the network. The Windows NT computer
`with Microsoft
`
`TCP/EP;§ installed created these TCP/IP printers, which consist of a
`direct—connect printer and a
`printer connected to a UNIX computer. The Windows NT computer with.TCP/IP is
`named nt in
`
`this example, and the printers are named plp; and p2, respectively.
`pl printer
`llTlGlT9r99
`
`NW$TTiHk
`Maeintesh
`
`AppletaM+
`ll.lOl993
`
`i<3E=~l
`WO|'kgDLp83.ll 11.101.1411
`H§lBEHl_Li::1
`N'U‘ll'l—lnk UWrdDv8l|T
`H&iBEU
`
`N'UU'Li k TCP.fPpa%I M8 938 Ma
`2;
`8 Prin'er jclb pppiatg;
`Printing to TCP+4IP or UNIX Printers Using Microsoft TCP/IP
`E;
`1
`.
`.
`.
`J
`E
`
`Osh
`
`lnternetwork Printing with TCP/IP
`Ovewiew of TCP/IP Printing
`2of5
`Ms~u6‘éf
`
`LN! Mmaga‘
`Wir' dowa HT
`mnith TG PMP
`TCPH P
`NMEEUI
`
`HflL_LlflK
`p2 printer
`48:4
`
`H§§_EHi_HEL
`Wrndovxs for
`‘m 1
`
`"**~» 8 2
`
`‘um ti
`
`Setting Up Windows NT for TCP/IP Printing
`Any Windows NT computer can be used to create a—'PGPa TCP/IP printer if Microsoft
`TCP+4IP is
`installed with TCP+4IP printing support.
`._ To configure a Windows NT computer for TCP/IP printing
`1.
`Start the Network option in Control Panel. When the Network Settings
`dialog box appears,
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 182
`
`

`
`choose the.Add.Software button.to display the.Add.Network Software dialog box.
`2.
`Select TCP+4IP Protocol And.Related.Components in the Network Software
`list box, and
`then choose the Continue button.
`
`In the Windows NT TCP—!—4IP Instailation Options dé_—a—legdiaiog
`3 .
`box, check the TCP/IP Network
`Printing Support option.
`If Microsoft TGPIIPTCP[IP is not already installed on this eempeterComputer,
`check the other options you
`want, as described.in.Chapter 2, "Installing and Configuring Microsoft TCP/IP
`and SNMP."
`
`Choose the OK button. Windows NT Setup displays a message asking for
`4.
`the full path to
`the Windows NT distribution files. Provide the appropriate location, and
`eheeseChoose the
`Continue button.
`
`All necessary files are copied to your hard disk.
`5.
`Ifthelf the Enable Automatic DHCP Configuration option is not checked in
`the Windows NT
`
`TCP/IP-Iaseallaeieninstallation.Options dialog box, yotimust complete all the
`required procedures for
`manually configuring TCP/IP as described in "Configuring TGPliPTCP[l
`Chapter 2.
`When the Network Settings dialog box reappears after you finish configuring
`TCP/IP,
`choose the Close button, and then restart your computer for the changes to
`take effect.
`
`in
`
`"
`
`You can now create a TCP+4IP printer on this Windows NT computer.
`Greatiag—aPrinter—fer—T€PaPlnternetwork Printing with TCP[IP 3of5
`
`Printer game:
`
`Eiscjnrripi
`E£lfl£_£Q;
`Qhare this
`.
`»'
`. =s
`.
`
`i*iiizi" 24£i¥?-
`i aei:4zi=azri.
`SUNUS LPR
`
`Adobe LaserJet II Cartridge V52.3
`LPT3:
`CO Ml
`COM 2
`C0 M3
`CO M4
`FILE:
`
`You can use Print Manager to create aTGP+a TCP[IP printer in the same way that
`you create any
`printer to be used on.a Windows NT‘network. You.need.the following information
`to create a
`
`TCP+IP£;§ printer:
`a—————
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 183
`
`

`
`;=The IP identifier of the host where the printer is connected. This can be
`the DNS name or
`
`the IP address. A direct—connect printer has its own IP identifier. For a
`printer connected to
`a UNIX computer,
`this is the computer's IP identifier.
`
`D l
`
`The printer name as it is identified on the host. This is the name defined
`on the UNIX
`
`computer or the name defined by the manufacturer for the direct—connect
`printer.
`The computer where you create the TCP/IP printer must have TCP/IP installed
`and configured
`with the TCP/IP Network Printing Support option, as described in Chapter 2.
`——————To create a TGP%IPTCPIIP printer
`1. From the Printer menu in Print Manager, choose Create Printer.
`D+Seriptien+
`Print—+e+
`-L-P5l‘—3—:-
`
`Sh~e—Name+—G9M4+
`leeatien+—FILE+
`
`In the Printer Name box of the Create Printer dialog box,
`2.
`of up to 32
`characters. This name appears in the title bar of the printer window, and
`Windows NT
`
`type a name
`
`users see this name when connecting to this printer if it is shared.
`This name can be the same as the printer name as it is identified on the
`printer's UNIX
`host, but it does not have to be.
`For a direct—connect printer, see the hardware documentation.to find the name
`by which
`the network printer identifies the print queue.
`3.
`In the Driver list, select the appropriate driver and, optionally, type
`text to inform network
`
`users about the printer in the Description box.
`4.
`In the Print To box, select Other to display the Print Destinations
`dialog box.
`lnternetwork Printing with TCP/IP
`Creating a Printer for TCP/IP Printing
`4of5
`
`7——Print—Bestinatiens
`1 -4 |4l=\M¢¥*lnMYWr:PHmlm'\*A|
`
`11 mm
`
`; A
`
`vailablegyailable Print Monitors+
`H--dN~Pee
`LeeaiPee
`Hewlett—Packard Network Port
`Local Port
`LPRMeriter—LPR M onitor
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 184
`
`

`
`Other...
`
`l ame or address of host providing lpd:
`1
`Name of pginlel on that machine:
`.1mu1mu1al an manuals |.|1||11m1|l||
`koti.microsoft.com
`SUN LASEFI
`5.
`
`*
`
`|
`
`"
`
`"
`
`67
`
`47
`
`87
`
`Ghapter—9——Internetwerk—PrinEing—with—TGPnP—l8i—In the Available Print
`Destinations liseiist, select LPR Print Monitor, and then choose OK.
`Add—lPR—eempallltla—printer
`
`I—t&e}J—I
`
`6. In.the Name Or Address Of Host Providing LPD box of the Add.LPR Compatible
`Printer
`
`type the DNS name or IP address of the host for the printer you
`
`dialog box,
`are adding.
`This can.be the DNS name or-lP;§ address of the direct—connect TCP+4IP printer
`or of the
`
`UNIX computer to which the printer is connected. The DNS name can.be the name
`specified for the host in the HOSTS tilefile.
`LPR stands for Line Printing utility, and LPD stands for Line Printing Daemon,
`which is how
`these elements are known on UNIX.
`
`7. In the Name Of Printer On That Machine box,
`as it is identified
`
`type the name of the printer
`
`by the host, which is either the direct—connect printer itself or the UNIX
`computer.
`For example, youinight have a UNIX computer running the print server component
`(fiég)
`with which the TCP+4IP printer you are creating will interact. Hi; lpd
`recognizes a printer
`attached.to the UNIX computer by the name Crisp,
`this box is
`
`the name you should type in
`
`Crisp.
`For adireeea.direct—connect printer, this is whatever name was used to create
`the prifiteprinter while
`running lpdT—Ipd.
`8. When.the Create Printer dialog box reappears, check the Share This Printer
`On The
`
`Network option if this definition is being created on a Windows NT computer
`that will serve
`
`as a print server for other users to access this printer.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 185
`
`

`
`ii
`
`
`Printer
`l-l ame:
`
`_D_iriyeri
`Dgegripfigni
`Print +e+——%%B¥EM£€RGSGF¥€GM—SU—LASER—l+l—ES$+té+ttttt—J—tO:
`
`rzl—%8
`
`5 hare this printmprinter on the network ————T—$—ll4—$
`
`1 S
`
`hgre Name:
`Lpcanonz
`SUNOS LPH
`
`Adobe LaserJet II Cartridge V52.3
`KOT|.wl|m:HOs0FT.cOM;suN msEH
`LPH pmt
`+7eeatieH+—w:%Bk;g—E——%—Rm—l—24—8———————J—Bldg2FIml278
`9.
`By default,
`in the Share Name box, Printer Manager creates asharedg
`shared resource name that
`
`is compatible with MS—B9S—basedDOSbased computers. You can edit this name,
`which users willwiii see
`
`when browsing to find this printer on the network.
`10. Optionally,
`in the Location box, you can type information about where
`this printer is located.
`Users can see this location information when they connect to the printer.
`11.
`Complete any other configuration information in the Create Printer
`dialog box, as described
`in Chapter 6 of the Windewsvwndows NT System Guide, and then choose the OK
`button.
`
`In Print Manager, the printer name you specified in the Create Printer dialog
`box appears in the
`title bar of the printer's window. For client computers configured with
`Microsoft Network Client
`
`version 2.0 for MS—99SQQ§, users willwill see only the shared name, not the
`printer name. Users who
`
`connect to this TCP+4IE>printer can select it and print to it frontapplications
`like any other printer.
`Users and administrators can use Print Manager to secure and audit the use
`of the printer and
`change its properties.
`
`4.
`E:inter Qucument Qptions §ecurity indow Help
`3lJF\lOS
`F'Fi Ready Ducuments wait
`8 gll
`8 Default SUN|]S LPH 2
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 186
`
`

`
`U U Status Priority
`..U...3.9.no|.a.m9....I5.a|.m.tbr.u.3h..—....Ur*lt.|.te=d] .
`m|.n|s.tr.a.|...5...2.?.t5tvl.
`1
`.1
`D ocumenl N ame Owner Printed at Pages Size
`Tip
`You.can.use the lpr connectivity utility at the command.prompt to print afileg
`file to a host running
`an.LPD server. You.can.also use the lpq<iiagnostic utility to obtain.the status
`of a print queue
`on a host running the LPD server. For information, see the entries for lpr
`and %pqIp_q in
`Chapter 11, "Utilities Reference."
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`.
`
`. ..£'u3
`
`lnternetwork Printing with TCP/IP 5of5
`Printing to Windows NT from UNIX Clients
`The Lpdsvc service is the server side of TCP/IP printing for UNIX clients.
`Ifig any UNIX clients on
`the network want to print to a printer connected to a Windows NT computer,
`this service needs
`
`to be running on the Windows NT computer so it can accept requests from the
`UNIX clients.
`
`The Lpdsvc service supports any print format,
`not perform any
`additional processing.
`EEe———TO start or stop the Lpdsvc service
`0
`At the command prompt,
`type net start lpdsvelpdsvc or net stop
`lpdsvelpdsvc and press ENTEREnter.
`_O r_
`
`including plain—text. It does
`
`In_Contro1 Panel, choose the Services option. Then.select £pds¥eLpdsvo in.the
`Service list and
`choose the Start button.
`
`On the UNIX computer, you can.use the Windows NT printer by typing a command
`such as the
`
`following:
`lpr —S NTHest——P—LpdPrinter—myfileTtxt—NTHosf —P LpdPrinfer myHle.fxf
`Where:
`
`-Is
`
`NTHes%l NTI—lost is the Windows NT Server running the Lpdsvc service. This
`Windows NT
`
`computer should be listed in the HOSTS file on the UNIX computer or on the
`DNS server.
`
`-Is
`
`£pdPriaterl l pdPrinfer is the name of the printer created on NTHeseNTHosf.
`
`gn
`
`myfileT—txtl myHle.fXf is the file to be printed.
`The Lpdsvc service is independent of the Lprmon service. The Lprmon service
`runs
`
`automatically to allow a Windows NT computer (and all clients who can access
`this computer)
`to print to a printer connected to a UNIX system, as described.in.the previous
`section.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 187
`
`

`
`€HAP¥ER—}G
`
`Troubleshooting TCP/IP
`The following diagnostic utilities included with Microsoft TCP/£P;§ can be
`used to eindfind solutions to
`
`TCP/IP networking problems.
`
`
`
`tracert Check the route to a remote system.
`For complete details about the utilities included.witt1Windows NT, see Chapter
`11, "Utilities
`Reference." See also the online Command Reference.
`
`These other Windows NT tools can be used for TCP/IP troubleshooting:
`ll Microsoft SNMP service,
`to supply statistical information to SNMP
`management systems,
`
`as described in Chapter 2, "Installing Microsoft TCP+EP4;§ and SNMP."
`ll Event ¥iewf++rViewer,
`to track errors and events, as described in-Eheggg
`Event Viewer chapter in the
`System Guide.
`ii Performance Monitor, to analyze TCP/IP, FTP, and.WINS server performance,
`as
`
`described in Chapter 8,
`(Microsoft
`
`"Using Performance Monitor with TCP/IP Services."
`
`SNMP must be installed if you want to monitor TCP/IP.)
`ll Registry Editor,
`to browse and edit Registry parameters, as described in
`REABMETWRT—in—yeer—%systemreet—direeteryT—READMEWRI
`in
`your \sysfemroot directory.
`Chapter 10 lof9
`arp View the ARP (address resolution protocol) table on the local computer
`
`2d
`
`etect invalid entries.
`hostname Print the name of the current host.
`
`ipconfig Display current TCP/IP network configuration values, and update or
`release
`
`TCP/IP network configuration values.
`n.btstat Check the state of current NetBIOS over TCP/IP connections, update
`
`% L
`
`MHOSTS cache, and determine the registered name and scope ID.
`netstat Display protocol statistics and the state of current TCP/IP
`connections.
`
`ping Verify whether TCP/IP is configured correctly and that a remote TCP/IP
`system is available.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 188
`
`

`
`' The computer was restarted after TCP/IP was instailed and configured
`Troubleshooting TCP/IP 2 of9
`Troubleshooting IP Configuration
`If you.have trouble installing Microsoft TCP/IP on your computer, follow the
`suggestions in the
`error messages. You.can.also use the ping utility to isolate network hardware
`problems and
`incompatible configurations, allowing you to verify aphysieala physical
`connection to a remote computer.
`Use the ping utility to test both.the host name and.the IP address of the host.
`For the syntax
`and description.of the ping command, see Chapter 11, "Utilities Reference."
`Ille——To test TCP/IP using the ping utility
`1. Ifthelf the computer was configured using DHCP, use ipconfig to learn.the
`IP address.
`
`Use ping to check the loopback address by typing ping 127.0.0.1 and
`2.
`pressing ENTER at
`the command prompt. The computer should respond immediately.
`Iflg ping is not found or the command fails, check the event log with Event
`Viewer and look
`
`for problems reported by Setup or the TCP/IP service.
`3.
`To determine whether you configured IP properly, use ping with the IP
`address of your
`computer, your default gateway, and a remote host.
`If you cannot use ping successfully at any point, check the following:
`
`
`
`The leeallocal computer's IP address is valid and appears eerreeelycorrecdy
`in the TCP/IP Configuration
`dialog box I
`The IP address of the default gateway and remote host are correct
`4.-
`
`IP routing is enabled and the link between routers is operational
`—I—fyeeIf you can use ping to connect to other Windows NT computers on a different
`subnet but
`
`cannot connect through File Manager or with net use I%server§§se[ver\share,
`check the following:
`3.-
`
`The computer is WINS—enabled (if the network includes WINS servers).
`3.-
`
`TheTne WINS server addresses are correct, and theggg WINS servers are
`functioning.
`J.-
`
`The correct computer name was used.
`3.-
`
`The target host uses NetBIOS. Ifneelf not, you.must use FTP or Telnet to make
`a connection+£ in
`this case,
`the target host must be configured with the FTP server daemon or
`Telnet server
`
`daemon, and you must have correct permissions on the target host.
`€hapter—&—S—Treablesheeting—T€PnP
`&——The scope ID on the target host is the same as the local computer.
`&——AreaterA router exists between your system and the target system.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 189
`
`

`
`-}—LMHOSTS contains correct entries, so that the computer name can.be resolved.
`For more
`
`information, see "Troubleshooting Name Resolution Problems" later
`chapter.
`&——TheTlwe computer is not configured to use WINST——W NS
`
`in this
`
`Troubleshooting IP Configuration
`Troubleshooting Name Resolution Problems
`Ifig the IP address responds but the host name does not when you use ping,
`you have a name
`resolution problem. In this case, use the following lists of common problems
`in name resolution
`to find solutions.
`Name Resolution Problems in HOSTS
`
`These problems can occur because of errors relatedrelated.to the HOSTS file:
`I; The HOSTS file or DNS do not contain the particular host name.
`I; The host name in the HOSTS file or in the command is misspelled or uses
`different
`
`capitalization.
`
`(Host names are case—sensitive.)
`
`I; An invalid IP address is entered for the host name in the HOSTS file.
`I; The HOSTS file contains multiple entries for the same host on separate
`lines.
`9:.-
`
`Amapping' A mapping for a computer name—to—IP address was mistakenly added
`to the HOSTS file
`(rather than LMHOSTS).
`Name Resolution Problems in LMHOSTSLNIHOSTS
`
`These problems can occur because of errors related to the LMHOSTS file:
`I; The LMHOSTS file does not contain an entry for the remote server.
`&;'The computer name in LMHOSTS is misspelled.
`(Notice that LMHOSTS names are
`converted to uppercase.)
`I; The IP address for aeemputera computer name in LMHOSTS is not valid.
`Troubleshooting TCP/IP 3of9
`
`ra
`
`Troubleshooting IP Configuration
`Troubleshooting Other Connection Problems
`In addition to ping, the other diagnostic utilities such as netstat and nbtstat
`can be used to
`
`find and resolve connection problems. Although this is not a complete list,
`these examples
`show how you might use these utilities to track down.problems on the network.
`... §: To determine the cause of Error 53 when connecting to a server
`1.
`If the computer is on the local subnet, confirm that the name is spelled
`correctly and that
`the target computer is running TCP/IP as well. If the computer is not on the
`local subnet,
`be sure that its name and IP address mapping are available in the LMHOSTS file
`or the
`WINS database.
`
`Error 53 is returned if name resolution.fails for a particular computer name.
`2.
`If all TCP/IP elements appear to be installed properly, use ping with
`the remote computer
`to be sure that its TCP/IPIE software is working.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 190
`
`

`
`__
`
`;=To determine the cause of long connect times after adding to LMHOSTS
`Because this behavior can.occur with a large LMHOSTS file with an entry
`0
`at the end of the
`
`file, mark the entry in LMHOSTS as a preloaded entry by following eheggg
`mapping with the
`#PRE tag. Then use the nbtstat —R command to update the local name cache
`immediately.
`_Or_
`
`Place the mapping higher in the LMHOSTS file.
`As discussed in Chapter 6,
`the LMHOSTS file is parsed.sequentially to locate
`entries
`
`without the #PRE keyword” Therefore, you should place frequently1ised.entries
`near the
`
`top of the file and place the #PRE entries near the bottom.
`_
`g=To determine the cause of connection problems when specifying a
`serversewer name
`
`4——;=Use the nbtstat —n command to determine what name the server registered
`on the
`network.
`
`The output of this command lists several names that the computer has
`registered. Aname—A name
`resembling the computer's computer name should be present. If not,
`of the other
`
`try one
`
`unique names displayed by nbtstat.
`The nbtstat utility can also be used to display the cached entries for remote
`computers
`
`from.either #PRE entries in LMHOSTS or recently resolved names. Tfig the name
`the remote
`
`computers are using for the server is the same, and the other computers are
`on a remote
`
`subnet, be sure that they have the computer's mapping in their LMHOSTS files.
`€hapter—&S—Treeblesheeting—T€PnP
`$lle——;=To determine why only IP addresses work for connections to foreign
`systems but not
`host names
`
`£T——1. Make sure that the appropriate HOSTS file and DNS setup have been
`configured for theggg
`computer by checking the host name resolution configuration using the Network
`icon in Gentrel—Panel—and—then—eheesing—the—BNS—betten—in—the—T€P+£P
`
`Troubleshooting TCP/IP 4of9
`
`2.
`
`3=~
`Control Panel and then choosing the DNS button in the TCP/IP Configuration
`dialog box.
`If you.are using a HOSTS file, make sure that the name of the remote computer
`is spelled
`the same and capitalized the same inig the file and.by the application using
`it.
`
`3w————
`
`If you are using DNS, be sure that the IP addresses of the DNS servers are
`correct and in
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 191
`
`

`
`the proper order. Use ping with the remote computer by typing both the host
`name and IP
`
`address to determine whether the host name is being resolved properly.
`Elle——To determine why a TCP/IP connection.to a remote computer is not working
`properly
`0
`Use the netstat —a command to show the status of all activity on TCP
`and UDP ports on
`
`the leealiocal computereé
`The state of a good.TCP connection.is usually established with 0 bytes in the
`send and
`
`receive queues. Efig data is blocked in either queue or if the state is
`irregular,
`there is
`probably a problem with the connection. Tfig not, you are probably
`experiencing network or
`application delay.
`Treublesheeting—9ther—Preblems
`
`This section presents some possible TCP+4IP symptoms with.recommendations for
`using the
`diagnostic utilities to determine the source of the problems.
`Troubleshooting TCP/IP
`Troubleshooting Other Problems
`;of—the—preblemsT—g
`
`Troubleshooting Other Problems
`Troubleshooting the FTP Server Service
`£ll>—To determine whether the FfP—ServerFTP Sewer service is installed
`
`correctly
`4—————Use ftp on the local computer by typing the IP loopback address from
`the command line+£
`for example,
`type ftp 127.0.0.1 and press ENTER.
`The interaction with the server locally is identical to the interaction
`expected for other
`Windows NT (and most U£XUNlX) clients. You can also use this utility to
`determine whether
`
`the directories, permissions, and so on are configured properly for the FTP
`Server service.
`
`Troubleshooting TCP/IP 6of9
`
`Troubleshooting Other Problems
`Troubleshooting Telnet
`tJe~——To determine why the banner displayeddisdplayed.with.Telnet identifies
`a different computer, even
`when specifying the correct IP addressa dress
`1.
`Make sure the DNS name and hosts table are up to date.
`2.
`Make sure that two computers on the same network are not mistakenly
`configured with the
`same IP address.
`
`The ethemetethernet and IP address mapping is done by the ARP (address
`resolution protocol)
`module, whictibelieves the first response it receives. Therefore, the impostor
`computer's
`reply sometimes comes back before the intended computer's reply.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 192
`
`

`
`These problems are difficult to isolate and track down. Use the arp —g
`eemmandcommend to display
`the mappings in the ARP cache. Tfyealf you know the ethemetethernet address
`for the intended remote
`
`computer, you can easily determine whether the two match. If not, use arp —d
`to delete the
`
`then use ping with the same address (forcing an ARP), and check the
`entry,
`ethemetethernet
`
`address in the cache again by using arp +;g.
`Chances are that if both computers are on the same network, yotiwill eventually
`get a
`different response. If not, you.may have to-felterfilter the traffic from.the
`impostor host to
`determine the owner or location of the system.
`Troubleshooting TCP/IP 7of9
`
`Troubleshooting Other Problems
`Troubleshooting Gateways
`tJe~——To determine the cause of the message,
`belong to one
`of the configured interfaces4.4éé" during Setup
`4—;=Find.out.whether the default gateway is located on the same logical.network
`as the
`
`"Your default gateway does not
`
`computer's network adapter by comparing the network ID portion of the default
`gateway's EP
`
`igaaddress with the network-£D;2(s) of any of the computer's network adapters.
`For example, aeemputera computer with asinglea single network adapter
`configured with an IP address of
`102.54.0.1 and a subnet mask of 255.255.0.0 would require that the default
`gateway be of
`the form 102.54.a.b because the network ID portion of the IP interface is
`lG2T54TlO254.
`
`Ghapter—&9—Treublesheeting—TGPnP
`Troubleshooting TCP/IP 8of9
`
`Troubleshooting TCP/IP 9of9
`Troubleshooting TCPIIP Database Files
`The fellewingfoliowing UNIX—style database files are stored in the
`\systemreetsysfemroot
`\SYSTEM32\BRE¥ERSDR VERS\ETC when you install Microsoft TCP/IP:
`Filename
`Use
`
`
`
`To troubleshoot any of these files on a local computer:
`gi
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 193
`
`

`
`l Make sure the format of entries in each file matches the format defined in
`
`the sample file
`originally installed with Microsoft TCP/IP;§.
`
`I '
`
`Check for spelling or capitalization errors.
`
`i l
`
`Check for invalid IP addresses and identifiers.
`
`$E————¥—$L—$—$+—R—%—%
`
`7 E
`
`OSTS Provides hostname—to—IP address resolution for Windows Sockets
`
`applications
`LMHOSTS
`NETWORKS
`
`Provides NetBIOS name—to—IP address resolution for Windows networking
`Provides network name—to—network ID resolution for TCP/IP management
`PRQTQCQLS Provides protocol name—to—protocol
`ID resolution for Windows
`Sockets
`
`applications
`SERWCES Provides service name—to—port
`applications
`
`UeilitiesUt Iities Reference
`
`ID resolution for Windows Sockets
`
`This chapter is a reference for using Microsoft TCP/IPIE utilitiesvfi which
`provide diagnostic and
`connectivity utilities for network and connectivity administration.
`I¢IH+seThese client utilities areare
`
`provided for file transferei terminal emulationT£ and network diagnostics.
`Besides the connectivity
`support built into Windows NTT£ some third—;party vendors areggg developing
`advanced connectivity
`
`utilities saehsucn as X Window werversrservers Network File System (NFS)
`implementationsry and so on.
`commands help you detect TCP/IP
`I9iagnestie—€eIIIIII£&&%ils—hdpDiagnostic
`networking problems. +—4enaeetérét¥—mnmw&als—Connectivity commands
`allow users to interact with and useuse resources on non—Microsoft hosts
`
`%UGhsuch as UNIX
`
`workstations. The following commands areggg included:
`
`I ;
`
`=Diagnostic commands: arpeézhostnameeg:ipconfigwg:lpqeéznbtstatw;:netstat+£
`pingvfi routevi and
`tracert
`
`rexeceé rSh?£
`
`I ;
`
`=Connectivity commands: fingerré ftpT—lprT—repL_IprL_rgp,
`telnetT£ and tftp
`Important
`
`The ftpvi ftpsvcvfi rexecvfi and telnet utilities all relvrely on password
`+nEthentieatienauthentication by the remote
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 194
`
`

`
`computer. Passwords areggg not encrypted before being %entsent over the
`network. This allows
`
`another user-e4uippedeguipped.with.a network analyzer on the same network to
`steal a user's remote
`
`account password. For this reasonvi it is ~lrenglystrongly recommended that
`users of these utilities
`
`choose different passwords for their Windows NT workgroupT—%verkstatienT£
`
`workstation or domain from the
`
`passwords used on %ystemssystems they are connecting to that areggg not
`Microsoft systems. All
`passwords used hygy Windows networking services are encrypted.
`w7w———To get help on T€P%§PTCPIIP utilities
`4-7;=At the command.premp~prompt,
`type the command name with.+;?. For example,
`type nbtstat +;? to
`get help on this eemmandcommend.
`_Or_
`
`1 .
`2.
`3.
`_Or_
`
`In the Program Manager Main group , double—click the Windows NT Help icon.
`In the Windows NT Help window, click the Command Reference Help button.
`In the Commands windowT—eliek. Click a command name.
`
`Choose the Search button in the Command Reference window, and then type a
`command
`name in the box or select aeemmanda command name from the list.
`Note
`
`Switches used in the syntax for TCP/IP commands are case—sensitive. For
`example, for nbtstat
`,
`the switch +;R haslwes a different effect from the —r switch.
`affi
`Chapter 11 l0fl8
`
`This diagnostic command<iisplays andwnodifies the IP—to—Ethernet or'Toker1Ring
`physical
`address translation tables used by the Address Resolution Protocol
`Syntax
`[+;N [if_addr]] arp +;d inet_addr
`arp +;a %;inet_addr]
`inet=_addr ether_addr [if_=addr]
`Parameters
`—a
`
`[if_addr] arp +S;§
`
`(ARP).
`
`Displays current ARP entries by querying TCP/£PT—£finet:addrlP.
`is specified, only the IP and
`physical addresses for the specified computer are displayed.
`+—d
`
`lfinegaddr
`
`Deletes the entry specified by inet:addrinegaddr.
`—s
`
`Adds an entry in the ARP cache to associate the IP address ine%—ine addr with
`the physical
`address ether_addr. The physical address is given as 6 hexadecimal bytes
`separated by
`hyphens. The IP address is specified using dotted.decimal notation. The entry
`1S
`
`that is, it willwill not be automatically removed from the cache
`permanent,
`after the timeout
`
`expires.
`—N
`[if_addr]
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 195
`
`

`
`Displays the ARP entries for the network interface specified by if_addr.
`Ghapter—&&—UEilities—Referenee
`finger
`Syntax—Parameters
`‘EH19
`Syntax—Parameeers
`ether—efher addr
`
`Specifies a physical address.
`if: addr
`the lP;§ address of the interface whose address
`if present,
`Specifies,
`translation table should
`
`be modified. If not present,
`inetine addr
`
`the first applicable interface will be used.
`
`Specifies an IP address in dotted decimal notation.
`Troubleshooting TCP/IP
`QED
`2ofl8
`
`This connectivity command displays information about a user on aspeeifiedg
`specified system running
`the Finger service. Output varies based on the remote system.
`Syntax
`
`finger [—I]
`Parameters
`-1
`
`[user]@hesthosf [...L J
`
`Displays information in long list format+£ not supported on all remote
`systems.
`user
`
`Specifies the user you want
`display
`information about allali users on the specified host.
`@hest—hosf
`
`information about. Omit the user parameter to
`
`Specifies the host name or the IP address of the remote system whose users
`you want
`information about.
`
`Troubleshooting TCP/IP
`Hnger
`30fl8
`
`This connectivity command transfers files to and from aeempeeera computer
`running an ETP—servieeFTP sengice. Ftp
`can be used interactively or by processing ASCII text files.
`Syntax
`ftp [+—v]
`Parameters
`
`[+—n]
`
`[+—i]
`
`[+—d]
`
`[+—g]
`
`[host]
`
`[—s: filenameHlename]
`
`;¥
`—¥—Suppresses display of remote server responses.
`49-;
`Suppresses autologon upon initial connection.
`-1
`
`Turns off interactive prompting during multiple file transfers.
`—d
`
`Enables debugging, displaying all ftp commands passed.between.the client and
`server.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 196
`
`

`
`LQ
`:§—BisablesDlsables filename globbing, which permits the use of wildcard
`characters in local file and
`
`path names.
`host
`
`(See the glob command in the online Command Reference.)
`
`Specifies the host name or IP address of the remote host to connect to.
`—s: filenameHlename
`
`Specifies a text file containing ftp commands+£ the commands willwill
`automatically run after ftp
`starts. Use this switch instead of redirection (>).
`
`The following table shows the ftp commands available when.the-FfP£g§ service
`is installed on a
`
`Windows NT computer. For details about syntax for individual ftp commands,
`choose the ftp
`commands topic in the Commands list in Command Reference.
`FTP Commands in Windows NT
`
`Command Purpose
`;=Runs the specified command on the local computer.
`%——;g_Displays descriptions for ftp commands.
`? is identical to help.
`Troubleshooting TCP/IP
`ftp
`4ofl8
`
`append. Appends a local file to afilea file on the remote computer using the
`current
`file type setting.
`ascii Sets the file transfer type to ASCII, which is the default.
`bell Toggles a bell to ring after each file transfer command is completed.
`By default,
`the bell is off.
`binary
`b e
`iiaii.
`Sets the file transfer type to binary.
`bye——Ends the FfP§g§ session with the remote computer and exits ftp.
`ed——Changes the working directory on the remote computer.
`c