HP t1000 T1500/T1510 Windows-based Terminal Network Installation Guide - Page 45

Edit Command, Username, Configuring Server Application Resources

Get HP t1000 - Terminal Thin Client PC PDF manuals and user guides View all HP t1000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

Configuring Server Application Resources 31 Note RSH support is not available from Windows NT servers. Even if X clients are installed on NT, RSH support must be available from other server(s) for the X Manager to be able to launch them. The X Manager is the terminal's interface to RSH; on the server the following must typically must be configured for RSH support: Note For exact details refer to the manuals on your server. First, rshd (or the equivalent) must be configured to respond to requests for application launching. Do this by modifying inetd.conf as appropriate for your system, or by running the appropriate system configuration tool. Second, the server must be able to resolve a name from the IP address of the terminal. If the terminal IP address-to-name mapping is provided by DNS, nothing needs to be done. Otherwise, the server's /etc/hosts (or equivalent) file must be modified to contain the name that the terminal reports it has for that IP address. If DHCP services are used, but dynamic DNS (DDNS) is not in use, it may not be possible to construct a static table that correctly matches name and current IP addresses. If the terminal has a domain name, the name that matches the terminal's name will typically have the domain name as well. Third, you must decide on how you are going to run the program. There are several approaches. There can be a one-to-one relationship for all terminal users to server users or there can be a many-to-one relationship for all terminal users to server users. The approach chosen will have many implications in the areas of security and privacy, and the choice should be made carefully. In the first case, you will need to provide accounts on the server for every terminal user. In the second case, you will need to provide a generic account on the server and have all X Manager sessions go through that account. For the one-to-one case, the entry in the X Manager Edit Command dialog box Username field should be self. For the many-to-one case, the entry should be the chosen account name. After creating the account or accounts on the server, the .rhosts file in that account must contain the names of all users and terminals allowed to use that log in. The .rhosts file must be owned by the server user, and contains lines of the form terminaluser

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
Configuring Server Application Resources
31
Note
RSH support is not available from Windows NT
servers. Even if X clients are installed on NT, RSH
support must be available from other server(s) for the X
Manager to be able to launch them.
The X Manager is the terminal’s interface to RSH; on the server the following must
typically must be configured for RSH support:
Note
For exact details refer to the manuals on your server.
First,
rshd
(or the equivalent) must be configured to respond to requests for
application launching. Do this by modifying
inetd.conf
as appropriate for your
system, or by running the appropriate system configuration tool.
Second, the server must be able to resolve a name from the IP address of the
terminal. If the terminal IP address-to-name mapping is provided by DNS, nothing
needs to be done. Otherwise, the server’s
/etc/hosts
(or equivalent) file must be
modified to contain the name that the terminal reports it has for that IP address. If
DHCP services are used, but dynamic DNS (DDNS) is not in use, it may not be
possible to construct a static table that correctly matches name and current IP
addresses. If the terminal has a domain name, the name that matches the
terminal’s name will typically have the domain name as well.
Third, you must decide on how you are going to run the program. There are several
approaches. There can be a one-to-one relationship for all terminal users to server
users or there can be a many-to-one relationship for all terminal users to server
users. The approach chosen will have many implications in the areas of security
and privacy, and the choice should be made carefully. In the first case, you will
need to provide accounts on the server for every terminal user. In the second case,
you will need to provide a generic account on the server and have all X Manager
sessions go through that account. For the one-to-one case, the entry in the X
Manager
Edit Command
dialog box
Username
field should be
self
. For the
many-to-one case, the entry should be the chosen account name.
After creating the account or accounts on the server, the .
rhosts
file in that
account must contain the names of all users and terminals allowed to use that log
in. The .
rhosts
file
must
be owned by the server user, and contains lines of the
form
terminal<space>user