David Longo wrote:
>We have had several machines lately that suddenly can't talk to *SM server 
>>and vice versa.  Have to reboot NT  to get back.  ping and other comm works 
>>o.k.  These will work o.k a few days then same thing.  These clients have 
>>been in production for a good while with no problem.  No recent changes to 
>>them.
>
>Only messages in dsmerror is TCPIP comm failure.
>Server says attempting to contact node.

Whenever you get a TCP/IP comm failure message, and the traditional
methods of TCP/IP communication work (ping, traceroute, etc.), your
problem lies almost certainly with communication through ports 1500 or
1501 (the TCP client ports).

Something has changed in your network configuration, or NT is refusing
communication through one or both ports.

--
Mark Stapleton (stapleton AT berbee DOT com)
Mark Stapleton (stapleton AT berbee DOT com)