×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
if I nslookup traveler01 from the client it's unsuccessful.
if I nslookup traveler01.dekko.com from the client it's successful.
if I nslookup traveler01 from the os of the notes01 server it's
unsuccessful.
if I nslookup traveler01.dekko.com from the os of the notes01 server it's
successful
Why is the server able to run the trace and not the client? It's like the
server knows to read traveler01's server doc and see
that the netaddress is traveler01.dekko.com but the client doesn't read
that field.
Makes it a real mother to have names.nsf open on NOTES01/DEKKO and click
File, Replication, Replicate and try to replicate to TRAVELER01/DEKKO. It
tells me to run the trace and gives up.
User situation: User changes 'internet password'. Can't use iPhone. Help
desk tries to hurry replication by replicating names.nsf. ..it hits the
fan.
work around: Create connection document to replicate between notes01 and
traveler01 every 15 minutes.
First time I ran: replicate traveler01/dekko names.nsf there was a few
pushes/pulls/updates.
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
