ID:RS DESQview/X: Troubleshooting QCONNECT, RSH and REXEC
Quarterdeck Technical Note #197 Filename: RSH.TEC
by Al Huck CompuServe: RSH.ZIP
Last revised: 4/02/93 Category: NW
Subject: How to troubleshoot problems involving the RSH, REXEC, and QCONNECT
programs that are an integral part of DESQview/X's network support.
This technical note is designed to help you troubleshoot problems with RSH,
REXEC and QCONNECT. These troubleshooting procedures can be used for any
network transport that DESQview/X supports. You should also obtain a copy of
the technical note that is specific to your network transport. Refer to the
bottom of this note to see what network transport technical notes are
DESQview/X Network Compatibility Note
The following networks are compatible with DESQview/X version 1.1:
The following networks are compatible with DESQview/X version 1.1 when version
1.1 of the DESQview/X Network Manager is installed:
FTP Software, Inc. PC/TCP Release 2.03, 2.05 Patch Level 3 or later
Novell LAN WorkPlace for DOS v. 4.01 or later
Sun Microsystems PC-NFS v. 4.0 or later
Beame & Whiteside Networking Software v. 2.3 or later
Wollongong Pathway TCP/IP version 1.2.2 or later
HP/Microsoft LAN Manager v. 2.1 or later
If you do not have one of the above networks, you will not be able to run
a remote window inside of DESQview/X.
TROUBLESHOOTING PROBLEMS WITH REMOTE PROGRAMS
This technote contains a step-by-step procedure for troubleshooting
problems with running remote programs. Before going through the steps in this
technical note, you should power down your computer and power it back on.
This will completely clear the system's memory. This should be done to give
the system a fresh start.
*** STEP ONE ***
On this step, we are going to QCONNECT the Remote Machine. The QCONNECT
command will verify that the remote machine in running an X Windows display
QCONNECTING A REMOTE MACHINE
Open a DOS window by: selecting "O" for Open Window, then select "DW" for
DOS Window. Once the DOS window is opened, type in "QCONNECT
The QCONNECT command will check if the remote system is Running an X
Window display server, and a message will appear.
IF THE MESSAGE "AVAILABLE" IS RETURNED:
The Remote machine is running an X Window display server, your machine
can talk to it, and you should go to STEP TWO.
IF THE MESSAGE "THE DESQVIEW/X NETWORK INTERFACE IS UNAVAILABLE" IS
This means that the DESQview/X Network Manager is not loaded on your
(local) machine. Before you can run a remote program, the DESQview/X
Network Manager must be running. If you are not sure how to install the
Network Manager, please follow the instructions immediately below.
To install the DESQview/X Network Manager: Quit DESQview/X, then run
DESQview/X Simple Setup and select your network transport when the
networking portion appears. You should select all the defaults as
they appear. This will verify that you have the rights setup
properly for the local machine. After you have ran Simple Setup, load
DESQview/X and try to Qconnect the Remote Machine again.
NOTE: When running Simple Setup, if DESQview/X will NOT allow you to
select your network transport, refer to APPENDIX A. When starting
DESQview/X, if you get the error message "The DESQview/X Network
Manager Failed to Initialize", refer to APPENDIX B.
IF THE MESSAGE "UNKNOWN HOST" IS RETURNED:
It means that the name of the remote system and its "IP" Address is not
in your "HOSTS" file. For more information on the "HOSTS" file, refer
to "HOSTS" in the Index of the DESQview/X Network Manager manual. Refer
to APPENDIX C for additional steps you can take.
IF THE MESSAGE "UNAVAILABLE OR BUSY" IS RETURNED:
The remote system is not prepared to accept remote server connections.
If this is the case make sure the Remote Machine is using the same
protocol that is running on the local machine. IPX/SPX cannot connect
to TCP/IP, nor can TCP/IP connect with IPX. Both machines must run
either TCP/IP or IPX/SPX.
If both machines are running the TCP/IP transport, check if the two
machines can connect to one another through the "PING" command by typing:
"ping remote_system_name". You may have to find the PING program in your
network transport subdirectory. For example, using Novell LAN Workplace the
command is usually:
If you cannot "PING" the remote machine, your network transport is not
configured correctly. Until this problem is resolved there is nothing that
can be done with DESQview/X to solve the problem. Consult your network
transport's manual or contact your network administrator for help.
Quarterdeck has some technical notes available for some specific network
transports. Refer to the bottom of this note for a list of available network
transport technical notes.
For more information on using your network utilities, refer to your
network transport manual or refer to the end of this technical note for
availability to other technical notes related to your network transport.
If you can "PING" the remote machine successfully, it means that the two
machines can at least communicate with one another and you should try
QCONNECTing the Remote Machine while checking the availability of other
functions. Refer to APPENDIX D to see how this is done.
*** STEP TWO ***
At this point you are able to QCONNECT the remote machine. This means the
local machine and the remote machine are both running X Window display
servers. In this step, we are first going to load the Network Diagnostics
screen in a DOS Window, then we are going to run a remote program on the local
THE NETWORK DIAGNOSTICS SCREEN
Displays the number of available sockets, how many sockets are being used
and what sockets are currently being used. This screen will also display more
accurate error messages when you try to connect to the remote system.
To open the Network Diagnostics screen, run the DESQview/X Setup program
from the "ToolBox Menu". Once Setup loads, select the following menu items:
"Advanced Setup" (A), "Network Setup" (N), "Advanced Network Setup" (A) and
"Control Network Manager" (C). Set Control Diagnostics to "Sockets" and
press Escape. The DESQview/X Network Diagnostic screen will appear on the
screen. It has actually been running all along but hidden from view; this
command sequence makes it appear. Leave this window displayed and Switch to
the DESQview/X Setup window and exit out of Setup.
Now that you have the Network Diagnostics screen loaded, verify how many
sockets that are available on the local machine. To do this look at the
bottom of this screen. The following will be displayed:
TCP Open/Total: 3/24
This example tells me that I have 24 TCP sockets altogether and 3 of them
are being used. DESQview/X has to use a few sockets for itself. The more
services you enable, the more sockets DESQview/X uses for itself. Please make
sure that you have at least 4 sockets available before you try to RSH or REXEC
the Remote Machine. Some programs can use as many as 4 sockets, but for the
most part a program will grab 2 sockets to initialize and drop down to 1
socket once it has loaded.
If you do not have at least 4 sockets available, you must increase them
before you can continue. For example, if you are using Novell's LAN
WorkPlace for DOS, you can increase the total TCP sockets by increasing the
number of "tcp_sockets" in the "NET.CFG" file. When possible, you should get
the technote for your network transport. A current list of network transport
technical notes is at the bottom of this technical note.
Note: you should have a maximum of 32 sockets. The maximum number of 32 is
a combination of UDP sockets and TCP sockets. Make sure that the sum of UDP
sockets and TCP sockets are limited to 32.
Now that you have verified the amount of available sockets, let's RSH or
REXEC the Remote Machine. Go to STEP THREE.
*** STEP THREE ***
At this point we have the Network Diagnostics Screen in a DESQview/X
window. In this step we are going to run a Remote Program using the RSH or
RSH/REXECING THE REMOTE MACHINE
To run a remote program on the local machine, open a DOS window and type
in the following commands:
rsh barnacle -l login_name program -display local_host:0
rexec barnacle -l login_name program -display local_host:0
barnacle = The name of the remote system - use your own
login_name = Your user/login name [on the remote system]
program = The name of the program to run
local_host = The name of this machine; must be followed by a ":0"
You should also use lowercase letters because UNIX and many UNIX utilities
are case-sensitive and they are often set up for lowercase letters.
Note that much of the above line is normally optional since DESQview/X will
supply your normal login name and display. Troubleshooting usually involves
being very explicit in order to remove any ambiguities in the system.
Therefore, you should include all the above information in the command line at
You should also type in the whole path and program to run the remote
program. As an example, let's say you wanted to run "xterm" that is located
in "/usr/X11/bin" on a UNIX machine named "milo" and the DESQview/X machine
was named "opus". Your login name to "milo" is "steve". Here is the proper
command, if you do not have a password set up:
rsh milo -l steve /usr/X11/bin/xterm -display opus:0
Or if you are using a password:
rexec milo -l steve /usr/X11/bin/xterm -display opus:0
The above commands should open a new window on your display with the
program selected running in it. For more information on using the RSH or
REXEC commands, refer to "Remote Shell Command" in the Index of the
DESQview/X Network Manager manual.
If the RSH or REXEC command works, CONGRATULATIONS! You have successfully
run a remote program and you do not need to continue with this technical note.
If the RSH or REXEC command fails, proceed to STEP FOUR.
*** STEP FOUR ***
At this point, we just tried to run a Remote program and it failed.
IF THE RSH OR REXEC COMMAND FAILS:
First, make sure that the remote station has your user rights set up
properly. It must know the machines that are trying to connect to it and the
users who are using these machines. On DESQview/X machines, you can set up
user rights (the programs a user can use and the user's default directory)
using the Setup program. For more information on setting users' rights in
DESQview/X, refer to "USERS" in the Index of the DESQview/X Network Manager
On other X systems, user rights are set up in varying ways, depending on
the implementation. Consult your network administrator or the documentation
for your system.
If you do not have the user rights set up properly, you will not be able to
run a remote program.
If you have the user right set up properly, make sure that the Remote
Machine is running an X Window display server. It is possible that the Remote
Machine is NOT running an X Window display server, or it may have an X server
that is not permitted to communicate with other systems. It is also possible
that the remote machine may also not be running an X server at the moment.
This means that you will not be able to display remote programs to that
Another possibility is that one of your machines might have an "XHOSTS"
file. To verify whether you have an "XHOSTS" file on a DESQview/X machine,
type in the following commands:
The above commands will display all the files called "XHOSTS" in the
/DVX/BIN subdirectory. If this file appears, then you have an "XHOSTS" file.
THE "XHOSTS" FILE
The "XHOSTS" file contains a list of machines that have the right to
display programs on this one. If this file exists, the problem can be solved
by typing the following command on the machine where the program is going to
NOTE: if you are having problems displaying a remote program on the
DESQview/X machine, type in "XHOST +" while in the /DVX/BIN directory. For
more information on "XHOSTS", refer to "XHOSTS" in the Index of the DESQview/X
Network Manager manual.
After you have checked for "XHOSTS" files, try to RSH or REXEC the Remote
Machine again. Refer to STEP THREE to see how this is done.
If you are now able to RSH or REXEC the Remote Machine, you need to add
the Remote Machine name to the "XHOSTS". Once you have done that, the
problem is SOLVED and you do not need to continue with this technical note.
If the RSH and REXEC command still fails, try increasing the amount of
memory allocated for the Network Manager. To see how this is done, refer to
APPENDIX E. After you have increased the Network Managers memory, try to RSH
or REXEC the Remote Machine again. To see how this is done, refer to STEP
If you are now able to RSH or REXEC the Remote Machine, then the problem
is SOLVED and you do not need to continue with this technical note.
If you still cannot RSH or REXEC the Remote Machine, try renaming the
"INETD.INF" and "INETD.CFG" files and run DESQview/X Simple Setup. Refer to
APPENDIX F to see how this is done. After you have renamed the "INETD" files
and have run Simple Setup, restart DESQview/X and RSH or REXEC the Remote
If you can now RSH or REXEC the Remote Machine successfully, then the
problem is SOLVED and you do not need to continue with this technical note.
If you still cannot RSH or REXEC the Remote Machine successfully, you
should get the Quarterdeck technical note for your network transport (see the
list of notes at the end of this technote) or contact your network
administrator for assistance.
*** APPENDIX A ***
WHAT TO DO IF DESQVIEW/X SIMPLE SETUP WILL NOT ALLOW YOU TO SELECT YOUR
If you have a network that DESQview/X currently supports and DESQview/X
Setup doesn't recognize your network transport, it means that your network is
not configured properly. If this is the case you should obtain a copy of the
technical note for your network transport (check the list of technotes at the
end of this document) or contact your network administrator for further
assistance. See the additional contact information at the end of this note.
*** APPENDIX B ***
WHAT TO DO IF DESQVIEW/X SIMPLE SETUP WILL ALLOW YOU TO SELECT YOUR NETWORK
TRANSPORT, BUT YOU GET THE ERROR MESSAGE "THE DESQVIEW/X NETWORK MANAGER
FAILED TO INITIALIZE" WHEN YOU START DESQVIEW/X?
It is possible that the "DVP" file may be corrupt or not configured
properly. To correct this, edit the Network Manager's "DVP" file. To see how
this is done, refer to APPENDIX E.
If after you have gave more memory to the Network Manager's "DVP" file and
DESQview/X starts up without an error message, try QCONNECTing the Remote
Machine. To see how this is done, refer to STEP ONE.
If you still receive an error message when starting DESQview/X, try
renaming the "INETD.INF" and "INETD.CFG" files and run DESQview/X Simple
Setup. To see how this is done, refer to APPENDIX F.
If after renaming the "INETD" files and runing Setup and DESQview/X starts
up free of error messages, try QCONNECTing the Remote Machine. Refer to STEP
ONE to see how this is done.
If you still receive an error message on startup after renaming the
"INETD" files and running Setup, you should get the technical note for your
network transport or contact your network administrator or Quarterdeck
Technical Support at (310) 392-9701. A list of the available technical notes
for network transport is at the bottom of this technical note.
*** APPENDIX C ***
Try QCONNECTing the IP Address instead of the Host Name. This can be done
by typing "QCONNECT" followed by IP address of the remote machine you are
trying to contact. This test will check if the remote machine is running an X
Window display server without using the local HOSTS file or the Name Server.
If QCONNECTing the remote machine's IP Address returns the message
"Available", this means that the remote machine is running an X Window display
server. This also means that the remote machine's name and IP Address are not
in the local HOSTS file. If this is the case, add the name of the Remote
Machine and its IP Address to the local HOSTS file. This can be done in
DESQview/X Setup under "Manage Host List" on the "Network Setup Menu". Simply
add the following information:
After you make these changes, you should RSH or REXEC the Remote Machine.
Go to STEP TWO.
*** APPENDIX D ***
HOW TO CHECK THE AVAILABILITY OF OTHER FUNCTIONS ON THE REMOTE MACHINE:
Use QCONNECT /S[service] machine to do this.
QCONNECT /SFTP 127.27.1.23
The above command will check for and "FTP" service for copying files.
Similarly /SSHELL checks for a RSH capability (running programs from this
machine without a password); /SEXEC checks for EXEC (the ability to run a
program from the remote machine with a password). If you do not have SHELL or
EXEC capabilities, you will not be able to run a remote program.
For more information about services, refer to "Services" in the Index of
the DESQview/X Network Manager manual.
If you can QCONNECT successfully with the /SSHELL or /SEXEC, try to run a
Remote Program. Go to STEP THREE to see how this is done.
If you cannot QCONNECT successfully with the /SSHELL or /SEXEC, you do not
have your network setu p properly. At this point, you should get the
technical note for your network transport (if it is available -- see the list
at the end of this document) or contact your network administrator for further
*** APPENDIX E ***
At this point, the DESQview/X Network Manager is failing to initialize or
you cannot RSH or REXEC a remote window. It is possible that the Network
Manager may need more memory. On this step, we are going to edit the Network
Manager's "DVP" file and increase its memory.
To do this, open a DOS window in DESQview/X. At the DOS prompt, type in
Then type in one of the following depending on your particular network
DVPMAN LWP -- for Novell's Lan Workplace for DOS
DVPMAN IPX -- for Novell's IPX
DVPMAN IPXSPX -- for Novell's SPX
DVPMAN PCTCP -- for FTP's PC/TCP
DVPMAN WOLLONG -- for Wollongong's Pathway
DVPMAN BWTCP -- for Beame & Whiteside's BW-TCP
DVPMAN PCNFS -- for Sun PC-NFS
DVPMAN LANMAN -- for HP/Microsoft LAN Manager
Once the DVP Manager window appears, press the F10 key for advanced
options. Increase the "Maximum Program Size (in K)" to 400. Press Enter to
save the changes, then quit DESQview/X and start it up again. Go back to the
step that referred you to this Appendix.
*** APPENDIX F ***
At this point, the DESQview/X Network Manager is failing to initialize or
you cannot RSH or REXEC a remote window and you have tried increasing the
memory of the Network Managers "DVP" file. It is possible that your
DESQview/X Network Setup files are corrupt. On this step we are going to
rename the INETD.INF and INETD.CFG files and re-run Simple Setup.
These files are used to tell DESQview/X various information about your
network transport (Location of "HOSTS" file, the IP address of the Name
Server, etc.). By renaming these files and running Simple Setup, we are going
to force DESQview/X to reconfigure them. This can be useful if the files were
corrupt or set up improperly.
To rename the INETD files, you should first quit DESQview/X and type in
the following commands:
RENAME INETD.* INETD2.*
Once these files are renamed, change to the "\DVX" directory and run
DESQview/X Simple Setup and follow the prompts. After running Simple Setup,
restart DESQview/X and try to duplicate the problem.
CURRENTLY AVAILABLE NETWORK TRANSPORT TECHNICAL NOTES FROM QUARTERDECK
The following technical bulletins may help with the problem you are
QFAX BBS COMPUSERVE
---- ------------ ------------
IPX/SPX #253 DVXIPX.TEC DVXIPX.ZIP
QFAX (310) 314-3214 - Call from the handset of your fax machine.
BBS (310) 314-3227
COMPUSERVE "GO QUARTERDECK"
BIX "JOIN DESQVIEW"
TECH SUPPORT (310) 392-9701 - Voice
WHAT YOU SHOULD DO IF NONE OF THESE SUGGESTIONS SOLVED YOUR PROBLEM:
Finally, if none of the above works, note your findings carefully, prepare
all the information you can about your systems (including a Manifest printout
for any DESQview/X systems you are running) and contact your network
administrator or Quarterdeck Technical Support at (310) 392-9701.
* Trademarks are property of their respective owners. *
*This technical note may be copied and distributed freely as long as it*
*is distributed in its entirety and it is not distributed for profit. *
* Copyright (C) 1993 by Quarterdeck Office Systems *
************************ E N D O F F I L E *************************