>I don't recall if this was brought up here before, but I thought I'd
>poll the community to find out if this is a known problem.
>
>I upgraded my OS from 10.3.9 to 10.4.6. Now, I'm not able to connect to
>locally running web sites in VPC either by name and IP address. The
>connection times out at the ping level regardless. I'm using VPC Shared
>Networking. I can get at external Internet sites like Microsoft or
>Google, but not locally defined sites running on my MacOS 10.4 system.
>
>I have smaller partition running 10.3.9 which I installed from scratch.
>I installed VPC and updated to 7.02 and pointed VPC to the 10.4 virtual
>disks. VPC can access them just fine. And I can access local sites
>running on MacOS 10.3.9 and the regular Internet.
>
>IPFORWARDING is turned on in both 10.4 and 10.3.9. I use a wired
>Linksys Router connecting the Macintosh and my Laserwriter to a Comcast
>cable modem. Prior to the router, I connected directly to the modem and
>used a dumb 4-port hub. The router allowed me to do the NAT translation
>on 10.3.9 and "see" the MacOS sites in VPC 7.02.
>
>Was something changed in 10.4.6 that breaks VPC networking? Sounds like
>some sort of security hole got closed or something. Is there a
>workaround?

> If you're trying to access something on the Mac hosting VPC using NAT,
> it's not going to work. In general, you must use the Virtual Switch
> for Mac-Windows communication.
>
>
> On Mon, 01 May 2006 00:41:04 -0700, Michael Vilain
> <(email address - cut out)> wrote:
>
> >I don't recall if this was brought up here before, but I thought I'd
> >poll the community to find out if this is a known problem.
> >
> >I upgraded my OS from 10.3.9 to 10.4.6. Now, I'm not able to connect to
> >locally running web sites in VPC either by name and IP address. The
> >connection times out at the ping level regardless. I'm using VPC Shared
> >Networking. I can get at external Internet sites like Microsoft or
> >Google, but not locally defined sites running on my MacOS 10.4 system.
> >
> >I have smaller partition running 10.3.9 which I installed from scratch.
> >I installed VPC and updated to 7.02 and pointed VPC to the 10.4 virtual
> >disks. VPC can access them just fine. And I can access local sites
> >running on MacOS 10.3.9 and the regular Internet.
> >
> >IPFORWARDING is turned on in both 10.4 and 10.3.9. I use a wired
> >Linksys Router connecting the Macintosh and my Laserwriter to a Comcast
> >cable modem. Prior to the router, I connected directly to the modem and
> >used a dumb 4-port hub. The router allowed me to do the NAT translation
> >on 10.3.9 and "see" the MacOS sites in VPC 7.02.
> >
> >Was something changed in 10.4.6 that breaks VPC networking? Sounds like
> >some sort of security hole got closed or something. Is there a
> >workaround?

>Curious. And that begs the question, why does it work in 10.3.9 and
>10.4.2 but not 10.4.6? If it shouldn't have, what security hole got
>closed? Can it be reopened?

> On Mon, 01 May 2006 12:54:20 -0700, Michael Vilain
> <(email address - cut out)> wrote:
>
>
> >Curious. And that begs the question, why does it work in 10.3.9 and
> >10.4.2 but not 10.4.6? If it shouldn't have, what security hole got
> >closed? Can it be reopened?
>
> Using Shared Networking from Windows to the Mac should have never
> worked, it's a limitation of the NAT VPC uses. IIRC, it never worked
> before. VPC for Windows has the same limitation, as did previous
> versions of VPC, the documented solution has always been to use
> Virtual Switch for host-guest communication.
>
> The "shared" networking option that I remember allowing this to work
> was the Shared Sockets option.
>
> Since Shared Networking in VPC is NAT from the Mac, any requests that
> would be send from Windows on that Mac would be essentially ignored by
> the Mac since they would appear to be from itself.

>In article <(email address - cut out)>,
> Steve Jain <noreply.-at-.essjae.com@> wrote:
>
>> On Mon, 01 May 2006 12:54:20 -0700, Michael Vilain
>> <(email address - cut out)> wrote:
>>
>>
>> >Curious. And that begs the question, why does it work in 10.3.9 and
>> >10.4.2 but not 10.4.6? If it shouldn't have, what security hole got
>> >closed? Can it be reopened?
>>
>> Using Shared Networking from Windows to the Mac should have never
>> worked, it's a limitation of the NAT VPC uses. IIRC, it never worked
>> before. VPC for Windows has the same limitation, as did previous
>> versions of VPC, the documented solution has always been to use
>> Virtual Switch for host-guest communication.
>>
>> The "shared" networking option that I remember allowing this to work
>> was the Shared Sockets option.
>>
>> Since Shared Networking in VPC is NAT from the Mac, any requests that
>> would be send from Windows on that Mac would be essentially ignored by
>> the Mac since they would appear to be from itself.
>
>Ah. That explains it. Seems that what VPC calls apples the Mac calls
>bananas. How Gateian.
>
>Anyway, I restarted VPC XP with Virtual Switch networking, and alls well.
>
>Thanks for the clarification and help!