Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




8 posts

Wannabe Geek


Topic # 18392 9-Jan-2008 10:26
Send private message

does anyone know how to network between Vista Ultimate and VMware V6.0.2 Build 59824 as am having real problems and is making me get frustrated i am sure once VMware is networked i can then work out the networking between vista and win2k3 server..

if anyone can help i would love that saving my hair from being pulled out Cry

Thanks guys and also wasn't sure where to put this post i thought networking as it's that i am after

Create new topic
181 posts

Master Geek


  Reply # 104292 11-Jan-2008 19:16
Send private message

I can probably assist. I gather your using VMware Workstation 6? If not can you tell me what product it is?

Pasting screenshots of your current config pages will probably be the best way to start.

Si



8 posts

Wannabe Geek


  Reply # 104419 12-Jan-2008 19:26
Send private message

yes it's VMWare V 6.0.2 Build -59824 if there is anything else you need to know please let me know

 
 
 
 


95 posts

Master Geek


  Reply # 104420 12-Jan-2008 19:48
Send private message

Marcg5477: does anyone know how to network between Vista Ultimate and VMware V6.0.2 Build 59824 as am having real problems and is making me get frustrated i am sure once VMware is networked i can then work out the networking between vista and win2k3 server..


VMware is typically no different from a "real" PC.  The first thing to check is connectivity.

Are all the machines set to automatically obtain an address (DHCP) or fixed addresses?  If fixed addresses what have you given them?

First step may be to open a CMD command prompt and run IPCONFIG / ALL and paste the results here.


DS



8 posts

Wannabe Geek


  Reply # 104426 12-Jan-2008 20:39
Send private message

the networking with internet is ok it's just using vista and the VMWare network cards won't let me do...

I Have VMnet1 and VMnet 8

On the VMnet8 the address is 192.168.136.1 (prefered)
Gateway is 192.168.136.254

VMnet 1 is 192.168.12.1 (prefered)
gateway 192.168.12.254


