Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS Remote Difficulties - HELP! RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I hope someone can help me; I am using WHS and have logged in on the WHS console previously, several times, on other computers.  I've also been able to remote in on my XP PRO machine previously.  For two days in a row, I have not been able to access either machine unless I sit in front of the server, logon and stop/restart some of the services for Remote.  After that, I can logon without a problem to either machine.  However, when I wake in the morning, and attempt to logon, I get, "The remote connection to the computer timed out.  Please try again."  I have a verified connection with a D-LINK 634M Router; and have opened ports 80, 443, 4125 and 3389.  What am I doing wrong?
    Monday, March 8, 2010 10:34 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Okay; I've read the previous responses and am willing to take all of those in to account.  Odd enough, when I woke this morning, I could actually log on remotely!!!?!!  A simple shutdown did the trick???  I'll have to check later to confirm this, however...  will let you guys know in the next 24 hours.  I hope it was this simple.  What would a shutdown due compared to a restart option?

    I shut the system down and let it sit for about 15 minutes, 8 hours ago...  I can't believe it would be THAT simple; yet, unlike the previous mornings, everything works.

    Wednesday, March 10, 2010 12:02 PM

All replies

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

    Have you tried rebooting your router? If you are having a problem with more than one computer the problem looks like it is not with Windows Home Server.

    Cheers,
    Al
    --
    Monday, March 8, 2010 2:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you already try the first method to fix anything - Reboot the server?
    Best greetings from Germany
    Olaf
    Monday, March 8, 2010 9:30 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have rebooted the router, re-booted the server and the desktop - I can only access the files associated with sharing and the personal folders when logging in by entering the domain - and it doesn't matter where I am.  I cannot access anything else remotely.  UPnP is up, I also just opened port 3389.  (I thought it was open previously - my error)  Still get nothing.
    • Edited by HKevin Tuesday, March 9, 2010 2:23 AM
    Tuesday, March 9, 2010 1:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Okay; as of 839 (US-EST); I uninstalled 3.5 .net SP1 and turned off automatic updates (I really hate to do that).  I rebooted the router and server again.  As of 857, I am able to access the console, remote to server and remote to my desktop.  However, I'm willing to bet I will not be able to login when I get up in the morning.



    Actually, updated as of 1039 (US-EST); It is back to timing out.
    Tuesday, March 9, 2010 2:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have rebooted the router, re-booted the server and the desktop - I can only access the files associated with sharing and the personal folders when logging in by entering the domain - and it doesn't matter where I am.  I cannot access anything else remotely.  UPnP is up, I also just opened port 3389.  (I thought it was open previously - my error)  Still get nothing.
    You don't need to forward port 3389 for Remote Access.
    Tuesday, March 9, 2010 4:40 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I hope someone can help me; I am using WHS and have logged in on the WHS console previously, several times, on other computers.  I've also been able to remote in on my XP PRO machine previously.  For two days in a row, I have not been able to access either machine unless I sit in front of the server, logon and stop/restart some of the services for Remote.  After that, I can logon without a problem to either machine.  However, when I wake in the morning, and attempt to logon, I get, "The remote connection to the computer timed out.  Please try again."  I have a verified connection with a D-LINK 634M Router; and have opened ports 80, 443, 4125 and 3389.  What am I doing wrong?
    What services do you have to stop/restart in order to get it to work?  Do you have any add-ins/applications installed on the server?  If so, which ones?
    Tuesday, March 9, 2010 4:44 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Everything I've been reading suggested to open 3389; obviously didn't make a difference.  I have no add-ins/applications installed.  I installed an anti-virus (clamwin) and ccleaner 2.9.  It is a new install.  Now preparing to work, I will have to get back later to examine and post the services...
    Tuesday, March 9, 2010 12:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Self built machine?
    NVidia graphics card? If so, check the FAQ How to handle error message “The Password is incorrect” attempting console access.
    Anything to see in the event log of the server or the client?
    Best greetings from Germany
    Olaf
    Tuesday, March 9, 2010 6:56 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, self built.

    GIGABYTE GA-G31M-ES2L LGA 775 Intel G31 Micro ATX Intel Motherboard
    Intel Pentium E5200 Wolfdale 2.5GHz 2MB L2 Cache LGA 775 65W Dual-Core Desktop Processor
    4 MB A-DATA 800MHZ DDR2 Ram
    320GB SATA 3.0 16MB Cache 7200 RPM Maxtor Hard Drive
    ANTEC 400W Powersupply

    Motorola Surfboard modem, DOCSIS 3.0.  Using CAT-6 cables...

    No graphics card; using the onboard video.

    just a standard build - for personal and business use.

    Interesting thought guys; I shut the server down and let it sit for about 15 minutes.  When I restarted it, I again had full access remotely - without rebooting the router.  The problem must be with the server; a setting or something - I still can't figure it out, I'm sure it will time out again.

    I've been stopping and restarting all of the remote services and found it apparently is not the issue - at first, it certainly appeared to be.  Would a reinstall without following updates do the trick?

    Strange - I'm also getting a red X by "Verifying that your remote website is available from the internet." when attempting to repair.  From other blogs I'm reading, this will not be an issue?  Other suggestions?

    Wednesday, March 10, 2010 3:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, self built.

    GIGABYTE GA-G31M-ES2L LGA 775 Intel G31 Micro ATX Intel Motherboard
    Intel Pentium E5200 Wolfdale 2.5GHz 2MB L2 Cache LGA 775 65W Dual-Core Desktop Processor
    4 MB A-DATA 800MHZ DDR2 Ram
    320GB SATA 3.0 16MB Cache 7200 RPM Maxtor Hard Drive
    ANTEC 400W Powersupply

    Motorola Surfboard modem, DOCSIS 3.0.  Using CAT-6 cables...

    No graphics card; using the onboard video.

    just a standard build - for personal and business use.

    Interesting thought guys; I shut the server down and let it sit for about 15 minutes.  When I restarted it, I again had full access remotely - without rebooting the router.  The problem must be with the server; a setting or something - I still can't figure it out, I'm sure it will time out again.

    I've been stopping and restarting all of the remote services and found it apparently is not the issue - at first, it certainly appeared to be.  Would a reinstall without following updates do the trick?

    For starters, you installed an A/V which (at least looking at their website) is not WHS-specific (that might be causing your problem), plus you installed CCCleaner.  FYI, installing any application (and, for that matter logging into the server desktop) is unsupported on WHS.  You could try a Server Reinstallation and don't install any add-ins or applications and see what happens.  (However, you do want to install all WHS updates.  Make sure you use the Update Now button in the WHS Console to do that.  Keep doing that until it says there are no more updates to install.)

    Strange - I'm also getting a red X by "Verifying that your remote website is available from the internet." when attempting to repair.  From other blogs I'm reading, this will not be an issue?

    That particular warning means http://xxxxx.homeserver.com doesn't work (which requires port 80 to be open).  In my case, I get that warning as well, but that's because I don't forward port 80 (I only forward 443 and 4125, then use https://xxxxx.homeserver.com for my web address).

    Other suggestions?

    Considering it's intermittent, I would lean towards a hardware issue (more specifically, a flaky NIC/ethernet cable/port on the switch/etc.)
    Wednesday, March 10, 2010 4:43 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi, 

    With all that info I would concur with Kariya21 and say it is probably your network drivers as RealTek cards have been known to cause problems.  Perhaps you can try these drivers from gigabyte on your Windows Home Server:

    http://www.gigabyte.com.tw/Support/Motherboard/Driver_Model.aspx?ProductID=2889&ost=xp#anchor_os 

    LAN
    Date Description Version Size
    2010/03/05 Realtek PCIe LAN Driver
    Download from :  
    Asia   Asia(China)   America   Europe   Europe(Russia) : ftp / http    		 5.742.1125.2009 3.08 MB

    Also you might want to look into updating network drivers on your client machines if they also use RealTek network drivers.

    Cheers,
    Al
    --
    Wednesday, March 10, 2010 10:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Okay; I've read the previous responses and am willing to take all of those in to account.  Odd enough, when I woke this morning, I could actually log on remotely!!!?!!  A simple shutdown did the trick???  I'll have to check later to confirm this, however...  will let you guys know in the next 24 hours.  I hope it was this simple.  What would a shutdown due compared to a restart option?

    I shut the system down and let it sit for about 15 minutes, 8 hours ago...  I can't believe it would be THAT simple; yet, unlike the previous mornings, everything works.

    Wednesday, March 10, 2010 12:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Well folks, that appeared to be the issue.  A simple shutdown???  I sincerely appreciate the responses and the assistance.  Now I'm having issues configuring a HP K80 printer on the server.  I understand WHS doesn't appreciate HP much...
    Saturday, March 13, 2010 12:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sometimes the network driver or something else may have a memory leak or ressources are getting consumed, but never given free again - in this case a reboot helps usually for a while. Besides that, switch the thing off and on again is usually one of the first troubleshooting methods for any device - including WHS ;-)
    Best greetings from Germany
    Olaf
    Saturday, March 13, 2010 9:52 PM
    Moderator