This support document describes steps to debug connection problems in Qedit for Windows.
If connecting to an MPE machine using the Firewall Protocol you need to check and see if the qserver job is running.
Use the Server command of the Options menu and check that the MPE server filename points to the correct server program in PUB.ROBELLE (or PUBTRI in the case of some trials).
Use the Connections command of the Options menu and check that for each MPE connection, the word 'Hello' is not included as part of the login string.
Try to logon exactly the same way as the connection and see if you can run the named server program.
Is there a short expiry message?
If yes, then this is probably a Trial, and server mode is enabled.
if not, then logon as Mgr.Robelle and run extend,verify, you will be prompted for a file name, so please enter qedit.pub. In order to confirm that the HPSUSAN number matches and that you see an option #1.
One tricky case: If you're using Time Machine (or another Date Manipulating product), expiring versions of the Qedit program will fail. Note that the date software can be configured for particular user sessions, so be sure to login as that user when verifying that ther server program starts normally.
Another case (HP-UX only) of expired server is that the daemon hasn't expired when first run, but expired after it was started. This way, the initial daemon keeps running, but subsequent connections will fail when they try to start their own server process.
Stuck at "Waiting for Host Response"
The "waiting for server response" usually indicates that RPM was able to start a new session but the server program has not started, or aborted immediately. This usually displays a logon message on the console immediately followed by a logoff message.
Logon at a terminal or via Reflection using the exact same string used in the Hello text box of the Connection List dialog.
At this point, if everything is working properly, you will not see anything on the screen. Qedit simply displays a few empty lines. If there is any message, something has failed during the main server/listener initialization.
If you don't see anything peculiar, try to change the Connection in QW so it uses the Firewall Protocol. Make sure the port number in the Server Configuration dialog matches the number used on the Info string.
Try to open a file on that connection. Keep an eye on the terminal session for any error message.
"Unable to start MPE server because the supplied login was not valid"
This error can be returned when the session limit on the host has been exceeded. Check the session limit and session count.
i.e. always refuse network logins.
QW will only work if this is set to check(must supply session password) or allow(do not supply login password).
If so, it will allow "batch" logins only when initiated through STREAMX. Security/3000 incorrectly identifies QWIN connections as batch logins (this is a Security/3000 bug that was fixed in version 27.81128).
line in their SECURCON.DATA file. Commenting it out with "(* ...... *)" worked around the problem. This also was traced to a bug in Security/3000 which is fixed in version 2.7.x. If you have this problem, you should contact Vesoft for a new version, or a command file which works around the problem.
Another customer reported that if a user had devices excluded in their Security/3000 profile, then they could not connect.
On MPE, If security and server are ok, check whether the RPM process is running. On MPE/iX 5.0 and up, RPM is part of the OS. On MPE/iX 4.0, RPM is part of the NS/3000 product.
on the system console when trying to establish a connection, you should make sure the NSSTAT and NSSTATL services have been started. To do this, simply enter NSCONTROL STATUS.
There is a way to have these services started automatically by modifying the file NSMAST.NET.SYS. Warning: This is a sensitive area and you should contact HP's Response Centre before changing the file.
On some systems, there is more than one IP address going into the system. For example, one address for the DTC, and one for the machine. You should use the IP address for the machine.
When typing in IP addresses, do NOT use leading zeroes, because that means an octal value.
To check that the lowest level of connectivity is working, you need to "ping" from the client to the host and from the host to the client, first by the IP address and then by the name.
Ping on HP-UX 9.0 is usually found in the /etc directory. You can just type /etc/ping IP-address, but I usually prefer to specify the packet size and, more importantly, the number of attempts or packets being sent to the other computer, or in this case the client.
Ping on 10.0 is found in /usr/sbin/ping.
Most network tools are found in @.net.sys and @.arpa.sys. Ping on the 3000 is available in Ping.net.sys. Below is an example of running Ping on the 3000.
Typically ping for clients with Microsoft TCP/IP stacks is supplied with the networking software. Ping for 16-bit systems varies depending on the stacks being used.
If all else fails in terms of trying to connect, then we need to see more of your configuration and we've found the following checklist to diagnose various Networking issues. We would need output from the following various commands on the HP 3000.