Help moving forward with demo please

Thanks for the help on the previous thread about getting the demo working on WindowsXP.  I took the advice after a de-install and cleaner install.  I'm able to get the database working, but cannot get Qman or WinDDI to connect.

Here is what I have accomplished so far...

Start Teradata 'net start recond' ...

PDESTATE.exe says that the database is running ...

Then I did the following ...

C:\Program Files\NCR\TDAT\LPDE\bin>tdinfo.exe
Vpr:   VprocID     RelVpr   Type     Cliq     NodeVpr   NodeNum   CabId    Status
   0:        0     1        1        0       16384      33        001-01   ONLINE
   1:        1     2        1        0       16384      33        001-01   ONLINE
   2:     8192     4        3        0       16384      33        001-01   ONLINE
   3:    16383     3        2        0       16384      33        001-01   ONLINE
 
Node:     NodeName NodeNum   CabId Cliq NodeVpr Type   Status CPU  Memory
   0:    localhost      33  001-01    0   16384    0   ONLINE   1  510 MB
 
systemname : localhost
clique cnt : 1
node   cnt : 1
vproc  cnt : 4
pdisk  cnt : 2
chan   cnt : 0
lan    cnt : 1
 
PDE state is RUN/STARTED.
DBS state is 5:    Logons are enabled - The system is quiescent
 
This is my lmhosts file:

# The following entries are for the Teradata demo
127.0.0.1   localhost     demo1099cop1
127.0.0.1   dbc             dbccop1
 
my dbc entry on ODBC is:
127.0.0.1
user dbc
 
for demo1099 it is:
127.0.0.1
user demo1099
 
 
But when I try to login I get the following:
10054 WSA E ConnReset


I tried user=dbc, password=dbc and also user=demo1099, password=dbc.  I get the same error with both.
Network is running, and I can, for instance, put this plea for help onto tek-tips.

Any assistance would be greately appreciated.

Regards
RanD

not that I ever thought about it but I thought the password for the demo1099  was demo1099 not dbc.

Can you logon via BTEQ which uses the CLI protocol to logon.

   .logon demo1099/dbc
   password

This would at least prove whether it is a GATEWAY issue or a bigger problem.

Personally I never like seeing duplicate entries in the host file.

# The following entries are for the Teradata demo
127.0.0.1   localhost     demo1099cop1
127.0.0.1   dbc             dbccop1


should probably be....

# The following entries are for the Teradata demo
127.0.0.1   localhost demo1099cop1 dbc dbccop1

Also make the same entries in the system32\driver\etc\hosts file  since you already have it in the LMhosts file.

I don't really know which file it looks the addresses up in.

As a matter of fact, I can login using BTEQ/BTEQWin.

Can't get in using ODBC connect and either QMan or WinDDI.

I have 'do not try to resolve IP address' checked in the ODBC configuration for dbc and for demo1099.
IP address is 127.0.0.1 (localhost)


The error I get when trying to connect with QMan or WinDDI is as follows:
0: [NCR][ODBC Teradata Driver] 0 WSA E Unknown Socket Error.

pdestate says pdestate is RUN/STARTED.

tdinfo says:
Vpr:   VprocID RelVpr Type Cliq NodeVpr NodeNum   CabId   Status
   0:        0      1    1    0   16384      33  001-01   ONLINE
   1:        1      2    1    0   16384      33  001-01   ONLINE
   2:     8192      4    3    0   16384      33  001-01   ONLINE
   3:    16383      3    2    0   16384      33  001-01   ONLINE

Node:     NodeName NodeNum   CabId Cliq NodeVpr Type   Status CPU  Memory
   0:    localhost      33  001-01    0   16384    0   ONLINE   1  510 MB

systemname : localhost
clique cnt : 1
node   cnt : 1
vproc  cnt : 4
pdisk  cnt : 2
chan   cnt : 0
lan    cnt : 1

PDE state is RUN/STARTED.
DBS state is 5:    Logons are enabled - The system is quiescent

this is frustrating ...
ah yes, networking, the last 'black art' for which one can be burned at the stake

Anyone know what the problem is or can suggest a possible resolution?