weird network problem

Discussion in 'Installation and Configuration of Parallels Desktop' started by jmshttn, Jun 19, 2007.

  1. jmshttn

    jmshttn Bit poster

    Messages:
    2
    I've been getting a weird network problem under parallels 3.0 (and possibly also 2.5 tho can't remember exactly).

    Basically, using Shared Networking, am able to browse only SOME sites correctly from inside Parallels, e.g. www.google.com is ok, but www.microsoft.com is not! On the native mac side, all sites work fine. I get this both in my old upgraded XP installation and also a brand new fresh vista installation.

    Looking thru the forums I've tried various things - using Disk Utility -> Repair Permissions, and also changing to Bridged Networking and back again, but nothing seems to help!

    Any ideas anyone?

    J
     
  2. dkp

    dkp Forum Maven

    Messages:
    1,367
    As a test if you don't mind, install FireFox or Safari for Windows and try side-by-side tests of web sites to see if some fail in IE but work in other browsers.

    This is a repeating problem and appears to have started with Parallels 3.0. Your symptoms are quite typical of those seen by other recent posters.
     
  3. jmshttn

    jmshttn Bit poster

    Messages:
    2
    Yup - same problem in both Firefox and IE 7... Haven't tried Safari tho.

    One observation - tho may be coincidental - while I can access www.microsoft.com on the mac, I am unable to ping it either in os x or parallels. Google however is pingable in both.
     
  4. dkp

    dkp Forum Maven

    Messages:
    1,367
    Microsoft appears to have disabled ICMP responses so ping won't work there.
     
  5. paddler

    paddler Bit poster

    Messages:
    9
    I have had luck with connection issues by disabling the network driver in parallels tools. Been running that way for months with no problems. I'm still on v2.5 so I can't attest to whet broke in 3.0

    If you can get to some websites and not others it might be a DNS issue. In Windows networking try manually setting your main dns server to 4.2.2.6 and see if that helps.
     

Share This Page