> Sorry, don't mean to repost this - but as it addresses numerous posts
> I've found here, thought I'd reword the topic and get a little more
> detailed. I originally posted this hint on MacOSXHints.com, after
> spending quite some time figuring it out, and (up to 10.4 and 7.0.2),
> it worked flawlessly.
>
> Here's the deal:
>
> On 10.3 and VPC 7.0.1, using Airport:
>
> When you open the URL "http://10.0.1.x/~user/directory/index.php" in
> IE6 under VPC WIN XP SP2 with Shared Networking enabled:
>
> The hybrid system works flawlessly (where x is the number provided
> under System Preferences for Apple Web Sharing, ~user is your username,
> directory is the directory you created in your "Sites" folder, and
> index.php is an example of a PHP file being executed by Apache under
> Apple's Personal Web Server. No other hacks or workarounds required.
>
> Along comes 10.4, and this no longer works. I've seen all sorts of
> crazy technical workarounds for it, with people typing jargon into
> Windows and the Mac Terminal, etc. to force some type of loopback
> nonsense...
>
> So my question is this - can someone with the latest version of 10.4
> and 7.0.2, using a single machine with an airport card and an airport,
> PLEASE test this simple process to see if the old reliable method is
> back to working again?
>
> I've heard that Apple had made some goofs with 10.4 that were causing
> other problems, and I'm hoping that the most recent upgrade (or one of
> the upgrades) fixed this problem.
>
> None of us bought Macs to go futzing around with command lines and DOS
> commands - plus I'm fairly certain that executing those commands would
> cause me other unforeseen problems.
>
> The way things are set up now (with 10.3 and 7.0.1) - I simply launch
> VPC, go back and forth testing between IE6 and Firefox until they
> agree, and I move on with my life. No interference with my other
> network settings, no interruptiong of my internet connections, no
> "loopback" cords, nothing else needed - just my iBook, VPC, and an
> airport express.
>
> It worked at one time, it should work again.
>
> So if you have a setup you could test this out on, I would greatly
> appreciate it.

> I've been through the upgrade once already - and it was a no go.
>
> I was hoping that someone with the latest version of VPC and Tiger
> could just run a simple test (like I outlined above) and let me know
> whether or not it was now working.
> I've seen all sorts of crazy technical workarounds for it, with people typing jargon into
> Windows and the Mac Terminal, etc. to force some type of loopback
> nonsense...
> None of us bought Macs to go futzing around with command lines and DOS
> commands - plus I'm fairly certain that executing those commands would
> cause me other unforeseen problems.
>
> It worked at one time, it should work again.

> The configuration of accessing the host OS X may have worked in VPC 6
> under Panther but does not work in VPC 7.0.2 under OS X 10.4.3. It
> appears the way Shared Networking now works in Tiger the OS X system is
> firewalled off from VPC. ...