ADSM does not find routes to the server. ADSM uses
standard WinSock calls and basically just
asks for a session with the server by name
or address ( whichever is provided in the options file ).
If the connection is failing beyond that point, you've
got a problem with the network or your TCP/IP configuration.
ADSM does not contain routing software.

Barry Fruchtman
ADSM Development

On Thu, 3 Jul 1997, Bartl, Michael wrote:

> Several times in the past there were discussions on the Error
> ANS4017E Session rejected: TCP/IP connection failure
>
> I get this error on one NT-Server, too and did some research:
>
> When the client tries to connect to the Server, the right IP-Route
> cannot be found. I first thought that ADSM is not able to get the right
> IP-Address out of the symbolic name, but found another interesting fact:
> When a PING is running (or was running shortly) in background, which
> means that the IP-route is cached, ADSM has no problem at all. A few
> minutes after the PING, when the cache has become invalid, ADSM traps
> into the same error.
>
> I hope it will be fixed in the next release of the client software.
> Did someone find a workaround for this problem?
>
> Regards
> Michael
>
>
>
> --
> Michael H. Bartl, ADAC e.V. (IDL/PPO)
> Tel.: (089) 7676-4063, Fax: (089) 7676-8161
> EMail: Michael.Bartl AT Zentrale.ADAC DOT de
>