Re: Server accessible from other servers but not clients. -- DOMINO400

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Server accessible from other servers but not clients.
From: rob@xxxxxxxxx
Date: Wed, 23 May 2012 15:43:15 -0400
List-archive: <http://archive.midrange.com/domino400>
List-help: <mailto:domino400-request@midrange.com?subject=help>
List-id: Lotus Domino on the iSeries / AS400 <domino400.midrange.com>
List-post: <mailto:domino400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/domino400>, <mailto:domino400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/domino400>, <mailto:domino400-request@midrange.com?subject=unsubscribe>

I opened up my local names.nsf. I went into Advanced, Connections. Most
of my servers are not listed there. I pick one(GDDATA) that is not listed
there. I run the trace my my client. Success. Try a trace of TRAVELER01
again. Failure. It says it is trying to look it up on GDISYS01 (my home
server).

I tried trace traveler01/dekko on gdisys01 and it works

There's no connection document pointing either way between GDISYS01
from/to GDDATA either. Not that it should matter. Just wondering why a
client trace fails to TRAVELER01/DEKKO but works to GDDATA/DEKKO. Wondered
if it was looking for connection documents on my home server (GDISYS01) to
TRAVELER01 or GDDATA. Not that.

Rob Berendt

Follow-Ups:

Re: Server accessible from other servers but not clients. , Walter Scanlan

This mailing list archive is Copyright 1997-2026 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.