the router is 192.168.0.254 (linksys router not modem) then have a dlink modem on 10.1.1.1 ( linksys and dlink are working together no probs i can access both the router and modem from my lappy which use's the router (192.168.0.254) )

is there anything else you need to know

.........................................................................................................................................................................................


C:\Users\Kisaku>ipconfig/all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Naruto
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 00-1A-6B-74-79-DD
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con
nection
   Physical Address. . . . . . . . . : 00-19-D2-DC-8A-26
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e82e:a49a:49ae:814a%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.50(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 12 January 2008 6:54:34 p.m.
   Lease Expires . . . . . . . . . . : Sunday, 13 January 2008 6:54:33 p.m.
   Default Gateway . . . . . . . . . : 192.168.0.254
   DHCP Server . . . . . . . . . . . : 192.168.0.254
   DHCPv6 IAID . . . . . . . . . . . : 234887634
   DNS Servers . . . . . . . . . . . : 10.1.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connection
   Physical Address. . . . . . . . . : 00-1B-24-24-85-1D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::8cb:25a3:71d7:9b6%8(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.54(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 12 January 2008 6:54:33 p.m.
   Lease Expires . . . . . . . . . . : Sunday, 13 January 2008 6:54:32 p.m.
   Default Gateway . . . . . . . . . : 192.168.0.254
   DHCP Server . . . . . . . . . . . : 192.168.0.254
   DHCPv6 IAID . . . . . . . . . . . : 201333540
   DNS Servers . . . . . . . . . . . : 10.1.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::71fe:3f73:70d9:b6d7%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.12.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 12 January 2008 8:34:29 p.m.
   Lease Expires . . . . . . . . . . : Saturday, 12 January 2008 9:04:28 p.m.
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 285233238
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   Primary WINS Server . . . . . . . : 192.168.12.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet
8
   Physical Address. . . . . . . . . : 00-50-56-C0-00-08
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ddec:93b0:761f:c6a%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.136.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, 12 January 2008 8:34:14 p.m.
   Lease Expires . . . . . . . . . . : Saturday, 12 January 2008 9:04:13 p.m.
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 192.168.136.254
   DHCPv6 IAID . . . . . . . . . . . : 302010454
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 7:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{C886D01E-0EF1-40FC-93A9-4BCBB7C1B
E6E}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5efe:192.168.0.50%13(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 10.1.1.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 10:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e66:1c5c:39df:3f57:ffc9(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::1c5c:39df:3f57:ffc9%12(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{77A96A43-E2C8-4887-8A6A-353DC50FD
358}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Kisaku>


95 posts

Master Geek


  Reply # 104430 12-Jan-2008 20:53
Send private message

Marcg5477:

the networking with internet is ok it's just using vista and the VMWare network cards won't let me do...
IPv4 Address. . . . . . . . . . . : 192.168.0.54(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0



This would be from Vista machine so that's OK. 

What operating system is running inside VMware ... ie. on the "guest"? 

The key is to make sure that the IP address of that machine is also on the same address range as your router (so 192.168.0. something).  If it is then try

PING 192.168.0.54

and see if you get a response.  If so then they should communicate OK.

If the 'guest" machine is on a differnt address range then they can't talk.  This is IP addressing - nothing to do with VMware ... it would be the same with a real PC.

DS



8 posts

Wannabe Geek


  Reply # 104432 12-Jan-2008 21:02
Send private message

ok so the VMnet1 & 8 doesn't matter what that is then just as long as the guest OS ( in my case it's windows Server 2003 Enterprise) matches the router IP then?

95 posts

Master Geek


  Reply # 104434 12-Jan-2008 21:18
Send private message

Marcg5477: ok so the VMnet1 & 8 doesn't matter what that is then just as long as the guest OS ( in my case it's windows Server 2003 Enterprise) matches the router IP then?



The normal config if for VMware to install many pretend networks such as the VMnet1 and 8 yo use for "private" communications between guests and the host machine.  However, most VMs will just use DHCP to get their own address on the network and communicate directly with the Internet and the rest of your LAN (including the host) using the main network (192.168.0.x).

So ... yes ... as long as the guest OS is on the same address range then all should be well.

DS



8 posts

Wannabe Geek


  Reply # 104437 12-Jan-2008 21:44
Send private message

the problem i still face is that i manually matched the ip addy to the main router i use and ping it and i can't ping the host and the host can't ping the guest so still not sure how to solve this

is there anything special to network from vista to a non vista machine?

894 posts

Ultimate Geek
+1 received by user: 32


  Reply # 104442 12-Jan-2008 22:06
Send private message

It could be that you DNS server is pointing at
DNS Servers . . . . . . . . . . . : 10.1.1.1

instead of in the range of 192.168.*.*

Dion



8 posts

Wannabe Geek


  Reply # 104443 12-Jan-2008 22:10
Send private message

maybe it's me or if i'm not that bright but when i did the ipconfig/all it told me it was on 10.1.1.1 as the DNS how to figure out what the DNS should be ?

sorry for being noobish

894 posts

Ultimate Geek
+1 received by user: 32


Reply # 104444 12-Jan-2008 22:33
Send private message

you could try 192.168.0.254

I don't know if they would be conflicting with each but you could try turning off the Wireless adaptor as both that and the ethernet have the same IP range on them.



8 posts

Wannabe Geek


  Reply # 104446 12-Jan-2008 22:38
Send private message

ok thanks will try tomorrow other wise will post here tomorrow night

95 posts

Master Geek


  Reply # 104504 13-Jan-2008 12:30
Send private message

Marcg5477: the problem i still face is that i manually matched the ip addy to the main router i use and ping it and i can't ping the host and the host can't ping the guest so still not sure how to solve this

is there anything special to network from vista to a non vista machine?


Check your VMware settings. 

In the HOST, Virtual Network settings on your "host" machine you should have VMnet0 (Bridged) and this is the normal it should use.  VMnet1 and 8 are "private" networks internal to VMware.  VMnet0 connect your Virtual Machine "direct" to the network ias if it was a real machine.

Subnet Mask will typically be 255.255.255.255

On the Automatic Bridging tab turn off auto as it may be connecting to wireless or something.

On the Host Virtual Mapping tab select you LAN card (not wioreless or anything else) under the VMnet0 dropdown.

Leave the rest and click OK.

Start your virtual machine.

Under the VM menu go to Removable Devices, Ethernet, Disconnect. 

If you are logged in to Windows inside the guest then Network icon in the system tray / notification are (next to the clock) should go disabled if it's there.  Go to Settings, Netork Connections and it should show the connection as greyed out.  If you right-click and look at properties for the adapter it should be using "VMware Accelerated AMD PCNet Adapter".

Quick question ... Have you installed VMware tools?  (VMm, Install VMware tools from host)

In VMware go to VM, Removable, Ethernet, Edit and check that it is connected at power on and that you are using Bridged mode.

Re-enable the card from VMware (VM, removable, Etherner, Connect or by ticking Connected in the above).

In your virtual machine try a PING again ...

PING 192.168.0.54

or

PING 192.168.0.254

both should work if all is well.  What address are you using for the VM's network card (IPCONFIG)?  If the address you have chosen is not unique then PING will fail.

PING should work regardless of DNS if you are using addresses as above.  DNS will only matter if you use a name like

PING www.geekzone.co.nz


DS

Create new topic


Donate via Givealittle


Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

Orcon announces new always-on internet service for Small Business
Posted 18-Apr-2019 10:19


Spark Sport prices for Rugby World Cup 2019 announced
Posted 16-Apr-2019 07:58


2degrees launches new unlimited mobile plan
Posted 15-Apr-2019 09:35


Redgate brings together major industry speakers for SQL in the City Summits
Posted 13-Apr-2019 12:35


Exported honey authenticated on Blockchain
Posted 10-Apr-2019 21:19


HPE and Nutanix partner to deliver hybrid cloud as a service
Posted 10-Apr-2019 21:12


Southern Cross and ASN sign contract for Southern Cross NEXT
Posted 10-Apr-2019 21:09


Data security top New Zealand consumer priority when choosing a bank
Posted 10-Apr-2019 21:07


Samsung announces first 8K screens to hit New Zealand
Posted 10-Apr-2019 21:03


New cyber-protection and insurance product for businesses launched in APAC
Posted 10-Apr-2019 20:59


Kiwis ensure streaming is never interrupted by opting for uncapped broadband plans
Posted 7-Apr-2019 09:05


DHL Express introduces new MyDHL+ online portal to make shipping easier
Posted 7-Apr-2019 08:51


RackWare hybrid cloud platform removes barriers to enterprise cloud adoption
Posted 7-Apr-2019 08:50


Top partner named at MYOB High Achievers Awards
Posted 7-Apr-2019 08:48


Great ideas start in Gisborne with hackathon event back for another round
Posted 7-Apr-2019 08:42



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.