Actually I've ended up having a similar problem. I think it's less of a Teradata DB thing within the VMware image, and more of a SLES apache2 issue. I'm not a networking specialist but I've done all the checks suggested by Dieter. The DB is working, pdestate -a returns happily. a bteq statement within the command prompt logs me in and works fine. however when I jump onto my native windows 7 host computer, I can't ping the system (setup on 192.168.47.128).
Carlos, it was and has been working fine using the basic installation of NAT without any changes. But it has been flaking and fallen off the cliff every so often.
--------------------------------------------------------------------------------- guest os
TDExpress14.0_Sles10:~ # ping 192.168.47.128
PING 192.168.47.128 (192.168.47.128) 56(84) bytes of data.
64 bytes from 192.168.47.128: icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from 192.168.47.128: icmp_seq=2 ttl=64 time=0.036 ms
64 bytes from 192.168.47.128: icmp_seq=3 ttl=64 time=0.034 ms
--- 192.168.47.128 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.033/0.034/0.036/0.005 ms
TDExpress14.0_Sles10:~ #
------------------------------------------------------------------------------------- host os
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\RB186032>ping 192.168.47.128
Pinging 192.168.47.128 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.47.128:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\RB186032>ping 192.168.47.128
Pinging 192.168.47.128 with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 192.168.47.128:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\RB186032>
↧