Connect to virtual machine from host

I am running Virtual Server 2005 and have a single virtual machine called "WIN03_MOSS".  This virtual machine is running Windows Server 2003 OS and has an instance of Sharepoint running on it.

I'm working on developing Sharepoint sites and have Sharepoint Designer 2007 on my host laptop.  I'd like to connect to WIN03_MOSS using the host computer because then I can work in full-screen mode and just connect to the remote server as I normally would if I actually had a physical Sharepoint server.

Everything is running on a single laptop that is not connected to any network.  How do I get my laptop to connect to my virtual machine running Windows Server 2003?  I can see the server and connect through Remote Control on the Admin website but I don't like working in such a small screen considering I will be test developing web sites.
LVL 5
MageDribbleAsked:
Who is Participating?
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.

Todd MummertCommented:

You should be able to use remote desktop.   You have to enable it in the guest machine in control panel -> system -> remote access  (I think).      Then assuming you have the guest reachable via the network (either bridged or local)...then just use remote desktop to login to the machine

0
Andres PeralesCommented:
Well when you remote to the WIN03_MOSS instance using RDP set your diplay settings to match you laptop screen and when you remote it you should be at full screen resolution.
Same applies if you are using the Virtual Machine Remote Client once connected just change you display settings.
0
MageDribbleAuthor Commented:
I am having issue with the network connectivity.  This laptop is not connected to any network (neither wireless nor wired) so I installed the Loopback Adaptor.  I setup the Virtual Machine to be 10.50.50.1 and I set my desktop to be 10.50.50.100 but I can not get them to connect.

How do I properly setup the Loopback Adaptor to get them to communicate?
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

Andres PeralesCommented:
Alright, when you setup you configuration in your Virtual Admin Website make sure that your VM is using the loopback adapter as it's network card!
0
Todd MummertCommented:

Try the following steps to setup both the host and guest correctly.    I am more familiar w/ VMware...  but others may be able to assist you.

http://technet.microsoft.com/en-us/library/cc708341(WS.10).aspx

0
MageDribbleAuthor Commented:
The Loopback adapter is setup as the virtual network for the VM WIN03_MOSS in the Admin website.
0
Andres PeralesCommented:
On your network properties under the general tab, do you have Virtual machine network services checked for the Loopback adapter?
0
MageDribbleAuthor Commented:
yes
0
Andres PeralesCommented:
under your VS Admin Site...under Virutal Networks you created a new virtual network and have it utilizing the MS Loopback Adapter and the connected check box is checked...
Under virtual Machine configure Network adapters the connected to is the network you created!
0
MageDribbleAuthor Commented:
I did exactly that but still does not connect.
0
Todd MummertCommented:

can you show the output of "ipconfig /all"  and "route -n" from both guest and host?

0
Andres PeralesCommented:
configure you ms loopback adapter to be 10.50.50.1 with a subnet mask of 255.255.255.0
then configure you network adapter in you virtual machine to 10.50.50.10 with a subnet mask of 255.255.255.0 and a gateway of 10.10.50.1
see what you get then?
0
MageDribbleAuthor Commented:
Host:

route -n didn't give any results.  It spit out basically help info regarding the route command

IP Config Results
Windows IP Config:
Host Name: Dev1
Primary DNS Suffix:
Node Type: Broadcast
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Wireless Network Connection 2:
Media State: Media Disconnected

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix:
Description: Microsoft Loopback Adapter
Physical Address: 02-00-4C-4F-4F-50
DHCP Enabled: No
IP Address: 10.50.50.1
Subnet Mask:  255.255.255.0
Default Gateway:
DNS Servers: 127.0.0.1


Virtual Machine (Client):

IP Config:
Host Name: LITWAREDEMO
Primary Dns Suffix: litwareinc.com
Node Type: Unknown
IP Routing Enabled: No
WINS Proxy Enabled: No
DNS Suffix Search List: litwareinc.com

Ethernet Adapter Local Area Connection 2:
Connection-Specific DNS Suffix:
Description: Microsoft Loopback Adapter
Physical Address: 02-00-4C-4F-4F-50
DHCP Enabled: No
IP Address: 10.50.50.100
Subnet Mask: 255.255.255.0
Default Gateway: 10.50.50.1
DNS Servers: 127.0.0.1
0
Todd MummertCommented:
sorry...   my bad --   netstat -rn

0
Andres PeralesCommented:
get rid of your DNS entries and leave them blank...
0
Andres PeralesCommented:
and from you workstation can you ping 10.50.50.1, 1 being your self?  And from the VM can you ping 10.50.50.100?
0
MageDribbleAuthor Commented:
Results for netstat
Host (Windows XP)
Network Destination	Netmask		Gateway		Interface	Metric
10.50.50.0		255.255.255.0	10.50.50.1	10.50.50.1	30
10.50.50.1		255.255.255.255	127.0.0.1 	127.0.0.1	         30
10.255.255.255		255.255.255.255	10.50.50.1	10.50.50.1	30
127.0.0.0		         255.0.0.0	         127.0.0.1 	127.0.0.1	         1
224.0.0.0		         240.0.0.0	         10.50.50.1	10.50.50.1	30
255.255.255.255		255.255.255.255	10.50.50.1	10.50.50.1	1
255.255.255.255		255.255.255.255	10.50.50.1	2		1
Persistant Routes: None
 
Virtual machine (Client)
 
