Remote Access Problems

There are two basic symptoms of remote Calendar Manager access problems:

• You try to browse a remote calendar where you think you have Browse access, and all you can see are appointment times.

• You try to insert, delete, or change an appointment on a remote calendar where you think you have access, and Calendar Manager gives you an Access Denied... error message in the footer of the Appointment Editor.

There are three things you can check to try to fix these access problems:

1. If you are using the NIS or DNS system, which uses the concept of mail domains, make sure you are trying to browse a calendar in your domain or that you have specified the domain in your browse list. For example, if you are trying to browse the calendar of user Rob in your domain, you can simply specify Rob@host. If you are in a domain called Eng, and Rob is in a domain called Corp, you need to specify rob@host.Corp in your browse list.

2. Make sure that the owner of the remote calendar has really given you Browse, Insert, and/or Delete access.

   In order for the access to occur, make sure both of these conditions are met:

   1. Names in the access list must take the form user@host or just user. (Note that if the name in the access list is just user, access is given to anyone on your network with that user name.) If you are using the NIS or DNS system, make sure your name in the access list is not listed in the form user@domain or user@name.domain.

   2. The owner of the calendar must remember to click SELECT on the Apply button on the Access List and Permissions Properties window.

      Check the user ID and group ID on both your workstation and the remote workstation. The user ID and group ID must be the same in both locations.

3. Determine your user ID and group ID on each workstation as follows:

   1. Look for your password entry in the file /etc/passwd.

      If you have an entry in this file, the user ID is the third field (the number between the second and third colons). The group ID is the fourth field (the number between the third and fourth colons). For example, if the entry for user Egret in the /etc/passwd file is:

      egret:X4y8r2Bg:3286:10:& West:/home/egret/:/bin/csh

      the user ID for user Egret is 3286, and the group ID is 10. The values of the user ID and group ID should be between 0 and 32767.

   2. If you are using the NIS system, and you do not have an entry in the file /etc/passwd and the last line of /etc/passwd starts with a `+', check for an entry in the NIS passwd entries. To determine your NIS user entry, type ypmatch username passwd in a Command Tool or Shell Tool.

      For example, to find the NIS password entry for user Egret, type:

      ypmatch egret passwd

      If the system responds with a user entry, the user ID is the third field, and the group ID is the fourth field.