LANsurveyor Responder Client Technical Details

All LANsurveyor Responder Clients use both TCP and UDP port 4347, but they work differently on Windows and Macintosh computers. These technical details describe the more important differences.

LANsurveyor Responder Client for Windows
LANsurveyor Responder Client for Windows is architected differently depending on the version of Windows on which it is running. If you are running Windows 95, 98 or ME, the LANsurveyor Responder Client is started as a background application when Windows is restarted. The background application is launched as the result of a Run Services Windows Registry entry.

If you are running Windows NT, 2000, 2003, or XP, the LANsurveyor Responder Client is started as a NT service. You can start, stop, and pause this service by using the Services Control Panel.

LANsurveyor can deploy NT service-based LANsurveyor Responder Clients using Active Directory. Refer to the LANsurveyor User's Guide for more information on deploying LANsurveyor Responder Clients.

LANsurveyor Responder Client for Mac OS X
LANsurveyor Responder Client for OS X is a Mac OS X daemon. It is run whenever the Mac OS X computer is running and does not have to have a user logged in.

LANsurveyor Responder Client for Mac OS
LANsurveyor Responder Client for Mac OS is a Mac OS INIT/Background Application. It makes use of AppleTalk's ADSP (AppleTalk Data Stream Protocol) and, optionally, TCP/IP (Transmission Control Protocol/Internet Protocol), which are connection-oriented protocols used to provide reliable, flow-controlled data transfer to and from the LANsurveyor application. LANsurveyor Responder Client for Mac OS requires System 7 and is compatible with Mac OS 8 and 9. It must be placed in the Extensions folder of your Mac OS machine in order to be loaded at System startup time.

LANsurveyor Responder Client for Linux
The LANsurveyor Responder Client for Linux is installed as a daemon and works even if no one is logged in to the machine. There are two different installers: an rpm installer for distributions that use rpm and a dpkg installer for distributions that use dpkg. Refer to the LANsurveyor Responder Client for Linux readme file in the LANsurveyor installation directory for more information.

Internet Protocol Specifications
The LANsurveyor Responder Client uses both UDP and TCP in order to communicate with the LANsurveyor management application. LANsurveyor uses UDP port 4347 to probe for LANsurveyor Responder Clients and TCP port 4347 to query and manage LANsurveyor Responder Clients.

Log File Maintenance
The LANsurveyor Responder Client creates and maintains a text log file of start and stop times and a record of every command received from a copy of LANsurveyor. This log file is called "LANsurveyor Responder Client Log" (NeonResponder.log for Linux) and its location depends on the OS version on which the LANsurveyor Responder Client is running:

• Windows 95/98: the Windows folder
• Windows NT/2000/XP: the WINNT folder
• Mac OS: the Preferences folder
• Linux: /var/log/

An exception to this Log File rule is found in the LANsurveyor Responder Client for OS X. This version of the Responder uses the OS X Console to which to log messages from the Responder. The OS X Console application is found in the Utilities folder under the Applications folder.