Network Destination	Netmask		Gateway		Interface	Metric
0.0.0.0			0.0.0.0		10.50.50.1	10.50.50.100	30
10.50.50.0		255.255.255.0	10.50.50.100	10.50.50.100	30
10.50.50.100		255.255.255.255	127.0.0.1	         127.0.0.1	         30
10.255.255.255		255.255.255.255	10.50.50.100	10.50.50.100	30
127.0.0.0		         255.0.0.0	         127.0.0.1	         127.0.0.1	         1
224.0.0.0		         240.0.0.0	         10.50.50.100	10.50.50.100	30
255.255.255.255		255.255.255.255	10.50.50.100	10.50.50.100	1
Default Gateway:	10.50.50.1
 
Persistant Routes: None

Open in new window

0
Andres PeralesCommented:
On your network properties under the general tab, do you have Virtual machine network services checked for your wireless NIC or Wired NIC, is your wireless NIC on?
0
MageDribbleAuthor Commented:
Peralesa - wireless is off and Virtual Machine Network is checked for my Loopback Adapter.  In regards to your other post, I can ping locally (host can ping host and VM can ping VM but I can not get the host to ping VM or VM to ping host)

I appreciate both Peralesa and Climbqunks help on this - this has been very frustrating for me over the past 4-5 days.
0
Todd MummertCommented:

I think the gw for the 10.50.50.0 network is wrong on the client.... if you try to access 10.50.50.1  from the client I don't see how it would get off the box.   But I admit to not fully understanding how MS uses the loopback adapters for this.  


on the client, try:

route delete 10.50.50.0

route add 10.50.50.0 mask 255.255.255.0 10.50.50.1

0
Andres PeralesCommented:
Check the virtual machine network for your wireless card / ethernet NIC.
What is the status of your Windows Firewall, is your firewall on the host machine off?  Turn it off for testing purposes!
 
0
MageDribbleAuthor Commented:
Climb - i tried route delete 10.50.50.0 on the Virtual machine but there is no route for 10.50.50.0 on the Virtual Machine.  It said "The route specified was not found"

Pera - The only thing the virtual machine sees is the Loopback Adapter which is all it should be seeing.  Firewalls off on all machines and no connectivity.
0
Andres PeralesCommented:
I am starting to think that your other network card needs to be on / enabled for this to work!
0
MagnuzCommented:
Just my 5 cents: have you allowed Internet Connection Sharing for your host's Internet connection? I believe this is required for the loopback adapter to work. Cheers, Magnuz
0
itprotocallCommented:
sometimes i have seen issue with the 'virtual networks' - create a new one and add the guest & loopback adapter to it.. should work.

although you have done this, just to refer again to confirm
http://www.experts-exchange.com/Microsoft/Applications/Virtual_Server/Q_24307785.html

in the host add an entry for the ip/hostname of guest in the ...\etc\Hosts file... and vice versa.
0
MageDribbleAuthor Commented:
itprotocall - thanks for the link.  I restored my laptop using the original disk last night to bring it back to how it was last week thinking maybe I did something wrong somewhere along the way.

Here's what I did this morning on a clean machine:

- Installed IIS
- Installed Virtual Server 2005
- Installed VMRCPlus
- Installed Sharepoint VHD
- Started Sharepoint VM (WIN03_WOSS)

This is where I got into the networking stuff.  I didn't disable anything.

- Turned off the manual switch for wireless adapter
- Added Loopback Adapter to host OS
- Configured IP to be 50.50.50.1 with subnet 255.255.255.0

Logged into WIN03_WOSS
- Added Loopback Adapter to Windows Server 2003 (on virtual machine)
- Configured IP to be 50.50.50.10 with subnet 255.255.255.0

Switched back to Windows XP (host OS)
- Logged into Virtual Server Admin Website
- Changed "Internal Network" to use Loopback Adapter

Opened command prompt
- tried to ping 50.50.50.10 (virtual machine)
----- No Response
- tried to ping 50.50.50.1 (itself)
------Ping successful


Logged onto virtual machine
- tried to ping 50.50.50.1 (host OS)
----- No Response
- tried to ping 50.50.50.10 (itself)
------Ping successful


So I appear to be back where I started.  :(  Any suggestions?
0
GreatGermCommented:
Here is a pretty full walkthrough from Bil Simser that appears to fill in the blanks: http://weblogs.asp.net/bsimser/archive/2009/04/20/using-the-loopback-adapter-and-sharepoint.aspx
0
itprotocallCommented:
the only thing different in my setup (its working fine for me) is:

Logged into WIN03_WOSS
- Added Loopback Adapter to Windows Server 2003 (on virtual machine)
- Configured IP to be 50.50.50.10 with subnet 255.255.255.0

i did Not add a loopback in teh virutal machine... just gave the IP to the physical adapter of the VM.

give the address 50.50.50.10 to the normal NIC of the VM and then connect this NIC to 'internal network'... and give it a try.
0

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
itprotocallCommented:
if you do not want to give the ip 50.50.50.10 to the primary NIC in the VM.. then add a 2nd NIC and give it this IP.

adding a loopback in the VM will not work... as there is no way you can add this loopback to 'internal network'
0
MageDribbleAuthor Commented:
son of a gun...i got rid of the loopback adapter on the virtual machine and setup the NIC and it worked.

i feel the monkey being lifted off my back as i type.  Thank you all for your help!
0
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
Microsoft Virtual Server

From novice to tech pro — start learning today.