hi
i am running VmWare under Windows XP with Red hat Linux 9

VMnet0 bridged to an automatically chosen adapter
Vmnet1(NAT) used 2 share Hosts IP address
VMNET 2 bridged to the USB interface for internet conn.
Vmnet8(host only) a private n/w shared by host

the problem is during boot it shows eth0 enabled but i am not able to connect to the inetrnet nor 2 windows

Help


annette

Which is your host operating system (the one that VMWare runs under)?

hey

i the host is winxp. and the linux i am using is red hat 9

I have more questions and maybe some pointers:

(1) Can you connect to the internet directly from
windows xp?

(2) what do you specifically mean by "not being able to connect to windows?"

The problem may be in how your networking is set up in windows xp and could be an IP address conflict of some sort. This is a pure guess on my part but is what I would look for if I was confronted with the problem you are having.

yes i can connect to the internet thru' winxp

i have given a ip address for winxp and for linux by adding a NIC adapter fro enabling eth0

it does not even show in the dmesg that it has recognised the DSL modem which is connected to the USB port

annette

How have you setup eth0?

It should be setup as an NAT device since presumably Win XP and Linux will be sharing a physical ethernet device and it will only have 1 IP address.

If, however, winxp has it's own ethernet device and linux will be using a seperate ethernet device with its own IP then it should be a bridged device.

yes i have set it as a nat device and have given the option to connect to the physical n/w.


the problem is the dsl is connected via a usb n not thru a lan card

how can i check if the devices connected to the usb are being recognized?

That information would have been helpful to have earlier...

I direct you to the section entitled "Notes on USB support in version 5" at the bottom of page 417 in the vmware manual: VMWare Workstation 5.5

I'm assuming that's the version you're using?

huh????????
the version of vmware i am using is 4.5.2.

Again, that information would have been helpful earlier, although we, including myself, could have asked... anyway, in that case I direct you to the section entitled "Notes on USB support in version 4"

Looks like you can't use it then. If you want to use it you'll have to connect it the host OS via ethernet instead of USB.

hey will i require 2 specifically configure the usb drivers for linux????????? or i will have 2 get a lan conn??????????????

Well I've not actually heard of anyone using a cable or (A)DSL modem via USB in Linux, as far as I know it's not supported, but I might be wrong on that one.

I personally would always recommend using an Ethernet connection over USB for anything network related, i.e. LAN, Internet, etc. If you connect using Ethernet then you'll be able to use the Internet connection on pretty much any OS you install in a virtual machine.

In a nutshell, if you want to use your Internet connection from a virtual machine, beit VMWare, QEMU or PearPC, you need to connect your modem to you computer using an Ethernet connection, not USB.

k
thnx 4 da suggestion. now the conn is via the ethernet.but once u boot winxp will already get an ip address . how will u assign another ip addresss???
when i click the option saying "bridge to the physical n/w" it prompts saying "it will affect the physical n/w"
wat do i do? tell me from teh begginning 2 check if i have done it properly from start

You can only use bridged networking if you have two physical network adapters. One for your host OS and the other for the VM, which you are 'building a bridge to', hence the term bridged network. All this means is creating a link, or bridge, between the virtual network adapter the VM is using and the physical network adapter that will actually be connected to your network.

If you only have one network adapter then you need to set up the VMs network adapter as a NAT device. NAT stands for Network Address Translation, this allows the VM to 'share' the IP address of the host OS via the one network adapter. The downside to this is because the VM doesn't have it's own IP address you can't use the VM as a server (web, smb, etc etc) because it's not uniquely identifiable on the network.

I'm guessing the reason you're getting that message is because you're trying to bridge to an already active network adapter, i.e. the one the host OS is using.

With the VM turned off, change the configuration of the network adapter from a Bridged device to the NAT device and see if that works.

You need to use NAT networking, not bridged.