New solution suitable for the Poster's setup. I cannot simplify it more than this.
Step 1: In VMWare Player's main window, right click on the VM name and select "Virtual Machine Settings".
Step 2: In the settings window, click on "Network Adapter" and among the options on the right, select "Host-only: a private network shared with the host".
Step 3: click ok.
BE SURE: The VMWare Player settings must be the default. If you fooled around with the various virtual network interfaces VMWare creates during installation, this won't work.
Step 4: Boot your virtual machine.
Step 5: If you have access to the linux command prompt, assign the ip address 192.168.40.129 like this (if you have root access):
ifconfig eth0 192.168.40.129 netmask 255.255.255.0
or
Step 5b:
sudo ifconfig eth0 192.168.40.129 netmask 255.255.255.0
(if you don't have root access).
In Windows:
Step 6: open the start menu and launch "Command Prompt". You find it in All Programs -> Accessories.
Step 7: Inside the command prompt, type ipconfig /all and press enter. One of the lines should display something like this:
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.40.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
The first three dotted groups of numbers should be identical to the one you configured inside your VM. The Subnet Mask should be identical to the one you added after the word "netmask" in the linux command you typed in Step 5.
Step 8: With the VM running, switch back to Windows and from the command prompt you opened in Step 6, type ping 192.168.40.129
You should get an output pretty much like this:
Pinging 192.168.40.129 with 32 bytes of data:
Reply from 192.168.40.129: bytes=32 time<1ms TTL=64
Reply from 192.168.40.129: bytes=32 time<1ms TTL=64
Step 9: On Windows, open up your browser and type in: http://192.168.40.129
.
Let me know if it works.
EDIT:
This answer takes for granted a "normal" home networking setup with a simple subnet and a simple private addressing. Different/more complex setups (such as a corporate network etc) will require a few modifications to the commands in order to work and you might have to check for other things. In a Home scenario with a simple home router, this should work.
EDIT#2:
Fixed a typo. The virtual machine should have a different address in the same network. So the very last number to the right should change, everything else should remain the same.
EDIT#3:
Original Poster's setup is not common (lack of any kind of network whatsoever save from a 3G connection, which is not suitable) so the original solution involving bridged networking (which would have allowed the virtual machine to reach internet) was scrapped. Current solution uses the "host-only" virtual adapter. Less flexible but given the limited requirements of the poster, suitable.
Original solution attached for archival purpose:
--- ORIGINAL SOLUTION ---
Scrap the bit about dns, you do not need it.
Turn off the virtual machine and go into its settings and under the Network Adapter option choose "bridged networking" (rather than Host-ONly or NAT).
In Windows, find out your local IP address.
You can find it out by going into the system tray, bottom right, and right click on the "status" option for your network connection. There should be a button called "details" that will give you, among other data, your current IP Address.
It will be likely something on the line of 192.168.1.102 or 192.168.0.102 etc. Once you have your Windows IP address (for the sake of this we will assume it is 192.168.1.102),
Turn on again the virtual machine and if you have access to the linux command prompt, type this (logged in as root):
ifconfig eth0 address 192.168.1.103 netmask 255.255.255.0
If you don't have direct root access add "sudo" at the start of the line:
sudo ifconfig eth0 address 192.168.1.103 netmask 255.255.255.0
Then switch back to Windows and in your browser type http://192.168.1.103
--- END ---