First, ignore the error messages on the client. They rarely point to the correct problem. Do a DSPMSG QSYSOPR. Look for an error message related to the device name. Look at the details. If it says the prestart job has ended or is ending, look at the joblogs for the prestart jobs. They're probably ending with the message "user XXXXX is not authorized to a library in the library list". XXXXX is usually QUSER. This user must have authority to all libraries in the library list. If it says "user is not authorized to device", hit F9 for more details. Look at the user name (probably QUSER). You need to give this user at least *USE authority to this device. I've noticed that recently all logon errors are all giving "password is not correct", where system errors used to give "licensed system SXXXXXXX is not available". Not very helpful…

---

Perhaps you are using Windows 95 password caching. In that case the password that is sent to your AS/400 is writtem in a file BOB.PWL in the Windows directory. Delete this file and try again…

---

There was a problem similar to this when we upgraded from I believe V2.3 to V3.1. It had to do with passwords that were "old" in terms of OS/400 version. The "fix" was to reassign a new password temporarily, then have the user signon with that password, they could then change it back if desired.

---

Here comes some small ideas: - Have you run the STRHOSTSVR-command on the AS/400 ? - Are the user in the system catalogue (WRKDIRE) - Try also to check the joblogg to see if it says anything.

---