[dba-VB] Scrum & C# - VS versions we have

Hi Francesco,

Thank you for your replay.
The following is just for information.
I have got installed VMWare Player v.2.x
I managed VM to see outer world (local LAN PCs) and the Internet.
But VM still can't access Vista's shares, and Vista's shares *are* accessable from other PCs in the LAN.
Vista host can't access guest VM's shares but those shares *are* accessable from other PCs in the LAN.
VMWare Player doesn't seem to have any tools to tune VM Network configuration.
I have checked Vista's firewall - it allow VMWare player to access host.

I currently decided to leave it as it's - I have posted a message in VMWare community with the question how to tune VMWare Player for its guest VM to see the host shares. No definitive advises yet.

Thank you.

--
Shamil

-----Original Message-----
From: Francisco Tapia <fhtapia at gmail.com>
To: Salakhetdinov Shamil <mcp2004 at mail.ru>
Date: Wed, 4 Mar 2009 15:38:59 -0800
Subject: Re: Re[2]: [dba-VB] Scrum & C# - VS versions we have

> Shamil,  I was referring to the nic configurations within the VM workstation
> application.  you should see under the settings for the VM the different
> types of NICs you can use.  the VM Network Configuration utility is more for
> fine tuning things like IP ranges or adding additional nics that you want to
> behave in a different way... my case I have a wifi and a LAN nic.  so I have
> my wifi be the bridge nic and the WIFI be the NAT, it's the way I chose to
> configure it but you can do so any which way you want.
> 
> 
> -Francisco
> http://sqlthis.blogspot.com | Tsql and More...
> 
> 
> 2009/3/3 Salakhetdinov Shamil <mcp2004 at mail.ru>
> 
> >
> > Hi Francisco,
> >
> > You're welcome to observe the project progress!
> >
> > Thank for your information on VMWare.
> > It should be easy to fix I guess but I must say it's not clear yet here how
> > to do that:
> >
> > Maybe from the following info from my "VMWare Manager Virtual Networks"
> > form
> > you can just point me what should be changed? (I must say I didn't read the
> > VMWare docs):
> >
> >
> > =====================================
> > [Summary]
> > VMNet0 (Bridged) - Bridged to an automatically chosen Adapter -
> > 255.255.255.255
> > VMNet1(Host-Only) - A private network shared with the host - 192.168.116.0
> > - Enabled
> > VMNet8 (NAT) - Used to share the host's IP Address - 192.168.119.0 -
> > Enabled
> >
> > [Automatic Bridging]
> > [x] Automatically choose an available physical netwrok adapter to bridge to
> > VMNet0
> >
> > Excluded Adapters (Do not attempt to Bridge to teh following adapters)
> > - Interl(R) Pro/Wireless...
> > - Broadcom 440x 10/100 Integrated Controler
> > - Blutooth Device (Personal Area Network)
> >
> > ? Maybe exclude some of them - I do use only wireless adapter to
> > communicate with my LAN
> >
> > [Host Virtual Network Mapping]
> > VMnet0 - Bridged to an automatically choses adapter
> > VMnet1 - VMWare Network Adapter VMnet1
> > VMnet8 - VMWare Network Adapter VMnet8
> >
> > [Host Virtual Adapters]
> > VMWare Network Adapter VMNet1 - VMNet1 - Enabled
> > VMWare Network Adapter VMNet8 - VMNet8 - Enabled
> >
> > [DHCP]
> > VMNet1 - 192.168.116.0 - 255.255.255.0 - vmnet1
> > VMNet8 - 192.168.119.0 - 255.255.255.0 - vmnet8
> >
> > [NAT]
> > VMNet host:  VMNet8
> > =======================================
> >
> > Thank you.
> >
> > --
> > Shamil
> >
> > -----Original Message-----
> > - Show quoted text -
> > From: Francisco Tapia <fhtapia at gmail.com>
> > To: Salakhetdinov Shamil <mcp2004 at mail.ru>, "Discussion concerning Visual
> > Basic and related programming issues." <dba-vb at databaseadvisors.com>
> > Date: Tue, 3 Mar 2009 08:28:40 -0800
> > Subject: Re: [dba-VB] Scrum & C# - VS versions we have
> >
> > > Shamil,  Generally the network errors may be due to the settings in your
> > VM
> > > for the nic card.  The settings are  to set the nic as Bridged,  NAT or
> > > Host-Only.  Setting as Bridge makes the VM act like a standalone pc where
> > > you can communicate from your host to the guest and the guest back to the
> > > host as if each was it's own hardware pc.  Setting it as NAT, then you
> > have
> > > essentially a firewall on the guest pc and you can't reach it from the
> > host
> > > you can only go from guest to host.  Host-Only is a nice feature in that
> > the
> > > guest pc can only talk to the host.  The host pc will be able to work as
> > > normal, and will also have access to the guest pc via the network.
> > >
> > > my typical settings are to setup vm workstations as bridged.
> > >
> > > btw, I was reading through this thread and while I am not familiar enough
> > > with C# I'd like to observe the project as I know I'd learn a great deal
> > > from it.
> > >
> > > I do have VS2008 std.
> > >
> > > -Francisco
> > > http://sqlthis.blogspot.com | Tsql and More...
> > >
> > ><snip>
> >
> 
>