Can Mesh install on wireless computer connected to home workgroup?

Locked Can Mesh install on wireless computer connected to home workgroup?

  • Thursday, April 24, 2008 3:26 AM
     
     
    I have successfully installed Mesh on 3 of my 4 workgroup computers, all wired connections.  However, on the 1 computer in the workgroup that is connected wirelessly, the install wasn't successful.  It seemed to install, but just hung at the Starting Mesh stage.  I tried repair a couple of times, and I tried installing with my AV program disabled, but no luck.  Is this a known issue?
    Walter B

All Replies

  • Thursday, April 24, 2008 4:08 AM
    Owner
     
     Answered
    Walter, could you try to exit and restart Live Mesh by following these steps:
    1. Right Click the Live Mesh icon in the systray
    2. Click Exit
    3. Once completed, click Start and select Live Mesh under All Programs. This will restart Live Mesh

    If Live Mesh is still not responsive, please submit a bug on Microsoft Connect at
    http://connect.microsoft.com and select Live Mesh Tech Preview. Submit a bug under Feedback and please follow the direction for attaching your servicing logs.

    Thank you,

    Nadia
  • Thursday, April 24, 2008 2:26 PM
     
     
    Will do Nadia.  I see that Jan has this problem as well. 

    Her bug: https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=339814&SiteID=425
    Walter B
  • Thursday, April 24, 2008 3:34 PM
     
     
    Nadia Fortini - MSFT said:

    Walter, could you try to exit and restart Live Mesh by following these steps:
    1. Right Click the Live Mesh icon in the systray
    2. Click Exit
    3. Once completed, click Start and select Live Mesh under All Programs. This will restart Live Mesh

    If Live Mesh is still not responsive, please submit a bug on Microsoft Connect at
    http://connect.microsoft.com and select Live Mesh Tech Preview. Submit a bug under Feedback and please follow the direction for attaching your servicing logs.

    Thank you,

    Nadia



    Bug submitted : https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=339867&SiteID=425
    Walter B