Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 22 Nov 2005 @ 18:13:44 GMT


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


Subj:   Re: Cannot logon to Teradata demo system
 
From:   David Wellman

Hi all,

Well, I think we're getting somewhere - I'm just not sure where !

I've installed and run the MS PortReporter tool and their PortQueryUI tool (essentially a Windows gui which takes a snapshot of any named port) and have the following results.

PortQueryUI says that: TCP port 1025 (tdmst service): NOT LISTENING - my deduction is that because this is "not listening" that's why I cannot connect from an application.

- note that this tool was run even after the "Teradata Service Control" application says that "Teradata is running"

The PortReporter tool shows the folowing list of Ports-to-Process mappings when it starts.

     PID:Process        Port        Local IP        State         Remote IP:Port
     4:System           TCP 445     0.0.0.0         LISTENING     0.0.0.0
     4:System           TCP 139     192.168.1.102   LISTENING     0.0.0.0
     4:System           UDP 445     0.0.0.0         *:*
     4:System           UDP 137     192.168.1.102   *:*
     4:System           UDP 138     192.168.1.102   *:*
     988:svchost.exe    TCP 135     0.0.0.0         LISTENING     0.0.0.0
     1032:svchost.exe   UDP 123     127.0.0.1       *:*
     1032:svchost.exe   UDP 123     192.168.1.102   *:*
     1116:svchost.exe   UDP 1031    0.0.0.0         *:*
     1124:Skype.exe     TCP 80      0.0.0.0         LISTENING     0.0.0.0
     1124:Skype.exe     TCP 443     0.0.0.0         LISTENING     0.0.0.0
     1124:Skype.exe     TCP 42289   0.0.0.0         LISTENING     0.0.0.0
     1124:Skype.exe     TCP 1041    192.168.1.102   ESTABLISHED   83.132.104.190:60359
     1124:Skype.exe     UDP 42289   0.0.0.0         *:*
     1124:Skype.exe     UDP 1027    127.0.0.1       *:*
     1324:svchost.exe   UDP 1900    127.0.0.1       *:*
     1324:svchost.exe   UDP 1900    192.168.1.102   *:*
     2448:fspex.exe     UDP 9370    0.0.0.0         *:*
     2884:alg.exe       TCP 1037    127.0.0.1       LISTENING     0.0.0.0
     3520:fshttps.exe   TCP 59591   127.0.0.1       LISTENING     0.0.0.0
     3632:fsdfwd.exe    TCP 58581   127.0.0.1       LISTENING     0.0.0.0
     5604:rsgmain.exe   TCP 56970   0.0.0.0         LISTENING     0.0.0.0

Note that port 1025 is not listed.

Further down this same file I get the following info relating to gtwgateway.exe (which I think/assume is the gateway program):

     Process ID: 2252 (gtwgateway.exe)

     User context: NT AUTHORITY\SYSTEM

     Process doesn't appear to be a service


     Port Statistics

     TCP mappings: 0
     UDP mappings: 0

I worked through the Event log messages for when Teradata is starting and the only one that I could find which looked strange (and I also compared this failing PC to a working one) is the following message:

     Event Type:       Error
     Event Source:     Teradata
     Event Category:   None
     Event ID:         8088
     Date:             22/11/2005
     Time:             14:58:13
     User:             N/A
     Computer:         DELL8600
     Description:
     Event number 34-08088-00 (severity 70, category 10), occurred on Tue
     Nov 22 14:58:13 2005 , at 001-01 (Vproc 8192, partition 10,
     task 5588) in system localhost in Module gtwgateway.exe, version
     PDE:05.00.00.11,TDBMS:05.00.00.11,RSG:05.00.00.00,TGTW:05.00.00.00
     Invalid Configuration:
     gtwnetconnect.c @260 (5588): Tue Nov 22 14:58:13 2005
     tdmst missing from /etc/services file - defaulting to 1025

I have also tried removing and re-installing the dbms (the above messages/diagnostics were from after the re-install) but that hasn't sorted the problem out.

What next folks ?


Many thanks,

Dave



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023