Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Anybody else having remote access issues? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    When I left home this morning, my WHS box was apparently happy.

    Now I can't remote access it. My browser just comes up "cannot display".

    The address resolves and pings.

    My only change anytime recently was the recent QFE earlier this week.
    Thursday, November 27, 2008 2:26 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Had the same situation yesterday - tried to connect via homeserver.com and failed. Used my dyndns.org address and could access the server that way. Clicking test in settings/remote/domain configuration  caused the console to disappear after a while (I don't thing that I clicked the Close button somehow). After reopening  the console remote access via homeserver.com was functional again.

    Best greetings from Germany
    Olaf
    • Proposed as answer by Al Jarvi Thursday, November 27, 2008 11:31 AM
    • Marked as answer by brubberModerator Thursday, December 4, 2008 7:59 PM
    Thursday, November 27, 2008 8:08 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm going to bet that Windows Live Custom Domains has hiccupped again. Which is annoying for those who rely on their home server's remote access features (to say the least).
    I'm not on the WHS team, I just post a lot. :)
    Thursday, November 27, 2008 2:30 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I also have QFE installed, no problem with remote access, all pages display as they should.

    Did you make any customisations to the default web page / use other then standard ports?
    Thursday, November 27, 2008 4:48 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yeah, same problem. I left my server back at my apartment earlier today and came home for thanksgiving. Got here and it was working fine, come back about 2 hours later and no remote access. Can also ping the server. Dont know why it would just magically stop working out of the blue like that.

    Really stinks because all of my photos are on my server and I was planning on showing them to the family for thanksgiving, now I cannot figure out whats wrong with my server unless i drive two hours back home.
    Thursday, November 27, 2008 7:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    There was a pretty big patch today.  I can't access my server via the website either but remote desktop is working.  So same problem.
    athlon 3400, 2gb ram, 9 drives totaling about 3.5 tbs.
    Thursday, November 27, 2008 7:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just an update, I completely unconfigured the remote access via the console and reconfigured everything again.  working great now.
    athlon 3400, 2gb ram, 9 drives totaling about 3.5 tbs.
    Thursday, November 27, 2008 8:00 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Had the same situation yesterday - tried to connect via homeserver.com and failed. Used my dyndns.org address and could access the server that way. Clicking test in settings/remote/domain configuration  caused the console to disappear after a while (I don't thing that I clicked the Close button somehow). After reopening  the console remote access via homeserver.com was functional again.

    Best greetings from Germany
    Olaf
    • Proposed as answer by Al Jarvi Thursday, November 27, 2008 11:31 AM
    • Marked as answer by brubberModerator Thursday, December 4, 2008 7:59 PM
    Thursday, November 27, 2008 8:08 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Olaf Engelke said:

    Had the same situation yesterday - tried to connect via homeserver.com and failed. Used my dyndns.org address and could access the server that way. Clicking test in settings/remote/domain configuration  caused the console to disappear after a while (I don't thing that I clicked the Close button somehow). After reopening  the console remote access via homeserver.com was functional again.

    Best greetings from Germany
    Olaf

    LOL... I did not even know I had a problem before coming across this thread...:-)

    Thanks... That procedure worked for me also...
    MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"
    • Edited by Al Jarvi Thursday, November 27, 2008 11:33 AM Added sentence
    Thursday, November 27, 2008 11:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Olaf Engelke said:

    Had the same situation yesterday - tried to connect via homeserver.com and failed. Used my dyndns.org address and could access the server that way. Clicking test in settings/remote/domain configuration  caused the console to disappear after a while (I don't thing that I clicked the Close button somehow). After reopening  the console remote access via homeserver.com was functional again.

    Yes, that's more or less what I'd try. If I were home. And didn't actually need remote access to work.

    Thursday, November 27, 2008 2:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm going to bet that Windows Live Custom Domains has hiccupped again. Which is annoying for those who rely on their home server's remote access features (to say the least).
    I'm not on the WHS team, I just post a lot. :)
    Thursday, November 27, 2008 2:30 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Dick Watson said:

    When I left home this morning, my WHS box was apparently happy.

    Now I can't remote access it. My browser just comes up "cannot display".

    The address resolves and pings.

    My only change anytime recently was the recent QFE earlier this week.


    I updated my server as soon as the update came out on Tuesday (from work).  Rebooted fine and the Remote Access website continued to work after the reboot.  However, the ability to logon to a client PC remotely didn't work until I got home (because the Connector software needed to be updated on the clients).
    Thursday, November 27, 2008 6:38 PM
    Moderator