Can no longer connect from Windows 10 to Teradata running under VMware - linux

Teradata Database on VMWare
Junior Supporter

Can no longer connect from Windows 10 to Teradata running under VMware - linux

MY ENV. - Window 10 Pro - ver. 1607 - build 14393.187

I have been connecting from Windows 10 to Teradata under VMWare (Linux) for several months using ODBC CONNECTION IP - 192.168.74.128.
As of today following a series of Windows updates I am no longer able to connect (using SQL ASSISTANT) / ping to this IP from Windows.

I can start the VMplayer on Windows , logon to the Unix machine and ping IP - 192.168.74.128.

pdestate -a  shows Teradata is also running ok.


so the issue appears to be on the Windows side.

 

The following partial Windows ipconfig seems a bit strange... there is no default gateway for IPv4.. and the IPv4 and DHCP server addresses don't match anything like I was using to connect to Teradata on the VMware Linux machine, namely connecting using - 192.168.74.128 prior to the Windows updates...


I'm using VM  driver 4.0.3.0.... anyone have any ideas as to how I approach correcting my connection issue? Again, I can start the VMPlayer logon to the Linux machine and see the Teradata status with no problems

Thanks BRIAN

 

----------------- PARTIAL IPCONFIG OUTPUT ON WINDOWS

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
    Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
    Physical Address. . . . . . . . . : 00-50-56-C0-00-01
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::e9ad:e542:20b0:6a67%2(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.233.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : Friday, September 16, 2016 7:51:19 AM
    Lease Expires . . . . . . . . . . : Friday, September 16, 2016 8:51:19 AM
    Default Gateway . . . . . . . . . :
    DHCP Server . . . . . . . . . . . : 192.168.233.254
    DHCPv6 IAID . . . . . . . . . . . : 33574998
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-AB-56-13-14-FE-B5-B9-BE-1D
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                        fec0:0:0:ffff::2%1
                                        fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled

----------------- IFCONFIG OUTPUT ON LINUX

s10-1310:~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0C:29:3E:6F:19
          inet addr:192.168.74.128  Bcast:192.168.74.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe3e:6f19/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5963 (5.8 Kb)  TX bytes:3870 (3.7 Kb)
          Base address:0x2000 Memory:d8920000-d8940000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:122 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8073 (7.8 Kb)  TX bytes:8073 (7.8 Kb)


Accepted Solutions
Junior Supporter

Re: Can no longer connect from Windows 10 to Teradata running under VMware - linux

Solved my issue by installing VMplayer 6.0.7... sorted out my connection issues with the new eth0 IP for TDE 15.10

1 ACCEPTED SOLUTION
2 REPLIES
Junior Supporter

Re: Can no longer connect from Windows 10 to Teradata running under VMware - linux

Hi.

 

Windows

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
...
IPv4 Address. . . . . . . . . . . : 192.168.233.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
...

 

Linux:

eth0 Link encap:Ethernet HWaddr 00:0C:29:3E:6F:19
inet addr:192.168.74.128 Bcast:192.168.74.255 Mask:255.255.255.0

 

It seems your machines (physical & virtual) are on different subnet. 192.168.223.* (mask 255.255.255.0) and 192.168.74.* (mask 255.255.255.0).

 

The easier solution is to reconfigure at linux size, IMHO.

 

HTH.

 

Cheers.

 

Carlos.

Junior Supporter

Re: Can no longer connect from Windows 10 to Teradata running under VMware - linux

Solved my issue by installing VMplayer 6.0.7... sorted out my connection issues with the new eth0 IP for TDE 15.10