none
WHS Client *used* to work RRS feed

  • Question

  • I have Vista x32 running as a virtual server under Vmware Fusion. I had been useing it with WHS to back it up for months. Some update to WHS forced an update of the client, now I'm screwed. It uninstalled the old client and the new client won't install with the message, "This operation cannot be completed at this time" or I get the message that it can't find the WHS, even though I have half a dozen drives successfully mapped to the server!

    I have tried all sorts of thinge, including running the software from a locanl copy, running it from the Software share, I even connected the notebook up directoy to the router off the cable modem. I have looked at dozens of posts conjured up with Google and Bing! searches - nothing works.

    I think it was the Power Pack update that did the dirty deed as all of my backs started failing. The other PCs on my network were able to install the client, even my Vista x64 Home Premium.



    SnoBoy
    Thursday, September 3, 2009 5:03 PM

Answers

  • Thanks to all who posted - you gave me some ideas that ended in success!

    Fixed - what I did was to add a hosts file entry for the home server since the ping to the server name wasn't successful (it had some wild IP address that didn't match the server's address at all. Then I opened a command prompt as administrator and ran the locally copied WHS client.

    Finally, success!
    SnoBoy
    Saturday, September 5, 2009 3:51 PM

All replies

  • I have Vista x32 running as a virtual server under Vmware Fusion. I had been useing it with WHS to back it up for months. Some update to WHS forced an update of the client, now I'm screwed. It uninstalled the old client and the new client won't install with the message, "This operation cannot be completed at this time" or I get the message that it can't find the WHS, even though I have half a dozen drives successfully mapped to the server!

    I have tried all sorts of thinge, including running the software from a locanl copy, running it from the Software share, I even connected the notebook up directoy to the router off the cable modem. I have looked at dozens of posts conjured up with Google and Bing! searches - nothing works.

    I think it was the Power Pack update that did the dirty deed as all of my backs started failing. The other PCs on my network were able to install the client, even my Vista x64 Home Premium.



    SnoBoy

    Are you able to successfully ping your server from your VM machine, both by name and by IP address?  Can you open a command prompt and run ipconfig /all on the client that doesn't work, one that does work, and the server, then post the results here?
    Friday, September 4, 2009 3:49 AM
    Moderator
  • Is the VMWare client in the same IP Subnet as the main stations or does it use it's own IP area?
    In later case you will have to change the behavior (or if this is unwanted, change the scope of Windows Firewall exceptions on WHS for some relevant components to allow connections from all networks).
    Best greetings from Germany
    Olaf
    Friday, September 4, 2009 6:56 AM
    Moderator
  • Thanks to all who posted - you gave me some ideas that ended in success!

    Fixed - what I did was to add a hosts file entry for the home server since the ping to the server name wasn't successful (it had some wild IP address that didn't match the server's address at all. Then I opened a command prompt as administrator and ran the locally copied WHS client.

    Finally, success!
    SnoBoy
    Saturday, September 5, 2009 3:51 PM
  • This points to a misconfiguration in DNS (external DNS server, attached DNS suffix, something like that).
    Best greetings from Germany
    Olaf
    Saturday, September 5, 2009 4:23 PM
    Moderator
  • Just means that sometimes you have to work around your ISP's DNS. ;-) 
    SnoBoy
    Saturday, September 5, 2009 4:31 PM
  • Thanks to all who posted - you gave me some ideas that ended in success!

    Fixed - what I did was to add a hosts file entry for the home server since the ping to the server name wasn't successful (it had some wild IP address that didn't match the server's address at all. Then I opened a command prompt as administrator and ran the locally copied WHS client.

    Finally, success!
    SnoBoy

    I just wanted to bump this thread as it provided the solution to a stubborn Vista machine's inability to find the server during Connector installation.  After this simple edit to the hosts file, all is well.
    Thursday, September 17, 2009 9:23 PM