hi,
i have vmware player (v 2.5.2) running linux(knoppix) as guest on my host( windows xp) and i have two problems:
1.i have a lexmark 1200 printer that the vmware recognise but i cant print with it from the guest even though it is marked as connected.
2.i cant connect to the internet from the guest (not when the network adapter is set to NAT nor to bridged)
-- I have checked that vmnet1 and vmnet8 on windows are enables and working properly
-- no vmware related execs are firewalled.
-- I know that NAT is working on another computer with the same virtual machine definitions.
this is the output of the ifconfig on linux(the guest)
>> knoppix@2[knoppix]$ ifconfig
>> eth0 Link encap:Ethernet HWaddr 00:0C:29:3B:7D:63
>> inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0
>> inet6 addr: fe80::20c:29ff:fe3b:7d63/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:542 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:65004 (63.4 KiB) TX bytes:9308 (9.0 KiB)
>> Interrupt:18 Base address:0x1080
>>
>> 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:26 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:1300 (1.2 KiB) TX bytes:1300 (1.2 KiB)
>>
>> knoppix@2[knoppix]$
>>
>>
and this is the output of the ipconfig on my host
>>>>
>>>> Microsoft Windows XP http://Version 5.1.2600
>>>> (C) Copyright 1985-2001 Microsoft Corp.
>>>>
>>>> C:\Documents and Settings\user>ipconfig
>>>>
>>>> Windows IP Configuration
>>>>
>>>>
>>>> Ethernet adapter VMware Network Adapter VMnet8:
>>>>
>>>> Connection-specific DNS Suffix . :
>>>> IP Address. . . . . . . . . . . . : 192.168.101.1
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . :
>>>>
>>>> Ethernet adapter VMware Network Adapter VMnet1:
>>>>
>>>> Connection-specific DNS Suffix . :
>>>> IP Address. . . . . . . . . . . . : 192.168.107.1
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . :
>>>>
>>>> Ethernet adapter Local Area Connection:
>>>>
>>>> Connection-specific DNS Suffix . :
>>>> IP Address. . . . . . . . . . . . : 10.0.0.1
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 10.0.0.138
>>>>
>>>> PPP adapter adsl:
>>>>
>>>> Connection-specific DNS Suffix . :
>>>> IP Address. . . . . . . . . . . . : 83.130.98.221
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>>>> Default Gateway . . . . . . . . . : 83.130.98.221
>>>>
>>>> C:\Documents and Settings\user>
>>>>
CAN ANYONE HELP??
thanks
Use NAT for the VMs on this host, since you don't want to bridge to the DSL interface. After switching to NAT, I would suggest restarting the guest OS. If the guest can't get a valid IP, then maybe your guest network config isn't completely sane. We can revisit this if the above suggestion doesn't work.
I would also recommend upgrading to Player 3.0, of course
I would also recommend upgrading to Player 3.0, of course
of course ????
VMplayer 3 does not install vmnetcfg.exe on Windows so every advanced network setup will be much harder to acchieve than with 2.5.2
At the moment I would rather wait for VMplayer 3.0.1
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
True, each user of software should base upgrade decisions on a set of things like whether or not the feature set offered by the new release is necessary, worth the price, worth the upgrade overhead, etc etc. Player is a consumer app, so I felt I could be a bit jokey, cause consumer apps are really geared to be run and supported at the latest and greatest. In reality, I only made that suggestion because Player 3.0 includes VM Settings, which would allow a user to switch a VM to use NAT within the UI.
I intend to respond to the discontent about the removal of vmnetcfg from Player. For the issue reported on this thread, the network editor wouldn't be useful or relevant, so we'll hold that discussion till I can give that discussion a reply worthy of the upset we've caused even just the few users who noticed.
why does it not apply to this post ???
if OP can't assign the right nic to the bridged interface he can't fix his bridged networking issue with an upgrade to 3
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
OP should be using NAT.
Your use case is valid, and I intend to address it in context. Without the network editor you can't easily turn off auto-bridging and manually pick the bridged interface. Unfortunately, as you and I have both seen, this use case is pretty relevant, cause auto bridging doesn't work, and so users often have to manually pick what they want to get stuff to work. (Though most of those use cases should be addressed with NAT. Unfortunately we do a poor job of exposing how to set up networking config - thus many of these forum issues show up).
hi,
I have used the information about the VMX paremeters and I have replaced all
the "ethernet0" lines with those writen in the link but it did not help
I have the VMware tools inside the guest
anything else I can do? thanks
in the link ??? - which one ?
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
in this one
I have listed several scenarios in that link - I am no mindreader so I really do not know what you used ...
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
thanks for the quick response
I have used the settings that enable an VMXnet network-card.
for "nat"
thats not very clever - use the varaiant with the e1000 instead.
Every recent OS should have a driver for that one while only a few OS come with buildin drivers for vm,xnet
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
I have used the varaiant with the e1000 instead
but it still doesn't work,I am attaching the ifconfig
knoppix@1[knoppix]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:3B:7D:63
inet addr:192.168.101.128 Bcast:192.168.101.255
Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe3b:7d63/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1377 (1.3 KiB) TX bytes:2278 (2.2 KiB)
Interrupt:18 Base address:0x1080
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:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:900 (900.0 b) TX bytes:900 (900.0 b)
knoppix@1[knoppix]$
thanks again
Knoppix received an IP from the VMware NAT-service.
If it still does not work check the firewall of the host.
Can you ping the host from Knoppix ? - should work
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
Yes I Can ping the host from Knoppix and Knoppix from host.
but it still does not work. I have checked the firewall of the host.
and I have VMware-authd ,VMware-player and Mozilla-Firefox(the web browser
in knoppix) all enabled.
any thing else to enable???
thanks
You say in your original post "I know that NAT is working on another computer with the same virtual machine definitions."
I presume that they are not identical definitions, i.e. you did get VMware to change the UUID and MAC address if/when you copied the VM?
in Knoppix open a shell and type
nslookup - then enter a test like www.google.com
does that work ?
___________________________________
VMX-parameters- VMware-liveCD - VM-Sickbay
NO,the output :
knoppix@2[knoppix]$ nslookup www.google.com
Server: 192.168.101.2
Address: 192.168.101.2#53
server can't find www.google.com: SERVFAIL
knoppix@2[knoppix]$