Hitting the Host Webserver From The Guest OS

bmagierksi said:
Greatly appreciate the help! This just made my life easier for testing on IE :)
Click to expand...

Glad I could help. Now, like me, you can spend hours figuring out why your seemingly correct pages don't look right in IE. :)

Rob
 
rmineric said:
Glad I could help. Now, like me, you can spend hours figuring out why your seemingly correct pages don't look right in IE. :)

Rob
Click to expand...

Ha! Yes, way to many hours of fun adding CSS gimicks to fix IE :D
 
I'd like to second fattymelt's idea for some sort of reserved IP address. Just before I ran across this thread, I posted the same idea in a different thread here:
http://forum.parallels.com/thread1877-2.html

Parallel's is an amazing product. I can't believe the speed and stability, and this is just the first release. Excellent work guys. Keep it up.
 
It's a shame so many people doing web development are ignorant on the structure of IP networks. There's going to be no special addresses for Mac and VM. IP already provides all the means even for that particular purpose. You have several options:
1. On a healthy IP network a DNS server allows dynamic registration. Your Mac and Windows VM just need sensible name to be set. Use it!
2. You can assign a second static IP both to Mac and XP. You just need to make sure it's from private range and doesn't overlap any network you know of.
3. Use Host-Only Networking that provides stable addresses. Even further you can assign static addresses manually.
 
serv said:
It's a shame so many people doing web development are ignorant on the structure of IP networks. There's going to be no special addresses for Mac and VM. IP already provides all the means even for that particular purpose. You have several options:
1. On a healthy IP network a DNS server allows dynamic registration. Your Mac and Windows VM just need sensible name to be set. Use it!
2. You can assign a second static IP both to Mac and XP. You just need to make sure it's from private range and doesn't overlap any network you know of.
3. Use Host-Only Networking that provides stable addresses. Even further you can assign static addresses manually.
Click to expand...

Thanks for the words of encouragement, serv.

For me, using the Host-Only Networking with Internet Sharing did the trick. Tried this before, but XP didn't seem to pick up an IP address, which prompted my original post here. Once I had XP booted and grabbing an IP address 192.168.2.x from DHCP, I reconfigured the network settings on the VM to assign it the static IP of 192.168.2.2, and OS X gets 192.168.2.1. I'm still slightly concerned about Apache in OS X being open to the whole 192.168.1.x subnet, but I'll probably just take care of that by locking down the Listen or NameVirtualHost (all my local sites are name-based VirtualHosts) directives in my httpd.conf. Anyway, it seems to be working great.

For those who aren't clear on how to actually set up the Mac and Parallels to do this kind of networking, select Contents under the Parallels Help menu, then look under Managing Virtual Machines > Networking in a Virtual Machine > Host-Only Networking with Internet Sharing. For me, that was installed at this local URL: file:///Library/Parallels/Help//index1265681.htm

Again, awesome product.
 
Using the MS loopback adaptor?

Hi

Interesting thread; I've been having the same problem as everyone else. I need to be able to have my host and guest communicate with each other over IP, regardless of whether I am physically connected to a network or not; but I also want my guest to be able to access the internet when I _am_ connected to a network.

With other solutions I've tried historically on the Windows platform (as host), I've been able to configure this by:

1) Installing the MS Loopback Adaptor on both host and guest
2) Configuring Loopback on both host and guest to have static IPs such as 172.16.254.1 and .2

Now, when I was trying to solve this same problem with Parallels earlier today, I tried:

1) Install MS Loopback Adaptor on the Guest OS (WinXP); configure with 172.16.254.10
2) On the host OS (Mac OS 10.4.whatever), alias 172.16.254.1 to the loopback interface by doing the following via a shell : ifconfig lo0 inet 172.16.254.1 netmask 255.255.255.0 alias

Having done this, I can make sure that the IPs work by, in each machine, pinging locally to the relevant IP.

However, no matter what I try, I cannot get Host and Guest to ping each other in this configuration, and I can't for the life of me work out why.

I'm going to try the 'host-only with NAT' concept later -- once I solve a separate problem that this option is apparently broken in my install of parallels :mad: -- but I'd be interested to know why my first solution doesn't work.....

Thanks.

--&e
 
Hi

Yes -- that part is all fine and dandy, but only works if the host and the guest can already see each other over IP. In the CSSDEV example, for instance, it would appear that both host and guest are already configured on a 10.0.1.* network (perhaps by using the Parallels 'host-only' networking solution).

My issue is one step before this -- I need the host OS and the guest OS to be able to see each other (for example, by being able to ping the IP addresses directly). Once that works, the rest is just icing :)

--&e
 
so

Has anyone figured this out?

Getting the Windows machine to 'see' the Mac webserver without typing the allocated IP for the Mac?

Anyone?

A step-by-step, please?
 
You must log in or register to reply here.
Back
Top