Key Concepts 95The end station stage attempts to determine an end station’s type byperforming the following steps:1 Attempting to start a Telnet session with the device and subsequentlyparse the Login banner if the Telnet service is supported.2 Determining if the node is operating as a file server. This is achieved byattempting to connect to the device via TCP port 2049.3 Determining if the node is operating as a print server. This is achieved byattempting to connect to the device via TCP port 515.4 Using Microsoft Windows API calls to obtain the Windows operatingsystem information, provided the node is a member ofdomain/workgroup.Web Type RecognitionCertain 3Com devices have Web (HTTP) management interfaces but donot support SNMP. Some of these devices identify their type using ahidden tag in their home page. For devices that have been recognized assupporting HTTP but not supporting SNMP, 3Com Network Director looksfor this tag in order to recognize the device.DNS Name ResolutionDuring this stage 3Com Network Director attempts to retrieve a DNSname for each IP address that has been detected. 3Com NetworkDirector uses information from the Windows registry in order to establishpotential DNS servers that exist. It then communicates with them directlymaking DNS queries using UDP.NBX Phone DetectionThis stage obtains detailed information about any Network BrancheXchange (NBX) devices that were discovered as part of the Web TypeRecognition Stage.The Network Discovery wizard allows you to specify the IP addresses ofindividual NBX call processors (NCPs) on the network, and a separateusername/password for each.This stage is required because the NBX chassis and phones do not supportSNMP. Many of the phones will not have IP addresses and consequentlywill not respond to a ping. The NBX chassis contains a non-visible Webpage which 3Com Network Director downloads using HTTP. The pageprovides 3Com Network Director with a list of phones that are associated
