I’m wondering if others have encountered this issue: Since upgrading to R7.02 from 7, I’ve noticed that when I switch my Notes client to a new Location and try to connect to a server that I had connected to on the previous location, but with another address, the client insists on trying to connect to the server using the “last known address” and repeatedly fails.
Here’s a scenario. Work all day at the office on internal network using laptop. Have a location document (“Office”)for internal network that uses a connection document for that server with the internal network address for that server of “server.internal.local” let’s say. Then go home with laptop and bring up Notes and switch to the “Home” Location. There is another connection doc in my NAB for this same server that’s available to the “Home” location that lists the address as “server.companyname.com”, which is it’s name available outside the company firewall. These connection documents are only available to the corresponding location docs that would use them.
After upgrading to 7.02 I’ve noticed that (in the above example) when I switch to the “Home” location, Notes keeps trying to connect to the server using the “last known address” of “server.internal.local”, even though I’ve switched the location and the connection document that uses that address is no longer available to the new location. I don’t know where it’s storing this address, but I can’t seem to find a way to “clear” it. Restarting doesn’t help.
The only way I’ve been able to “reset” it, is by going to the replicator page and forcing it to try to replicate my local DB’s and fail, and then when it’s finished, force it to replicate again. On the 2nd pass it apparently gets the correct address and connects. Also, if you force a “Trace” to the server from the User Preferences it will cycle through the connection docs and eventually make a connection.
Anyone else encounter this or know how to easily “flush” the last known address?