Archives of the TeradataForum

Message Posted: Tue, 15 Apr 2003 @ 16:13:47 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Yes, the port setting is the problem.

NCR never bothered to register and reserve a TCP/IP port for use by Teradata client software. Instead, they just use an unreserved port (1025). Not only is this port unregistered, it's the first unregistered/unreserved port, so many applications upon starting will grab this port if it isn't in use.

In the past, NCR relied on the fact that the Teradata gateway port reservation service would start up and grab 1025 before anybody else had a chance. In XP, it turns out that they start services in parallel. and so sometimes (often) some other service will grab the port first. n my case, I find that on my dual-CPU system things just work, and on my single-CPU system Teradata almost never gets the port.

Changing the port to some value unlikely to be grabbed by some other application works (at least, mostly... No guarantee that any future software you load won't grab the same port you pick, but it's unlikely). There are also ways to make the Teradata gateway port service start sooner, so it is more likely to get 1025, but this is difficult.

The downside of changing the port is that every client needs to know the port number you pick.

	<Prev	Next>		<<First	<Prev	Next>	Last>>