Re: Weird problem

[rob@xxxxxxxxx]

I too had a similar situation recently.  And it had more to do with a 
change in our Domain Name Servers.  I could ping it from i5 but couldn't 
TRACE it from Domino.
First, however, I would check your Server documents, Ports tab, and ensure 
that it was using the exact same name in "Net Address" as you are using in 
the ping command, including any domain appended.  Actually found a few 
that had IP addresses instead of names.
You should have multiple DNSs set up.  If you have one on the far side of 
the comm that is listed first in 
CFGTCP, option 12
and when the comm dropped, it started using a local one (which may not 
have all names entered in it, etc) then that might be an issue also.

> trace gdisys02.dekko.com 
 
Determining path to server GDISYS02.DEKKO.COM 
Available Ports:  TCPIP 
Checking normal priority connection documents only... 
Allowing wild card connection documents... 
Enabling name service requests and probes... 
Checking for GDISYS02.DEKKO.COM on TCPIP using address 'GDISYS02.DEKKO.COM
  Requesting IP Address for GDISYS02.DEKKO.COM from DNS 
  DNS returned address 10.10.1.131 for GDISYS02.DEKKO.COM 
  Requesting IP Address for GDISYS02.DEKKO.COM from DNS 
  DNS returned address 10.10.1.131 for GDISYS02.DEKKO.COM 
GDISYS02.DEKKO.COM is the address of server CN=GDISYS02/O=DEKKO 
Connected to server GDISYS02/DEKKO 

Rob Berendt