Shared Networking not functioning.

Our House <bflathornNOSPAM@optusnet.com.au> wrote:

> When I use shared networking, Internet Explorer will no longer connect.

Is Windows set to use DHCP?

>>
>> Paris

>You will have to manually change the MTU if you're using
>broadband........ there is a program Dr.TCP that can be found on
>broadbandreports.com and there it will easily let you change you MTU to
>1492.
>

Why? I've built, supported, used, you name it with Windows systems
since 3.x and have never had to change the MTU to allow IE to connect
to the Internet.
Steve Jain, Microsoft MVP for Virtual PC for Windows
Website: http://www.essjae.com
*** All posts are provided AS-IS, no warranty, no QoS ***

Steve Jain wrote:

>>>Paris

>>
>>You will have to manually change the MTU if you're using
>>broadband........ there is a program Dr.TCP that can be found on
>>broadbandreports.com and there it will easily let you change you MTU to
>>1492.
>>

>
> Why? I've built, supported, used, you name it with Windows systems
> since 3.x and have never had to change the MTU to allow IE to connect
> to the Internet.
> Steve Jain, Microsoft MVP for Virtual PC for Windows
> Website: http://www.essjae.com
> *** All posts are provided AS-IS, no warranty, no QoS ***

Let's just say this is a "built-in feature" that has occured with
Version 7. Since there is no Shared Socket or Shared Packet this might
be the reason why this problem does exist.

Other people were saying its because of the IPv6 addresses thats enabled
on the Mac side that is causing the issue which is totally false, I have
tested it on quite a few Macs and it does not help anything by turning
it off.

Dialup Connections on the Mac most likely will need DNS addresses to be
put in while on broadband connections it will have to be MTU changing.

I am not saying all ISPs do require this, but I know Verizon is one of
them and I can't recall whether or not Comcast was another.

--
The Software Corner
http://www.thesoftwarecorner.com
Enhance your computing experience!

Steve Jain <essjae-No@Spam-hotmail.com> wrote:

>> You will have to manually change the MTU if you're using
>> broadband........ there is a program Dr.TCP that can be found on
>> broadbandreports.com and there it will easily let you change you MTU
>> to 1492.
>>

> Why? I've built, supported, used, you name it with Windows systems
> since 3.x and have never had to change the MTU to allow IE to connect
> to the Internet.

It depends on the nature of the broadband connection (DSL or cable), and
whether the PC is directly connected to the modem or whether there is a NAT
router inbetween.

There is usually no problem with cable, which supports an MTU of 1500.

DSL using PPPoE or PPPoA usually supports an MTU of only 1492. If the
PPPoE/PPPoA dialer is in Windows itself, that normally assigns itself a
correct MTU of 1492, so there should be no problem in this case.

If, however, the PPPoE/PPPoA dialer is within an external NAT router, and
the connection to Windows is plain ethernet, then Windows assigns the
connection an MTU of 1500, and Windows might not be able to easily tell that
the connection to the ISP supports an MTU of only 1492. The result might be
packet loss or long latency while recovery takes place. The best
performance in this scenario will be obtained if the Windows ethernet
connection is assigned an MTU by the user manually patching its
configuration, using a utility such as DrTCP.

However, all this might have nothing to with the original poster's problem.

--
Robin Walker
rdhw@cam.ac.uk

In article <1go8gcg.xoa9ly106r8d5N%neillmassello@earthlink.ne t>,
neillmassello@earthlink.net (Neill Massello) wrote:

> Our House <bflathornNOSPAM@optusnet.com.au> wrote:
>

> > When I use shared networking, Internet Explorer will no longer connect.

>
> Is Windows set to use DHCP?

Just to clarify, shared networking was working fine, out of the box with
a 100% standard install of VPC. No adjustments needed to either VPC or
XP. It has just stopped.


The cessation seemed to accompany the installation of security updates
for OS X.

I don't know if Windows is set to use DHCP. It worked before and now it
doesn't. I didn't change anything in the Windows settings.

This happened to me once. I needed to shut Windows down (not save
state), select Virtual Switch, boot windows, shut it down again, and
then switch back to Shared Networking.

I have basically the same Mac setup, 10.3.6 and the security patch
12/02/04. I am experiencing the same problems with not being able to
connect to the internet via IE explorer. IE seems to send the request
to the website but is not allowed to receive any information back. I
have played with all the firewall settings with no solution. My next
try will be to try and connect using the virtual switch option using
the mac ethernet connection for VPC 7 and the mac airport connection
for Safari, etc. Please post if you solve the problem.

mpramsey@comcast.net wrote:

> I have basically the same Mac setup, 10.3.6 and the security patch
> 12/02/04. I am experiencing the same problems with not being able to
> connect to the internet via IE explorer. IE seems to send the request
> to the website but is not allowed to receive any information back. I
> have played with all the firewall settings with no solution. My next
> try will be to try and connect using the virtual switch option using
> the mac ethernet connection for VPC 7 and the mac airport connection
> for Safari, etc. Please post if you solve the problem.

Problem solved...I Turned on the virtual switch in VPC 7 and set it to
ethernet. The wired connection into my wireless router is now the imac
ethernet port, and the imac airport connection remains my wireless
connection into my wireless router. Once I started VPC7 I went to the
command prompt and did the ipconfig/release and ipconfig/renew process
to update the VPC 7 ip address. In my router software I enabled the MAC
authorization and added both the imac ethernet mac address and the VPC
7 ethernet mac address to the mac authorization table. I turned on mac
authorization and the VPC 7 firewall. In the mac network settings under
the network port configurations I enabled both the airport and ethernet
check boxes and dragged the airpot selection to the top of the list.

In short I think upgrading to OSX 10.3.6 and the latest security update
of 12/02/04 does something to dis-allow the proper operation of the
shared networks function in VPC 7. BTW I tried the Dr TCP deal and
swapped the mtu number with no success. Hope this helps someone.