Solution to for VMs to access multiple vlans - one for management, one for iSCSI file storage?

I have an ESX 4.1 host, and an iSCSI SAN, and a vCenter server all sitting in the same VLAN 100 on a switch (which I intended for iSCSI traffic). The SAN is going to serve as storage space for my virtual machines, and as file storage. One the ESXi host, I've plugged in NIC's I've dedicated to iSCSI traffic into the proper ports on that VLAN 100 on my switch.

I've plugged another NIC on my ESXi host  into a port on my switch dedicated to my actual network (management - VLAN 200), and this is the NIC the booted virtual machines actually use for network traffic.

Here's where it gets tricky (for me at least). I'd like to have one virtual server dedicated to being my file server (mounting an iSCSI share on VLAN 100), but I want it also to be accessed from my management VLAN 200, but I'm not sure how to accomplish this.

Additionally, I'll have a few other situations where I'd like to have access to VLAN 100 from systems networked in VLAN 200, such as a terminal server where I can run the vSphere Client from.

I have no idea how to achieve this, so any help would be appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

you can add multiple network interfaces to the virtual machine and assign them in different vlan`s so that way you can access all the vlans.
Justin CAWS Solutions ArchitectCommented:
Like c0s said, just add another virtual network adapter to the VM and assign it to the port group you have configured for the VLAN you want access to.  Give that adapter an IP address on that VLAN and Windows will figure out how to route it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial

Example would be

Virtual Switch: vSwitch 0 (iSCSI)

VLAN100 attached to Physical Addapter (Nic 1)

vmkernel port (iSCSI1)
iSCSI1 (iSCSI Nic) (ip address of vmware iSCSI san)

virtual machine port group
File server (iSCSI Nic) (ip address of iSCSI san)

Virtual Switch: vSwitch 1 (Management)

VLAN200 attached to Physical Addapter (Nic 2)

virtual machine port group
File server (Lan Nic) (ip address of Lan)
Server A (Lan Nic) (ip address of Lan)
Server B (Lan Nic) (ip address of Lan)

If at all possible adding a dual or quad port nic would give you more options on redundancy and separation of network

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.