1. Can't Modify a Locked Record

A locked record means that someone is accessing that record for update. The error message should give the name of the User accessing the Node. Possible solutions:

• You have locked yourself out because you have multiple browser windows open. Close all of them and relogin to NetDB.
• Another User is using the record right now. Since the User name is listed in the error message, you can contact that User by looking up their netdb record. Or you can wait - an inactive session will timeout after an hour.
• The database has not released the lock for some reason. Send mail to netdb-support@networking.

2. Session Time out

After an hour of inactivity, sessions are automatically terminated. Any unsaved changes that you have made on a record will be lost. If you still are logged into PC- or MacLeland, you will be returned to the NetDB home page with a red message saying that your session has timed out and this is a new session.

3. Can't Access a Record

The most common reason that Users cannot modify a record is that the record is not in the same Group as the User. The record was probably created by a User whose default Group is not the same Group as other Nodes on that Network. To fix this problem, send a note to your network consultant or to help@networking.stanford.edu.

4. Can't swap Node name with alias on same record

To swap name with alias on a Node, do the following:

1. Go to Modify Node page.
2. Rename Node to a name different from desired Node name or desired alias.. Remove Alias.
3. Save
4. Go back to Modify Node page. Put in desired Node name and desired alias.
5. Save

Why is this more difficult in NetDB3 than NetDB2? Take a Node where the name is A and the alias is B. Simply swapping A and B on the Modify Node page gives errors because a Node name and alias are quite different in the world of DNS (domain name service). In NetDB2, this would work because when B is removed from the alias field and the cursor is moved to the name field, B is immediately removed as an alias. However, in NetDB3, because of the stateless nature of HTML, B is not actually removed as an alias until the revised form is saved. NetDB3 thinks B is an alias and suddenly someone wants to use it as a regular name at the same time.

5. Can't remove User's default Group

Even if a User has all Groups and all records access, an active User must have at least one Group which is also the default Group. In order to remove this Group, the User must be inactive.

6. In the Node Custom Fields, why do I see "unknown administrator" or "unknown user"?

NetDB version 3 requires that people (Node users, Node administrators) be in the Stanford Directory. During migration of data from NetDB2 to NetDB3, if we could not find the Node users or Node administrators in the Stanford Directory, we would move the name into the custom fields. Since Node administrator is a mandatory field, the admin team "UNKNOWN" was used to fill the Node administrator field.

7. How do I sort Full Search results by IP address?

Currently, sorting by IP address is not supported in Full Search. It will be implemented in a later version. To get a list of nodes by IP address, search by IP address in Quicksearch.