Re:Connect to Teradata Virtual Machine Guest from Windows Host

Ra*** about 3 years ago

@Rtyu Default account for database admin: User: dbc Password: dbc

Rt*** about 3 years ago

How to connect as admin ?
Add comment

Comments (16)

Far*** about 3 years ago

Great article. Thanks a lot

Ra*** about 3 years ago

@Rtyu Default account for database admin: User: dbc Password: dbc

Rt*** about 3 years ago

How to connect as admin ?

Rt*** about 3 years ago

How to connect as admin ?

Ra*** about 4 years ago

@Joe hi Joe, I am glad that your problem is resolved. Last night I upgraded VMware Player to version 12 as the previous one didn't work well in my Windows 10 machine. The NAT connection mode is always working. However I could not get the bridged network mode work even I can see one IP is allocated to the virtual machine from router. DHCP was already setup previously for my virtual adapters. Yes, you are right. VM0 is also not shown in my network adapter list though I can see vm1 and 8 which are used for the other two types of connection mode respectively. So my issue is a little bit different from yours. I will also let you know once I fix it.

Jo*** about 4 years ago

@Raymond Hey, Raymond thanks for all your help, but I fixed the problem. Within the Teradata Express VM, I opened YaST2 and used the network setup method. I then edited my VMware Single Port adapter. This enabled the DHCP. If you choose the automatic address setup (via DHCP) it should configure and give you a new IP address. I then was able to use this IP address to connect to my VM on the host. Now bteq and SQLA can logon to the VM database. I also found that VMnet0 is your bridged connection, however, my host isn't showing a VMnet0 at all... I wonder if this is an issue. So I'm investigating this further. I'm still unable to connect to the internet, but as long as I can connect to my VM, it'll suffice.

Jo*** about 4 years ago

@Raymond Hey, Raymond thanks for all your help, but I fixed the problem. Within the Teradata Express VM, I opened YaST2 and used the network setup method. I then edited my VMware Single Port adapter. This enabled the DHCP. If you choose the automatic address setup (via DHCP) it should configure and give you a new IP address. I then was able to use this IP address to connect to my VM on the host. Now bteq and SQLA can logon to the VM database. I also found that VMnet0 is your bridged connection, however, my host isn't showing a VMnet0 at all... I wonder if this is an issue. So I'm investigating this further. I'm still unable to connect to the internet, but as long as I can connect to my VM, it'll suffice.

Ra*** about 4 years ago

@Joe The status shows your service is running correctly. If your can ping your VM that means it is probably something to do with the port number the service is using. For example, the firewall may be blocking traffic from/to the default port number 1025. Could you please double-check your firewall settings? The example was using NAT. Could you please try whether NAT works? If it works, then the problem is most likely to do with the port number. As I am not an expert in network, you may have to look into VM official documentations to find out details about it. I will also try the bridged network in my laptop to see whether it will work when I get home.

Jo*** about 4 years ago

@Raymond Yes, I have tried it in NAT mode, and I still get that error about login in SQLA. I can connect on my VM and pingit on my WindowsOS. Right now my firewall is off, how can I check if the port is being blocked? Please also let me know if your bridged connection worked. Thanks

Ra*** about 4 years ago

@Joe The status shows your service is running correctly. If your can ping your VM that means it is probably something to do with the port number the service is using. For example, the firewall may be blocking traffic from/to the default port number 1025. Could you please double-check your firewall settings? The example was using NAT. Could you please try whether NAT works? If it works, then the problem is most likely to do with the port number. As I am not an expert in network, you may have to look into VM official documentations to find out details about it. I will also try the bridged network in my laptop to see whether it will work when I get home.

Ra*** about 4 years ago

@Joe The status shows your service is running correctly. If your can ping your VM that means it is probably something to do with the port number the service is using. For example, the firewall may be blocking traffic from/to the default port number 1025. Could you please double-check your firewall settings? The example was using NAT. Could you please try whether NAT works? If it works, then the problem is most likely to do with the port number. As I am not an expert in network, you may have to look into VM official documentations to find out details about it. I will also try the bridged network in my laptop to see whether it will work when I get home.

Jo*** about 4 years ago

@Raymond Yes, I have tried that multiple times, but I still get PDE:RUN/STARTED and that DBS is 5: Logons are enabled. Like I said, on the Windows server I can ping my IP, but when I try to connect in BETQ or in SQLA I get errors.

Jo*** about 4 years ago

@Raymond Yes, I have tried that multiple times, but I still get PDE:RUN/STARTED and that DBS is 5: Logons are enabled. Like I said, on the Windows server I can ping my IP, but when I try to connect in BETQ or in SQLA I get errors.

Ra*** about 4 years ago

@Joe Can you try the following command to start your service in VM? /etc/init.d/tpa start Could you please also parse the status of Teradata service if it cannot be started successfully? The command you can use to check service status is: pdestate –a

Ra*** about 4 years ago

@Joe Can you try the following command to start your service in VM? /etc/init.d/tpa start Could you please also parse the status of Teradata service if it cannot be started successfully? The command you can use to check service status is: pdestate –a

Jo*** about 4 years ago

My windows OS can ping the IP for the VM. However, when I try to connect in windows through SQLA I can not get it to ping, and I get the login error... I realize you say that it is because the service has not started yet, but what does that mean? how can I establish the connection? I am also on a bridged connection.

Jo*** about 4 years ago

My windows OS can ping the IP for the VM. However, when I try to connect in windows through SQLA I can not get it to ping, and I get the login error... I realize you say that it is because the service has not started yet, but what does that mean? how can I establish the connection? I am also on a bridged connection.

Ra*** about 4 years ago

@Mihir I have not used Administrator Client but I assume you can use the same connection properties as you will use in SQL Assistant or Teradata Studio. Since .NET provider is working, the ODBC driver should also work. Cheers, Raymond

Mi*** about 4 years ago

Connected to Teradata Administrator As well, by Installing .NET Provider. Thank you!

Mi*** about 4 years ago

Connected to Teradata Administrator As well, by Installing .NET Provider. Thank you!

Mi*** about 4 years ago

Thanks a lot for this article.! Very much Helpful. but how to connect Teradata Administrator ? ODBC/.NET option not provided in Teradata administrator

Ra*** about 4 years ago

@Unknown I am glad it helped you. I met those issues previously and found nothing useful to fix. So I then looked into a number of articles in Teradata and then finally fixed it and decided to summarize those details in my blog.

Un*** about 4 years ago

I have been stuck on making the odbc connection work from few days with Teradata VM and when i was just about to give up I finally found your post and finally it worked. Sigh....!! Thank you so much.

Un*** about 4 years ago

I have been stuck on making the odbc connection work from few days with Teradata VM and when i was just about to give up I finally found your post and finally it worked. Sigh....!! Thank you so much.

Un*** about 4 years ago

you are a savior. Most useful information no where to found.