The Ataman™ Rlogind Service
Yüklə 209,44 Kb. Pdf görüntüsü
|
- Bu səhifədəki naviqasiya:
- 10.4.4 Screen buffer size limits.
- 10.4.5 Manual resize necessary when screen buffer size is changed on the server end.
- 10.5 Using the Rshd and Rexecd Services
- 10.6 Using the Command Line-Based Tools
- 11. Programming Considerations
- Do not try to use the getch() or kbhit() routines supplied by your compiler vendor. Those routines are usually not designed to work with pipes.
- 12. Troubleshooting / Technical Support 12.1 Where to Begin 12.1.1 Event Log
- 12.2 Known Problems and FAQ 12.2.1 Summary of permissions requirements for the ATRLS.
- 12.2.2 Remote users use CPU time even when they are idle.
- 12.2.3 User does not have permission to logon.
- 12.2.4 Running a text editor or program clears the screen and appears to hang.
- 12.2.5 Use of client-side screen “scroll-back” does not work.
- 12.2.6 Process terminated immediately, probable CreateProcessAsUser failure.
- 12.2.7 With rshd/rexecd program exits immediately with no output.
- 12.2.8 Rcp of extremely large files fails.
- 12.2.9 Version 3.X and newer doesn’t have the Environment File option
- 12.2.10 rshd: (user1/user2@host)
- 12.3 Contacting Ataman Software’s Technical Support
- 12.4 Ataman’s World Wide Web Site
Not Implemented. On real VTXXX terminals sequence, so there is no standard for a corresponding sequence. If you need to send F5, try using ^A5 as in the table above. Note: Terminal emulators often differ on the definition of VTXXX keys. Therefore, your client program may not match our set. The arrow keys work with nearly all emulators. 10.4.4 Screen buffer size limits. Due to both the method used to copy the console screen buffer to the remote screen and an internal limit in a Win32 API call used to perform the copy, screen buffer sizes are limited to a maximum of 60 lines and 128 columns. If the Ataman Telnetd Service or the Ataman Rlogind Service is used via slower links (for example over a 14.4K modem), performance will be best when using smaller screen buffer sizes. 10.4.5 Manual resize necessary when screen buffer size is changed on the server end. The rlogin and telnet protocols do no allow a server to communicate a window size change to a client. Thus, if you run a DOS or OS/2 character mode application (which can automatically cause screen buffer size changes) or use an application that explicitly changes the size of the screen buffer (i.e. the “mode con” command), you must manually resize the client to match the change in the screen buffer size. If your rlogin or telnet client program implements resizing the client window, it will be passed to the rlogind/telnetd service. The remote screen buffer will be resized to match the client. To check the size of your remote screen buffer use the “mode con” command with no additional arguments. 25
10.5 Using the Rshd and Rexecd Services The Rshd and Rexecd services are used by invoking an rsh or rexec client program of your choosing. The discussion in the User Environment section for the rlogind and telnetd services above applies to the rshd and rexecd services too. 10.6 Using the Command Line-Based Tools The ATRLS provide 4 command-line-based tools: AWHO.EXE, AKILL.EXE and REXEC.EXE. You will need to cause your PATH variable to point to the directory where these tools are stored, or else switch to that directory when you run them. The AWHO.EXE program lists the users currently logged-on to the ATRLS. The “-a” flag provides more detail. The AKILL.EXE program terminates a logon session. It takes a session id argument. The session id arguments are listed by the AWHO.EXE program. Alternatively, the argument “all” causes all current logon sessions to be terminated. The REXEC.EXE program is a client program that works with the rexecd service. The client program is similar to the one provide with Windows except that it has a -p flag which allows you to specify the password from the command-line. WARNING: Users with debug privileges will be able to see this password information in running programs. Also be careful with the security settings of any files which store this password information. Execute REXEC.EXE with the -? flag for a usage message.
A substantial number of our clients use the Ataman TCP Remote Logon Services (ATRLS) in conjunction with hand-held radio frequency terminals. These users typically write their own software and need assistance with making their software work with the ATRLS. This section answers most commonly asked questions. • If you generate your own escape sequences, you want to use Simple Mode. Advanced Mode generates its own escape sequences recreating the contents of the console screen buffer on a remote host. These escape sequences will interfere with escape sequences that you generate. • It is now possible to send bell characters in Advanced Mode. See Sending Bells in Advanced Mode for information on how to enable this feature. The discussion below assumes you have chosen 255 as your bell character. Because of the way that Advanced Mode works (screen scraping), you must generate the bell character in a special manner: 1. The bell character is interpreted only on the top line of the console screen. Thus to use it, you must first position to the top line. This is to prevent repeated beeps caused by line scrolling. 2. You should avoid character scrolling within the top line of the console screen. If you cause the screen locations containing bells to move, the bell characters may be resent. 26
3. Because Advanced Mode works by screen scraping, it is important that you change a screen location each time you want to sound a bell. The following pseudo-code demonstrates a good way of doing this: static int flip = 0; MoveCursor(0, 0); if (flip == 0) then print “ \xff”; # \xff in hex is 255 decimal flip = 1; else print “\xff “; flip = 0; endif
The idea is to use two screen locations. Each time a bell is generated, alternating locations are used to print the new bell and to erase the previous bell by overprinting it with a space character. • Simple Mode works by setting the standard handles to pipes. Some programming environments handle pipes differently from consoles. The most common difference is the tendency to buffer pipes. Please consult the programming environment documentation to discover how to override this buffering, since it will interfere with user interaction. In ANSI C, this is done with the setvbuf call. setvbuf(fp, NULL, _IONBF, 0); • Simple Mode is configured from the Prompts Page of the ATRLS Control Panel. • In Simple Mode, if your program needs to do character-at-a-time input (as opposed to line-at-a-time input), you will need to input using Win32 API calls. Do not try to use the getch() or kbhit() routines supplied by your compiler vendor. Those routines are usually not designed to work with pipes. The file SAMPLE.CPP contains sample source code of a working program that shows escape sequence output to stdout and character-at-a-time I/O from standard input. This file contains sample _kbhit() and _getch() subroutines using the appropriate Win32 API calls.
The ATRLS report error messages to the Application Event Log. This log can be viewed using the Event Viewer application, which is usually launched by double-clicking its icon. 27
The icon is found in the Program Manager group under Administrative Tools. The Application Event Log must have a check mark beside the Log menu entry to be selected. All ATRLS entries begin with the tag “Ataman”. Most of the error messages are self- explanatory. If an error message requires explanation, please do not hesitate to send electronic mail to technical support (support@ataman.com). On rare occasion, you may have a service failure. These are logged by the Service Control Manager in the System Log. If you are having compatibility problems with a client program, it may help to enable tracing. See the Enable Tracing section for details.
• CMD.EXE (or other if you have overridden default command processor): • Readable by System account. • Readable by user accounts used for telnet. • Home directories of incoming users: • Local to machine. • Readable by System account. • Readable by user. • Files of the ATRLS: • Full Control by System account. • Readable by user accounts. • All paths above must be searchable by telneting user accounts and the System account. • The ATRLS service must run under the System account. 12.2.2 Remote users use CPU time even when they are idle. This message occurs only when using rlogind or telnetd in Advanced Mode and is not a problem, but an artifact of providing full-screen support. Windows does not provide inherent remote full-screen support but does provide the ability to read a screen’s current contents. Advanced Mode examines the screen periodically to monitor any changes. If the CPU usage by remote users produces a heavy load than consider switching some remote users to Simple Mode.
By default, the Windows Server does not allow normal users to logon. See if this is your problem by using the failing user account to logon to the main console (i.e. logon normally). You can override Microsoft’s default by using the User Manager for Domains to give the user account the right “Log on locally” as follows: 28
• Run the User Manager for Domains program located in the Administrative Tools program group. • If the server, for which you are setting the rights, is a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), skip to the next step. Otherwise, it is necessary to tell “User Manager for Domains” that you want to set rights for the server machine, not the domain. To do this, select the Select the Domain item in the User menu. In the dialog box where it says “Domain:”, type “\\MachineName” where MachineName is the host name of the system, which you wish to edit privileges. When you push the OK button, you can edit the privileges for that system • Select the User Rights item in the Policies menu. • Scroll the “Right:” drop-down list until you get to “Log on locally” entry. • Add those users or groups you wish to allow to logon. • If your server is not a BDC, you are finished. • If your server is a BDC, run the Server Manager for Domains program located in the Administrative Tools program group. • Select the Synchronize with Primary Domain Controller item in the Computer menu. 12.2.4 Running a text editor or program clears the screen and appears to hang. Probably the program in question is using an Alternate Screen Buffer (a Win32 Console API feature). The ATRLS is unable to read the alternate screen buffer. Common editors with this problem: GNU emacs and some ports of “vi” clones. In both instances, you can find free (but unsupported) ports of similar editors on our web site that do work with our services. (Source code as well as Intel binaries are provided.) 12.2.5 Use of client-side screen “scroll-back” does not work. This is a side effect of the Advanced Mode. Essentially Advanced Mode takes periodic snapshots of a console screen buffer and sends ANSI escape sequence across the network to duplicate the screen remotely. This is necessary since Windows only provides this method to intercept console I/O. Unfortunately using this method means that scroll-back buffers in the client programs are not used, since scrolling never occurs. 12.2.6 Process terminated immediately, probable CreateProcessAsUser failure. We cannot give you an exact diagnosis of the problem because Windows does not return an error from the CreateProcessAsUser() API call when the problem occurs. Here are the possibilities that we know of: 1. You are out of some system resources, most commonly, window stations (under Windows Server you may only have about 15). If you suspect this is the problem, see: Increase number of simultaneous connections . 2. The Windows system file: User32.DLL had an initialization failure, see Microsoft Knowledge Base Article Q142676 for fix you can make in the Windows registry.
29 12.2.7 With rshd/rexecd program exits immediately with no output. Probably it is the same problem as Process terminated immediately, probable CreateProcessAsUser failure. . Because the CreateProcessAsUser() API call does not return an error indication, there is no way for us to warn you that this has occurred. 12.2.8 Rcp of extremely large files fails. Our rcp server actually does support 63-bits of file size, unfortunately most rcp clients do not support more than 31 bits of file size (2 gigabytes). There is no real standard for rcp. Should you find a client rcp that claims to support extremely large files but does not work with our rcp server, please let us know!
Since we now automatically load the user’s registry and environment, the functionality is not useful to most users. However if you do find you really do need that functionality, you can achieve it by: 1. Change the environment file to a series of SET commands. 2. Save it as ENVVARS.CMD in the user’s home directory (other directories can be used if desired). 3. Configure the user’s command processor options as follows: Interactive Command Processor: %COMSPEC% /K CALL %HOME%\ENVVARS.CMD Batch Command Processor: %COMSPEC% /C CALL HOME%\ENVVARS.CMD&%COMMAND% 12.2.10 rshd: (user1/user2@host) Access denied.User2 needs user1@host added to its Host Equivalent List. See Host Equivalence List for details. 12.2.11 Cannot find control panel icon on an x86-64 machine (XP/2003 64-bit). The ATRLS are still 32-bit applications. You can find the icon by looking in the Control Panel folder named “ View x86 Control Panel Icons”. 12.3 Contacting Ataman Software’s Technical Support Free technical support is provided exclusively via electronic mail. From the Internet use: support@ataman.com . IMPORTANT: Our biggest problem in providing technical via electronic mail is receiving invalid return addresses. If your local mailing system does not automatically provide it, please give a standard return address as part of your message. In all cases, please list your telephone number so we can still reach you in the event of electronic mail failure.
30 Bug fixes are worked into minor releases that are distributed on our world-wide web site: http://www.ataman.com You may also obtain the latest version from Ataman Software for a distribution fee. You only need to obtain one copy to upgrade all the copies for which you have a license. Your registration code will work with all minor version releases that have the same major version number as the software you originally licensed. Only the latest major release version is eligible for full technical support. When a new major version is released, support for the old version will be phased out over a 6-month period. We reserve the right to charge for technical support for copies purchased 1 year or more earlier. We reserve right to limit the number of people contacting us for support from site licenses and large volume purchases (> 200 copies). (We expect your internal support to provide first-line technical support to your end users, with your technical support people contacting our technical support people.)
Not sure if you have the latest version? Check out our World-Wide-Web site: http://www.ataman.com 13. Ordering the ATRLS The latest ordering information can be obtained from our website: http://www.ataman.com 31 Document Outline
Yüklə 209,44 Kb. Dostları ilə paylaş:
|