Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Unable to connect to WHS console or connect through Remote Access RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I am seeing a couple people posting nearly identical problems in the last couple days. I was able to connect to my WHS console 2 days ago (that was the last time I tried), when I tried this afternoon I enter my password and hit enter and receive the error "This Computer cannot connect to your home server. Check 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" My network appears to be working as I am able to interact with files (add, remove, open etc) on my server, as well as connect to the internet. This made me decide to try to connect through Remote Access, assuming it was an issue with the console application and to workaround it, but I receive the error: "Remote Desktop can't connect to the remote computer for one of these reasons: 1) remote access to the server is not enabled 2) the remote computer is turned off 3) The remote computer is not available on the network" Again options 2 and 3 are verifiably false as I can connect to files on the server. I can't disprove the first one, but I am unsure how that would be turned off on its own. It has been over 2 months since I connected to the server through remote desktop and my server is an HP model that does not have the connections needed to access it other ways. I have also tried to connect to it through various computers. 2 different operating systems ( Windows 7, and Vista). This is worrying me a little as I have much of my important files backed up on this server. The connector is showing me green status. I have restarted it, the computers I was trying to connect to it, and even the switch that connects them. I haven't seen a solution to this, anyone have a resolution or information on why this started occurring?
    Thursday, July 23, 2009 4:44 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Posted on another post was that openDNS was the problem, having tried that, it solved my issue. openDNS must be removed as the dns server and windows 7 and windows vista start working perfectly again through connector and remote desktop.
    • Marked as answer by Amnis Friday, July 31, 2009 7:44 PM
    Friday, July 31, 2009 7:44 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Try to shut down and reboot your machine. Press the power button once to start a shutdown. Wait until the machine is off. Then press power button again to restart.
    LightsOut - Power Management for Windows Home Server http://www.home-server-blog.de/add-ins/lightsout/#en
    Thursday, July 23, 2009 6:08 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    oops sorry, when I said "I have restarted it", it was referring to the server. After waiting about 2 hours this afternoon for error to resolve itself I restarted my WHS by the method mentioned. It shut down successfully, restarted successfully without any error messages. However the problem persists even to this moment.
    Thursday, July 23, 2009 7:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Some more questions:

    1. Can you still access the shares (either from the tray icon or from explorer window?  (type \\yourservername\shares in the address bar, replace "yourservername with the name of your server)
    2. Did you manually set a fixed IP address for the server or are you using DHCP?
    3. Have you recently installed any software (Add-ins) on the server
    4. Have you recently made any changes to your network configuration? (new router, changes in router config, new firmware on router)
    5. Have recently installed or modified (Third Party) firewall or internet security applications
    6. Can you reach the server from outside your LAN (only if you have remote access configured)
    7. Are the status lights on the HPServer all solid blue?

    Thursday, July 23, 2009 11:30 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    1. Shares still work fine, whether accessed through explorer or WHS connector. I can use files just fine. 2. manually set IP 3. No new addins in about 4-6 months 4. exact same network configuration for about 6-8 months 5. There are no anti-virus or security software on server, and one of the computers is currently only using windows firewall as it was just reformatted. Other has windows firewall with the new Microsoft security essentials anti virus that I am beta testing. I have been beta testing it for about a month now. 6. no remote access set 7. status lights are all solid blue
    Thursday, July 23, 2009 12:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Posted on another post was that openDNS was the problem, having tried that, it solved my issue. openDNS must be removed as the dns server and windows 7 and windows vista start working perfectly again through connector and remote desktop.
    • Marked as answer by Amnis Friday, July 31, 2009 7:44 PM
    Friday, July 31, 2009 7:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Posted on another post was that openDNS was the problem, having tried that, it solved my issue. openDNS must be removed as the dns server and windows 7 and windows vista start working perfectly again through connector and remote desktop.
    I am not trying to be an a$$, but I am using OpenDNS, alway have and always will. No problems. I would question how good of an answer "openDNS was the problem" really is. However, it worked for you and that's good, but I don't see any problems while using it as my dns server. I've run WHS, XP, Vista and Win7 and had no poblems.

    Cruise
    Friday, July 31, 2009 9:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Posted on another post was that openDNS was the problem, having tried that, it solved my issue. openDNS must be removed as the dns server and windows 7 and windows vista start working perfectly again through connector and remote desktop.
    I am not trying to be an a$$, but I am using OpenDNS, alway have and always will. No problems. I would question how good of an answer "openDNS was the problem" really is. However, it worked for you and that's good, but I don't see any problems while using it as my dns server. I've run WHS, XP, Vista and Win7 and had no poblems.

    Cruise
    I have been using openDNS for over a year, so I to am surprised this was the issue. But all I can say is that starting around the 20th of July my Windows 7 and windows vista computers lost their ability to connect to my server. I was even unable to open up the browser to get a new version of the connector at http://myserver etc etc. Someone mentioned in another article that they solved it by taking off openDNS and so I figured it was worth a shot. I tried to connect to the WHS before I made a change just to make sure nothing happened today that made it work, still got the same error. Then I opened up my router options, changed the DNS server settings back to default, hit apply, the router did not have to restart or anything, I tried logging into my WHS again, and it went right through.

    I had no problems until ten or so days ago either. But I have been seeing people with similiar issues popping up around here recently, and so once I found a solution for me I wanted to share it because it may be the same for them. Sounds like your not one of the people having connection issues recently, and I am glad for that. But it is simply undeniable that taking my router off of openDNS fixed the connection issues I have been having.
    Friday, July 31, 2009 9:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I had no problems until ten or so days ago either. But I have been seeing people with similiar issues popping up around here recently, and so once I found a solution for me I wanted to share it because it may be the same for them. Sounds like your not one of the people having connection issues recently, and I am glad for that. But it is simply undeniable that taking my router off of openDNS fixed the connection issues I have been having.

    Sounds to me like your network got out of sync with OpenDNS.  If you have a dynamic IP address from your ISP, and you don't have anything telling OpenDNS that your network changed, then you'll get this problem - you can't ping the other PC's on your home network.  If you log into OpenDNS from one of your home computers and view your defined networks, you'll see right away if your IP address registered with OpenDNS is different than the IP address you are browsing from. 

    You can get around this by using a client that runs on a PC on your home network which keeps your OpenDNS network definition updated.  (look on the OpenDNS site for links to download).  I use my WHS machine, since it's always running.

    So while removing OpenDNS will let you connect to your other PC's, hence solving the problem, it does so at the cost of foregoing the benefits of OpenDNS.  That's a cost I'm not willing to pay.

    Good luck!


    Tim Dallmann
    Monday, September 28, 2009 10:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    [truncated]
    So while removing OpenDNS will let you connect to your other PC's, hence solving the problem, it does so at the cost of foregoing the benefits of OpenDNS.  That's a cost I'm not willing to pay.
    I used to use OpenDNS when Bellsouth was my ISP. My network suffered as a result of being on Bellsouth. For that and other reasons I switched to Cox. When I did, the added value of OpenDNS was diminished, but this isn't a comparison of broadband providers.

    I've read elsewhere that large-scale content providers distribute their sources to improve delivery. Reportedly, if you use OpenDNS, those distribution schemes don't get calculated correctly by the provider. Your location apparently gets based on the location of the OpenDNS server, rather than your location. Maybe true, maybe not.

    In any case, I installed the OpenDNS client on my WHS server itself. It's always on, when a workstation is on. That kept my DHCP IP refreshed. I never had a problem locating my server by name.

    Chris
    Gainesville, FL
    Thursday, October 1, 2009 12:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hey i ot a problem with my server and it realy anoying ive only had it for a day. bascially what happens is that i can log into the WHS console but then shortly afterwards it freezes goes blue and the closes saying the same message as in the first post basiclaly something to do with the server not being connected

     

     i think the cause is the an add in that i installed the other day but i cant say for sure. I dont have remote acces becuase the server is connect directly in my computer but i can still access my shared folders. and i cant switch on remote acces and i dont think it is switched on. any help would be appreciated.

     

    many thanks

    Saturday, January 22, 2011 12:56 AM