Hi,
I''ve taken on a new client and dont know squart about Lotus/Domino6 Server. For now I do have to manage the thing...
I have a short list of dumb-ass questions, hence the large points offer...
1. If a user has the lotus client installed and connects from home, when opening it connects to an internet host name... How to I change this on the client?
(Please try to provide instructions I can give to an end user, if possible)
2. If a user uses pop/smtp to the Lotus server, how do I change the password? -Internet password settings?
3. In exchange, you dont have to know the users previous password to change it, how do you do the same thing in Domino?
a. check CONNECTIONS section in local names.nsf to see if there is a defined priority address to connect to that server
b. if already connected to home server, ask home server if it has a defined priority address
c. if no priority way, repeat A and B for low priority ("backup") network addresses
d. if all the above fail, try resolving server's common name in DNS (e.g., Domino1/HouseNet, it would try to connect over TCP/IP to host Domino1, which, depepdning on DNS setup, might try hosts files, domino1.com, domino1.yourcompany.com, etc.)
e. failing that, if the client has a "passthru" server deifned in it LOCATIONS section in names.nsf, try to connect to passthru server, and ask passthru to proxy through to that server
Most likely, you need to open CONNECTIONS and look for a connection defined for that server, with the correct host name or IP address defined on the last tab of the connection. Select File->Mobile->Server phone numbers (it isn't just phone numbers), and see if the server is defined. If not, add a connection.
#2a) If using the Notes lcient as a POP/SMTP client, it configures similar to Outlook or Outlook Express. There is an ACCOUNTS section in names.nsf. Do FILE->SERVER-LOCATIONS, then on the left, click ACCOUNTS. Open the POP or SMTP account, and edit the password field.
#2b) If you are refering to Domino as a POP3/SMTP server for other clients, you change a user password in the Person record for that person, in the server names.nsf.
#3a) For internet protocols -- using a web browser to access a Domino application, or POP3/IMAP/SMTP to access mail, or an LDAP client, you change the person document's Internet Password (aka HTTP Password) field, as in #2b.
#3b) If you are talking about the Notes client ID's password, it works very differently. Client and server do not exchange password information. Instead, the user.ID file contains Public Key Certificates. The client tells the server, I am Joe Bloe, and the certificate issued by YOURCOMPANY proves this. Server says, I accpt YOURCOMPANY certificates, and by the way, I'm DOminoServer1, and this certifcate from YOURCOMPANY proves it, too. Client accepts server certificate, srver accepts client certificate, and all is well. The password is merely a way to protect the ID file.
So, what if you lose the password? Several things oculd happen:
1. If the certificates were set up with password recovery, then the authorized administrator ID (or sometimes combination of multiple authorized IDs) can unlock the ID with a new password. The Notes 6 password dialog includes an option to activate this feature. BUT, the ID must have been created with the recovery system in place, and frequently this does not happen. If you support Notes/Domino at this company, you should make sure that it is put in place for the future
2. Frequently, administrators store an original copy of all created .ID files, with password info. If you can find this, give the user a copy of the original .ID file, and you should be good. The old file might have expired, in which case you would have to renew it first.
3. Last option is to create a new ID with the same name. It will be fine, unless there is a document or database somewhere encrypted with the old ID. the new ID will match in name only, so anywhere names are used, the new ID will function teh same as the old (mail addresses, access control lists, groups for mailing, groups for access control, and other special "permissions"). But, if the user ever received an encypted message, that message is unloackable, and the user will never be able to read it, because the new .ID has different private key information.