You can use Host option in vm ware network settings, instead of NAT, Bridged.
Once done, start your vmware and assign statics IP to guest.
for example for guest:
in gateway enter:
Then on host machine, open the vmnet1, go to properties, set static IP as follows:
in gateway enter:
remember xxx is the same for all these entries, and usually same for all IPs.
once done, you will be able to use internet and all the things.
Please let me know if there is any issue!
Yes, login to guest machine, and assign IP as you do on any machine by going to network settings.
On host, go to VMNET1 properties and assign Ip as described above.
It is not working. Below are the settings:
I am in VMWARE and I can see Linux window. I have Mozilla there. Do you feel I miss out any thing?
I have C:\Program Files (x86)\VMware\VMware Workstation\ . On opening this, I land up in Linux window, where I have Teradata studio, root after login with root/root.
Basically, I was talking about windows host and windows guest configuration. I have not tested it on linux. The main thing is the same default gateway for both the machines. You have made right settings for Host, but for the guest you will have to use same default gateway.
I see lot of users are having very same issue. Can't connect from/to vmware machine. Can't reach internet and so on.
1.when using TD secure connection (ie anyconnect, ciscovpn, juniper) to Teradata or customer network, you have to take care about the routing, if not, the statefull firewall always cut your outbound connection(s) to gateway.
2.when deploying a new image, I always generate new MAC address (as someone might have very same on my network, just to avoid network conflicts)
3. when there is issue with DHCP server (on Windows) you probably get some weird IP configuration (starting with 172.* or 175..*) if there are not some 'preffered' values (as M.Saeed Khuram noticed above). When this very same is faced via/on linux, you probably don't get your interface (eth0) working automaticaly.
Here is my output from ipconfig/ifconfig commands issued on host/guest machines for "NAT" configuration. I never used BRIDGED so far, never had to, as NAT is working pretty much well. Especially when more than one virtual machine is up and running.
- NAT (share host ip)
- different MAC address for host interface
LOCALMACHINE: command: ipconfig/all
Ethernet adapter Local Area Connection:
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 22.214.171.124(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 126.96.36.199
DHCP Server . . . . . . . . . . . : 188.8.131.52
DNS Servers . . . . . . . . . . . : 184.108.40.206
Primary WINS Server . . . . . . . : 220.127.116.11
Secondary WINS Server . . . . . . : 18.104.22.168
NetBIOS over Tcpip. . . . . . . . : Enabled
VIRTUALHOST: command: ifconfig
If you find this post Off-Topic, let me know i will unpublish it.