VPC 6.1 and OS X networking together on a PowerBook G4

Nov 07, '03 09:37:00AM

Contributed by: kdkinsey

Discovery through adversity once again. After applying the AirPort 3.2 update on my Powerbook G4 1GHz (sans-AirPort extreme), I discovered Virtual PC 6.1 with virtual switch (DHCP) could no longer "see" Mac OS X and vice-versa, both on the AirPort interface logged into an AirPort network. This lead to desperate experimentation that panned out.

Caveat: no testing beyond my experience of AirPort 3.2 update / Panther / VPC 6.1. AirPort card and built-in Ethernet required. Mileage probably will vary.

Situation: I deploy struts apps into Tomcat under OS X that utilizes JDBC to a SQL Server, as well as a socket-based Java interface to a Business Intelligence server, both running under VPC 6.1.

Here's how to get this to work with no Ethernet cable attached to the built-in Ethernet interface and having not joined any AirPort network (although AirPort interface must be on). It doesn't get more isolated than that in a car traveling down the interstate!

  1. Under System Preferences, set up Sharing to share "AirPort" internet connection to "Built-in Ethernet." Apparently OS X will allow this, even though the built-in Ethernet interface is inactive. A check with ifconfig will confirm what's happening with regards to Panther's DHCP server. Even more amazing is that VPC will use it.

  2. Ensure Virtual PC virtual switch is pointing to "built-in Ethernet" and crank up (for me, XP Pro) with DHCP under Windows.
That's it. After that, OS X can ping the VPC instance at the DHCP address assigned to it via internet sharing. VPC can ping the OS X AirPort IP address (for me, a fixed IP unrelated to any active AirPort network in the car). The apps communicate brilliantly between one another - no wires/routers/hubs necessary. Quite fast, too!

I hope this hint helps some folks - it certainly helped me!

Comments (7)


Mac OS X Hints
http://hints.macworld.com/article.php?story=20031101210620201