Quantcast
Channel: Teradata Downloads - Connectivity
Viewing all articles
Browse latest Browse all 445

CLI CONNECTION USING HOSTS NAME INSTEAD OF IP ADDR. - EXTENDED TIME FOR LOGON

$
0
0

I have run several tests using BTEQ and have altered between logging on using an IP and a name in the Windows hosts file.
I have noticed that the logon process takes an extended period of time when using the name vs the IP. These are relevant entries...  Anyone have any idea where the time is being spent? Am I forcing a logon to a specific vproc using the name and if so, where does the direct IP send the logon request ?
thanks
hosts file
127.0.0.1           localhost
198.168.74.128  teraclicop1
 
BTEQ logons
.logon 198.168.74.128/tester,xxxxxx    -----> ~ 1 sec
.logon teracli/tester,xxxxxx ------------------->  ~ 7 - 8 sec's
 
 
 

Tags: 
Forums: 

Viewing all articles
Browse latest Browse all 445

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>