Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS not accessible via Console or Remote Desktop RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    WHS was working excellent until about a week ago when I could no longer access it through either the Console login or Remote Desktop. Trying to connect either way returns an error. However, backups are still happening (I see the "Backup Complete" message in the morning), I can access files on the server through Explorer, and the taskbar icon is showing "Network Healthy". I have tried restarting the machine and attempting to access it from other computers to no avail.

    Since the server is in the basement and headless, I wanted to see if any of you had any
    ideas before I drag it up here or a monitor and keyboard down there.
    Saturday, August 11, 2007 3:30 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hello,

    Hopefully this helps some people....

    I recently installed WHS Outlook to see if it was of any value to me.  When I uninstalled, i came across the same error.  I was reading your posts looking for the answers to why i was not able to access the Console or my server via RDP.  I was quite upset when I read so many articles saying that I would need to reinstall and potentially lose data.  I did however, find another fix/work-around in which I did not have to completely reinstall my WHS OS.  I found that for whatever reason, the registry entries that deal with the RDP/remote services had disappeared.  Supposedly located in:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
    Control\Terminal Server\WinStations\RDP-Tcp


    My entire "RDP-Tcp" folder and its registry entries were gone.


    My fix:

    1st:  I uninstalled the add-in manually following other posts on the Internet.

    2nd: I manage two Home Servers and was able to Export the registry "RDP-Tcp" from the 'good' server and import the .reg file to the appropriate location on the 'bad' server. I restarted my machine and all of my RDP/Console services worked fine.

    I'd be willing to email the .reg file pending a review for any security risks to my data if anyone is interested and would like to try the fix.


    Again, I hope this helps some people with the same issues.  Or maybe someone already figured this out....this post is a bit older.



    Jon

    • Proposed as answer by Kev Reid Wednesday, February 11, 2009 9:03 AM
    • Marked as answer by Olaf EngelkeModerator Wednesday, February 11, 2009 8:48 PM
    Wednesday, February 11, 2009 2:46 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    What is the error that you get?

     

    Saturday, August 11, 2007 4:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just curious, are you trying to access it rdp with an IP?  Could the ip have changed?  ping server to see if it resolves

     

    Grey

     

    Saturday, August 11, 2007 5:41 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Via the console login it says:


    "The computer cannot connect to your home server. Click your network connection and make sure your home server is powered on. If your home server has recently restarted, try again in a few minutes."

    Via Remote Desktop it says:

    "The client could not connect to the remote computer." (Plus a bunch of Microsoft-ese.)


    Saturday, August 11, 2007 11:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hm, I was connecting by host name but I just tried connecting by IP and was able to get in by Remote Desktop. I don't think the IP has changed since install but it's not set as static on my router. (Changing that now.) Unfortunately, I still can't connect via the console. At least I'm partway there...
    Saturday, August 11, 2007 11:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would suggest setting your server with a static IP address (either through the server or by assigning its NIC MAC address an IP address from the router), then flush the DNS on the computer that cannot connect (I'm not sure if the WHS Console uses that info or not, but it couldn't hurt).  Go to a command prompt window and type:

     

    ipconfig /flushdns

     

    Hope that helps!

    Saturday, August 11, 2007 11:54 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Progress Smile

     Now reinstall the connector and see what happens.  (Just for me please)

     

    Still.....Grey

     

    Sunday, August 12, 2007 1:08 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Well, reinstalling made things worse, unfortunately. When installing the connector software, it searches for (and finds!) the server but when I enter my password, I get an error screen that reads:

    "An unknown error has occurred."

    Can't get past that screen which means I can't install the connector software which means no backups. I have no idea what's gone on here. Nothing has change on my network or my machine to cause these weird errors.
    Monday, August 13, 2007 6:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same problem that started a few days ago and cant seem to fix it.  Tried everything maybe time to reload the server and start from scratch.

    Monday, August 13, 2007 4:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also have the same problem. Have static IP, can reach server via remote but not from my main desktop. 

    Tuesday, August 14, 2007 12:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Great error msg eh?

     

    Are you using the cd to install the connector?

     

    BTW...What is the name of your server?  could there be another?

     

    Start> run> cmd>  Ping server

     

    What is the ip?  Is it correct?

     

    Start> run >  \\server

     

    Stuff should open, click to software and try the connector install there.

     

    Still

     

    Tuesday, August 14, 2007 1:09 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having a similar issue.  I got a message a few weeks ago that a drive needed repairing - I think it was the drive with the OS.  I ran the repair and rebooted a few times and ever since I haven't been able to log into console, even from the WHS machine itself.  But I can still access the shares and the backups seem to be occurring.  I haven't had the time to play around with it anymore but what should I do - try to do the reinstall of WHS with the upgrade option so as not to lose my data?

     

    Tuesday, August 14, 2007 4:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ok, I fixed my issue with help from another, related thread. Here's what I did:

    1. Set a static IP for the server on my router.

    2. Entered the IP address into the hosts file (c:\windows\system32\drivers\etc):
    192.168.0.104    SERVERNAME

    3. Reinstalled the Connector software.

    All problems are fixed. My guess is the IP may have been changed and then some sort of DNS caching got everything screwed up. It went south pretty easily, though.
    Tuesday, August 14, 2007 3:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well you do not set a static ip for a box in your router.  If you want to set a static IP for a box you do it on that box.

     

    For example, most routers are say 192.168.0.1 and they hand out 100 ip's in the range of say 192.168.1.100 to 199

     

    So you would assign your box (desktop or home server) an ip of say 192.168.1.10

     

    10 will not be handed out buy the router so you are okay.

     

    If you had done ping server from a cmd prompt you could have seen where it was pointed.

     

    I am the worlds worst at suggesting an entry in the hosts file, but it is a bandaid/work around for a problem that can be fixed.

     

    Out of curiousity, did you change the name of your server from server?  If so, was there another box named server?

     

    Still....

     

    Tuesday, August 14, 2007 10:37 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think it rather depends on your router, Grey. Mine can make the whole range available, and does provide a section for assigning static IPs. (That said, I have a DC so that does the DHCP Smile )

     

    I hate assigning to the hosts file, because it doesn't resolve the problem. I think it's a name resolution issue at the ISP's DNS servers, which are doing a "smart lookup" and getting it wrong (appending a default domain and looking for server.com for example). It can be sidestepped by unplugging the router from the Internet, so the name is forced to resolve locally, though sometimes it needs the DNS cache to be flushed.

    Tuesday, August 14, 2007 11:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well I know they can make the entire range avaialable, just out of the box they do not.

     

    I bet I know your problem, I saw it once before.

     

    On your desktop you have set dns to an outside ip, not the router.

     

    Tell me eh eh eh is that so ? LOL

     

    WHS is KEWL !!

     

    Still...

     

    Thursday, August 16, 2007 2:39 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    LOL! Good to see you in such humour, Grey.

     

    My DC (DHCP server) sends its unresolved DNS enquiries to the ISP, using the same settings as the router.

     

    WHS is HOT!!

    Thursday, August 16, 2007 1:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am new to WHS but with many years IT experience.
    I have installed WHS and attached 5 PCs around the house. Everything was working well until some time over the weekend. Sunday afternoon I think.
    I had been testing WHS Outlook Add-in and it had proved itself so I decided to buy the full version.
    When the key arrived I tried to attach to the server using the connector from my Laptop - It failed. I tried RDC it failed. I tried every PC I own and all had stopped working.
    I had to go to the server to install the registration key. Then set about trying to research why this might have happened.
    I already had my server defined by IP address in each systems host file.
    Remote desktop is enabled on every PC - it is only the server that fails.
    I can png my server by its name - so name resolution is not the problem.
    I tried going out to the internet and coming back in but got the same problem.
    I have a BT home hub and I have read and implemented all the ports suggested for WHS including 4125 RDP.

    Prior to it failing I had been using connector to remove an addin (Disk Management) which took far too long in fact I inadvertantly stopped the connector before the uninstall had finished. I had to re-install and remove it again to finally get it to leave the system. I did this directly on the server through the console just after I registered WHS outlook.

    It was when I tried to test the newly installed outlook that I realised the error was present.

    I have read somewhere that the problem seems to relate to the fact that nothing is listening on port 55000 in the server. I have not been able to find this post a second time so I don't really know how the user had tested it. But the firewall does have 55000 and 56000 opened.

    I have also ready that some people have got so desperate that they have performed a server rebuiuld to rid the problem.

    I am concerned about taking that approach because I would not want to lose my 3.5tb of data on the server when a new installation grabs the disks.

    Has anyone any ideas on how to solve this (i have followed the various microsoft posts to configure it)

    Windows connector toolkit troubleshooter runs and gives three pices of advice.
    1) The version of the Connector software does not match the version of Windows Home Server - I have uninstalled and re-installed from the servers software folders. This can't be true unless the wrong version is stored on the server. During the short time I have had WHS it has updated the connector twice. has it got his wrong?
    2) Windows Home Server Connector troubleshooting article - Already followed this artical in detail - this points at two things Name resolution and firewalls - I have tried dropping all firewalls including my router firewall - it doesn't make any diofference. The name resolution I already tested above.
    3) ReadMe for this tool - that is the readme for the connector troubleshooter tool. I have followed this and published to toolkit on the server so I can create and send error logs.

    Today it gave a fourth piece of advice
    4) Cannot connect to the server internal Web site (password hint page) - This leads to the following - I do have a godaddy certificate installed. I have today reset my BT home hub to factory settings and then reset the port forwarding as they were previously.

    The server internal Web services use TCP port 55000. This test may indicate that there is a problem with the Web services on your home server, but it is more likely that other problems are contributing to this issue.

    Check the following:

    • Your home server and home computers are connected to the same router. - Yes they are

    • Internet Information Services (IIS) is running on Windows Home Server. - yes it is running

    • The "WHS site" is started on IIS. - yes it is and I can connect to it over the internet using servername.homeserver.com

    • There is a security certificate installed on the "WHS site". - Yes there is and I don't get a certificate warning when I connect as above

    • TCP ports 55000 and 56000 are open on your Windows Home Server Windows Firewall. - Yes these ports are opened in the firewall defined as HTTP and HTTPS (there are two entries for each)

    If you need assistance with these tasks, contact Product Support. - I don't need assisance with the tasks but I do need help to resolve this problem.


    Sorry this is so long but as you will see I have undertaken all the various suggestions that have been posted against this issue.

    Thanks for any help you can offer

    Kev
    Tuesday, December 2, 2008 8:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    there are various possibilities, what happened.
    What for a server is it - self built or one of the known brands?

    WHS - Outlook? What exactly do you mean with that - did you install Outlook on the server? If yes, you should be aware, that the usage of WHS as desktop replacement is not supported (means, it may have unexpected side effects) and may be also denied by the EULA. Side effects can be caused also by each other software, i.e. NVidia drivers are known to break Remote Desktop connection and WHS Console access.

    Around the 25th you may also have received the last Windows Home Server update (KB957825) - you can try to uninstall this through Control Panel on the server and check, if this fixes the issue. (I had to go the uninstall/reinstall tour on my server for that patch also to fix some stuff.)

    Do you see any errors or warnings in the event log of your server?

    The toolkit seems not to like the latest upgrade, so it complains about different versions (maybe because there are indeed different versions also in the console, which are shown for you, btw?), even if this must not be true (at least I have read this in another thread).

    Just in case, a reinstall is coming, your data is still not in danger, as long as you get offered a server reinstallation (a new installation wipes all, but a server reinstallation will preserve your data and only wipe the OS system partition).
    Best greetings from Germany
    Olaf
    Tuesday, December 2, 2008 9:31 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the speedy reply. Here are my answers

     Self Build - it is my old Windows 2003 SBS

    Outlook is only installed on the server to enable WHS Outlook to work. Whs Outlook is an addin that makes a version of OWA available through the console. Outlook (the full application) is never run on the server except from the add-in. Even profiles are managed by the add-in.

    As this was working for several days before the insident I had mentally discarded it.

    Radeon 7000 Ve (Microsoft) drivers are installed.

    Windows Home Server update (KB957825) was installed 26th November - I think it was working after that but I can't b sure because I don't use connector or RDC every day. Most days it just runs. - I have uninstalled the update to see if the situation changes. Nonothing changed still can't connect with Console or RDC

    Even log is pretty clean - there are a few warnings and errors but I can accept each one as real - eg user failed to logon.    I do get a block of 6 disk errors when the system is restarted but after the system is running there are no more and chkdsk runs clean and the console says all drives are healthy. I have put this down to my Sata card being a bit slow to get started.  There are no services failing to start etc.

    It is beginning to look like a restore (I have seen this problem fixed by a restore several times in other forums)

    Thanks again

    Kev
    Wednesday, December 3, 2008 9:55 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just started to try a re-install to overcome this consol and RDC connection failure.

    I placed the original WHS installation disk in the CD drive.
    Re booted
    Loaded software in grey
    Initialised
    Then a set-up window appeared there were no options - just next - It said this will install WHS all previous data will be lost. So I chickened out.

    I do have external backups of all my important files but I have nearly 2tb of recorded video which is not on any external backup device. I really want to do a re-install rather than a fresh install is there any thing I can do to get a re-install option?

    Kev
    Wednesday, December 3, 2008 10:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Kev,
    on the right side of WHS New installation - is there an arrow down allowing to select the server reinstallation?
    If not, how are the disks configured? SATA controller in IDE mode?
    Is the system drive listed as volume 0 and physically connected to the first controller port?
    Best greetings from Germany
    Olaf
    Wednesday, December 3, 2008 11:46 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi when I insert the WHS installation CD and select boot from CD this is the sequence of events

    Black screen grey bar Windows is loading files.
    Black screen Microsoft green rolling bar
    Blue Glass screen - Set-up is initializing - blue progress bar in modal form
    Then I get the first installation screen
    Windows Home Server accross the top
    Left hand side
    Collecting information
    Dynamic update
    preparing installation
    installing windows finishing installation

    only the top one is highlighted as this is clearly the install sequence.

    to the centre and right there is a grey box with Welcome to Windows Home Server Installation accross the top
    and two active buttons Next or Cancel

    Do I have to go past here to get to the re-install screen - I have been cancelling at this point so as not to lose my existing system.

    On the disk question
    I have 2 160g IDE drives - one has the system on it.
    This is the configuration I originally built then I added 2 1TB Sata drives on a Sata card.
    Then I added two USb drives with a further 750gb each.

    I have been thinking of disconnecting the usb and Sata drives and starting the installation. Then on the first reboot attach the drives again so that windows can recognise them. Only problem is that the second IDE drive and the rest of the drives are part of the same drive D - therefore what happens if the D drive is reset while to system is being installed before the first re-boot.

    I really don't want to lose the data on these drives - I can recover most of it but the time it takes to rebuild 3.5 tb is an age.

    Thanks for your efforts

    Kev
    Wednesday, December 3, 2008 1:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    the sata is not set up as a raid

    Kev
    Wednesday, December 3, 2008 1:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Kev Reid said:

    Hi when I insert the WHS installation CD and select boot from CD this is the sequence of events

    Black screen grey bar Windows is loading files.
    Black screen Microsoft green rolling bar
    Blue Glass screen - Set-up is initializing - blue progress bar in modal form
    Then I get the first installation screen
    Windows Home Server accross the top
    Left hand side
    Collecting information
    Dynamic update
    preparing installation
    installing windows finishing installation

    only the top one is highlighted as this is clearly the install sequence.

    to the centre and right there is a grey box with Welcome to Windows Home Server Installation accross the top
    and two active buttons Next or Cancel

    Do I have to go past here to get to the re-install screen - I have been cancelling at this point so as not to lose my existing system.

    Yes.  Once you click Next, you should see a list of all of your hard drives.  Make sure they are all listed (then click Next).  After that, you should see a drop-down menu with 2 options:  Server Reinstallation (which should be the default) and New Installation.  You want Server Reinstallation.

    Kev Reid said:

    On the disk question
    I have 2 160g IDE drives - one has the system on it.
    This is the configuration I originally built then I added 2 1TB Sata drives on a Sata card.
    Then I added two USb drives with a further 750gb each.

    I have been thinking of disconnecting the usb and Sata drives and starting the installation.
     

    No, leave them connected.  Any drive that is part of the storage pool must be attached at the time of Reinstallation.

    Kev Reid said:

    Then on the first reboot attach the drives again so that windows can recognise them. Only problem is that the second IDE drive and the rest of the drives are part of the same drive D - therefore what happens if the D drive is reset while to system is being installed before the first re-boot.

    I really don't want to lose the data on these drives - I can recover most of it but the time it takes to rebuild 3.5 tb is an age.

    Thanks for your efforts

    Kev



    Wednesday, December 3, 2008 3:03 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks got as far as seeing the drives but my Sata drives are not showing - I remember the trouble I had getting the damn card working when I first built the server.  So I am currently rebooting in to the good OS to find out what the card and drivers are. I guess I will then have to burn them to a CD so that I can find them and load them before I go past the drives screen.

    is there a set of generic sata drivers on the install  DVD that can make progress a little quicker.
    My driver set is for the Sil3114 version 1.3.11.0
    drivers loaded are
    SI3114.sys
    SIwinAcc.sys
    and
    SiISupp.dll

    I havce navigated to my backup files for these drivers but when I load them I still don't see the drives.

    I feel deperatly close to having to d a fresh install and losing some of my data

    Thanks again for any help on this issue

    Kev
    Wednesday, December 3, 2008 3:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Kev Reid said:

    Thanks got as far as seeing the drives but my Sata drives are not showing - I remember the trouble I had getting the damn card working when I first built the server.  So I am currently rebooting in to the good OS to find out what the card and drivers are. I guess I will then have to burn them to a CD so that I can find them and load them before I go past the drives screen.

    I doubt a CD will help much.  You will need to install the drivers twice (once in the GUI portion, the second time in the text portion, when you press F6 to install drivers).  The only reliable method for the second (text) part is a floppy drive.

    Kev Reid said:

    is there a set of generic sata drivers on the install  DVD that can make progress a little quicker.
    My driver set is for the Sil3114 version 1.3.11.0
    drivers loaded are
    SI3114.sys
    SIwinAcc.sys
    and
    SiISupp.dll

    There are no SATA drivers on the DVD at all.  The underlying OS is Windows Server 2003, and SATA drives were not (widely) available back then.

    Kev Reid said:

    I havce navigated to my backup files for these drivers but when I load them I still don't see the drives.

    I feel deperatly close to having to d a fresh install and losing some of my data

    Thanks again for any help on this issue

    Kev


    My suggestion at this point:  Find a relatively high capacity (300 GB+) PATA drive and use that as your primary (drivers won't be an issue).  This way, if you ever need to reinstall again, it will be much simpler.
    Wednesday, December 3, 2008 3:51 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    How does a large Pata help I will still have 2TB of sata for data and a total of 3.5TB in all?
    I will atill have the problem of installing the Sata drivers after installation is complete therefore the drives will have to be added to the array and therefore be initialized.

    I am going to set about trying to get my sata drivers on to a floppy

    Fortunately there is an old floppy on the system

    Thanks

    Kev
    Wednesday, December 3, 2008 4:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I may not have been clear on this point - when I built the system it consisted of 2 160gb IDE drives. They are still there and one of them stil contains the system.

    Thanks again for all your helpfull comments _ ifeel I am making progress even if Iend up having to trash it and start again.

    Kev
    Wednesday, December 3, 2008 4:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Kev,
    you may be able to perform a server reinstall, if you can get the SATA drivers on a USB stick, so that the first stage of setup can access the SATA drives. Second (ancient looking) stage of setup may or may not request the drivers again on a floppy drive (since you say, an IDE drive is the primary drive, this may work without needing to provide the SATA drivers again  from other peoples experiences). So if your mainboard has a floppy connector and you have still a working floppy disk and its cable, you could attach it temporary.

    In case, still no server reinstallation is offered, you can try to save your data by disconnecting all data drives (pulling the cables!) during setup.
    • Check the D: drive (especially the subfolder shares in hidden folder DE) on the primary disk and store all files eventually found here somewhere else (USB stick, client disk, whatever).
    • If the data is secure, reinstall WHS on the disk and apply all updates.
    • Now attach the most empty data disk and boot the server up.
    • Login to the server locally.
    • In Windows Explorer, copy the content from DE\shares (again a hidden folder, so you have to toggle the show hidden files and folders option on your servers Explorer options) to either a share reachable through the desktop shortcut Shared folders on server or to a spare disk (USB drive maybe) or to a client PC network share with enough space to hold the data.
    • If this is completed, add the disk to the storage pool.
    • Now you can do the same with the next data disk, but simply copy the content to a subfolder in Shared folders on server. Some files my appear twice due to folder duplication on the old installation.
    Client backups will be lost in this process, but they are usually kind of redundant, since the client still exists.
    Best greetings from Germany
    Olaf
    Wednesday, December 3, 2008 8:24 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanka Olaf,

    I will need to find a few hours to implement this without interuptions - I will let you know how I get on.

    Regards

    Kev
    • Proposed as answer by jpg200 Wednesday, February 11, 2009 2:29 AM
    Wednesday, December 3, 2008 10:47 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hello,

    Hopefully this helps some people....

    I recently installed WHS Outlook to see if it was of any value to me.  When I uninstalled, i came across the same error.  I was reading your posts looking for the answers to why i was not able to access the Console or my server via RDP.  I was quite upset when I read so many articles saying that I would need to reinstall and potentially lose data.  I did however, find another fix/work-around in which I did not have to completely reinstall my WHS OS.  I found that for whatever reason, the registry entries that deal with the RDP/remote services had disappeared.  Supposedly located in:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
    Control\Terminal Server\WinStations\RDP-Tcp


    My entire "RDP-Tcp" folder and its registry entries were gone.


    My fix:

    1st:  I uninstalled the add-in manually following other posts on the Internet.

    2nd: I manage two Home Servers and was able to Export the registry "RDP-Tcp" from the 'good' server and import the .reg file to the appropriate location on the 'bad' server. I restarted my machine and all of my RDP/Console services worked fine.

    I'd be willing to email the .reg file pending a review for any security risks to my data if anyone is interested and would like to try the fix.


    Again, I hope this helps some people with the same issues.  Or maybe someone already figured this out....this post is a bit older.



    Jon

    • Proposed as answer by Kev Reid Wednesday, February 11, 2009 9:03 AM
    • Marked as answer by Olaf EngelkeModerator Wednesday, February 11, 2009 8:48 PM
    Wednesday, February 11, 2009 2:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Jon, I had found the same reference and I forgot to report back here to say that I had fixed it.

    Kev
    Wednesday, February 11, 2009 9:01 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi, Jon.

    I have the exact symptoms which you describe. I checked my registry, as you suggested, and I do have some folders and registry keys, but I don't know if they are complete.

    Would you mind sending me the relevant registry info? I think the easiest way to do it is to create a registry dump of only that section of the registry. It should create a ___.reg file.

    Many thanks.

    Mark Shneour
    mark@dotmom.com

    PS -- It's pathetic, dontcha think, how poorly documented WHS is? You'd think Microsoft would do a better job, OEM product or not....
    Thursday, May 21, 2009 8:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have experienced all the same systems that you have expressed here and others have express elsewhere. They seem to be tied around PP2, but I not sure. Everything was working one day and somewhere around PP2 upgrade they stopped. At first, I thought it was some of the Win7 machines, but then Vista started exhibiting the same symptoms. Rather than go the HOSTS route, I added the IP address of the WHS to the list of DNS servers in my DHCP scope (actually as the first one) and magically everything started working again. Don't know what caused it, but now I can use my Connector tray icon again and actually connect AND restore as needed. Hope this helps.
    Brent
    Friday, May 22, 2009 12:09 PM