NO Terminal response (ODBC)

Tools & Utilities
Teradata Employee

NO Terminal response (ODBC)

Hello dear,
Now I have the following issue as ‘NO Terminal response (ODBC)’. Would you please have a look at this for us:
Problem Description:
The customer created a Windows terminal with ODBC connection. Login ODBC with SQLA, will be show an error as ‘the connection destination can not be found’.

The Teradata of the connection destination passes through the same gateway to the new terminal and the 2nd octet.
However, Some terminals can already connect from the same segment as the new terminal. (hereinafter referred to as an old terminal)

In the old terminal, ping is passed to teraNode which is the connection IP of ODBC, but it does not go through the new terminal.
When tracert from Node to Node from old terminal, there are response from Node after response from 2 gateways.
When tracert from Node to Node from new terminal, there are no response from Node after response from 2 gateways.

According to customer , they thought that whether Node have some kind of terminal restriction or not? So had error as ‘the connection destination can not be found’ was pop up.

Thanks in advance
Best regards
David

1 REPLY
Teradata Employee

Re: NO Terminal response (ODBC)

That sort of error message doesn't come from the database, driver, or SQLA.

Check for something network related, e.g. firewall or ACL.