On Jun 28, 2006, at 4:54 AM, Loon, E.J. van - SPLXM wrote:
...ANS1033E (RC-53) An invalid TCP/IP address was specified." In the directory C:\Program Files\tivoli\TSM\TDPSql a dsierror.log is created with the following lines: 06/26/2006 08:59:43 GetHostnameOrNumber(): gethostbyname(): errno = 11004. 06/26/2006 08:59:43 TcpOpen: Could not resolve host name. 06/26/2006 08:59:43 ANS4039E Could not establish a session with a TSM server or client agent. The TSM return code is -53. 06/26/2006 08:59:43 ANS1033E An invalid TCP/IP address was specified.
... Hello, Eric - Unfortunately, this is another case of messages being less helpful than they could be, in this case failing to cite exactly what it was that the software attempted to look up in DNS. Such citation is important not just for thoroughness, but to help identify corrupting influences in the lookup argument. An insidious example is where there is accidental binary in an option file hostname, such as where backspaces and retyping were somehow captured into the string, which are "invisible" when the option file is displayed via 'cat' or like command, rather than 'od' (octal dump). Use 'dsmc q opt' and a file dump utility to verify what's in there. To help analyze - and perhaps instantly correct the problem - make a backup copy of the option file and in it replace the host name with the host's IP address. This will eliminate at least the primary gethostbyname() lookup (though there may be a reverse DNS lookup to verify number -> name -> same number). I deduce that the client is Windows... 11004 is Windows error WSANO_DATA: "The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for." It's possible that there is some irregularity in the DNS responses being received by that client. Keep in mind that where there are mutiple DNS servers in the environment, a client may end up using them rotationally, where one of the DNS servers may have faulty info, or be giving bad responses - or be timing out. Try using 'nslookup' or 'dig' or like command to inspect what this client is getting back relative to other clients. Richard Sims
