Versuche einmal das
Potential problem one:
If the server's previous IP address is stored in any Server Connection Document or Server Document, when that server's IP address is changed in DNS and on the server itself, these old Server Connection documents or Server documents will cause connection failures.
Solution:
Use the DNS fully-qualified domain name, not the IP address, as the network address stored in the Server Connection Document and Server Document. You can then change the server's IP address in DNS without having to change the Server Connection Document or Server Document. Changing the network address from the IP address to the DNS name can be done at any time.
To modify the Server Connection Document --> Basics panel, if Local Area Network is chosen in the Connection Type field, click the Advanced panel and check the entry in the Destination server address field. If the field contains the server's IP address, delete the IP address and enter the fully-qualified domain name. Remember, both the server-based Domino Directory and the client-based Address Book can have this problem.
To modify the Server Document --> Ports panel --> Net Address for TCP ports, if the field contains the IP address, change the entry to the proper fully-qualified domain name.
Potential problem two:
The algorithm that all Notes clients and Domino servers use to connect to a Domino Server can cache the IP address that was used to successfully connect to a server. If this cache entry exists, when the server's IP address is changed, the old cached address may be used causing the connection to fail. This cache is called the Notes Name Service Cache (NNSC).
It is important to understand why caching is performed. Notes supports a wide range of networking technologies implemented as Notes ports. If Notes attempts to connect to a server that is down and tries every possible technology (Notes port), using every possible Name to Address resolution tool until each one fails, the connection attempt takes a long time. To prevent the long delay that would occur in reporting the error when the server goes down, Notes implements two server connection algorithms. One algorithm is fast and uses cached addresses, while the other is slower and uses the complete algorithm which bypasses the cache when it fails.
Solutions:
One of the following solutions may resolve this problem. Solutions are listed in the order they should be tried:
-- The fast connection algorithm is only used if the client or server successfully connected to the same server earlier in the day. If a successful connection has not yet occurred today, the slower algorithm is used and the cache is bypassed. To avoid this problem, change a server's IP address late in the evening but before midnight. This is the easiest solution because it is transparent to the user and involves no help desk calls or any action on the user's part.
-- The cache is rewritten following successful connection to the server. The cached address is the address entered by the user, not the resolved IP address. Therefore, if users have the habit of connecting to server/acme by entering "server.acme.com," the cached address will be server.acme.com, not 1.2.3.4 and the problem will not occur.
-- The cache is rewritten following any successful connection to the server. If a user tries to connect to the server by its Notes name (for example, server/acme), the stale cache entry is used. If a user tries to connect using the server's fully-qualified domain name (for example, server.acme.com), then the cache will not be used, the new address will be fetched from DNS, and the correct new address will be entered in the cache. To make this successful connection using the fully-qualified domain name of the server, use the File --> Database --> Open menu command, or the File --> Preferences --> User Preferences --> Ports --> Trace service menu command.
-- The cache is stored in the following fields in the Location Document for the Notes client and in the Server Document for the server:
• $Saved Addresses
• $SavedDate
• $SavedPorts
• $SavedServers
• $SavedTriedDate
If these fields are deleted from the Location or Server Document, the old IP addresses in the cache cannot be used. This method can be confusing because the Notes items are rewritten when the client or server exists from an in-memory copy. Therefore, to use this method to clear the cache for the client, create the agent in the Local Names & Address Book (NAB) and then switch to the Island Location document and exit the client. Restart the client and then run the agent to clear the cache for all other locations. Switch to your normal location.
Sample agent formula language code to clear the cache:
• FIELD $SavedAddresses:=@DeleteField;
• FIELD $SavedDate:=@DeleteField;
• FIELD $SavedPorts:=@DeleteField;
• FIELD $SavedTriedDate:=@DeleteField;
• FIELD $SavedServers:=@DeleteField;
• SELECT @All
-- As a last resort, disable the use of the cached addresses by using the following notes.ini setting: DONT_USE_REMEMBERED_ADDRESSES=1
NOTE: If the client uses multiple or slow port technologies, Product Development discourages the use of this technique because it can cause a long delay in reporting that a server is down.
