Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Remote desktop and port forwarding fail after updates. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Last week i installed WHS and all was working great. I let WHS configure my router (D-Link DI-614) and it configured fine. I setup the website connection info and that went fine. I could connect to it via the NET, take control of PC within my network through the WHS Website, everything worked fine. Then I pulled down all of the updates and the WHS website quit working, remote desktop won't connect (External or Internal network fails), and I got port forwarding errors. I tried everything the help files suggested and even reinstalled just incase I did something wrong to corrupt file, although the only thing i did was create a user account and connect a PC via the connector CD. After I reloaded it, it worked great again all night long. But the next morning it quit working again. This was after the updates pulled down through the automatic updates. The strange thing is, all of the other features like backups, share folders, and the remote console all work fine.

     

    Please help, I am lost and have no other ideas.

     

    Thanks,

     

    Shawn

     

    GIGABYTE GA-M68SM-S2 AM2 NVIDIA GeForce 7025

    AMD 64 X2 4000+ Brisbane

    SEAGATE BARRACUDA 500GB SATA 3.0GB/s

    A-DATA 2GB (2x1GB) DDR2800

    Monday, March 3, 2008 8:59 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi Eman and Deuce,
    do you have a NVidia or ATI graphiccard in your home server? If yes, the drivers for this card can break Remote Desktop (and that way also WHS console) access to the server (eventually also after an update of other components sharing the same ressources like .NET Framework).
    Uninstalling the video drivers or applying the following lines into the registry may help. (Save the next lines in a text file with the extension .reg and import it after logging in locally to your server in its registry, reboot the server.)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    “SessionImageSize”=dword:00000020

    (Btw. it is not a good idea to post different bugs in another persons thread.)
    Best greetings from Germany
    Olaf
    Saturday, March 21, 2009 2:43 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Please try Unconfigure, then Configure Domain name part of WHS Remote Access (WHS Console, Settings Menu, Remote Access).

     

    Instructions can also be found at http://blogs.technet.com/homeserver/archive/2007/11/26/the-windows-home-server-november-27th-update.aspx

     

    Another issue may be that the IP address of your WHS box changed after the update. In that case reconfiguring your router should help. If this is the case the best thing to avoid this problem from appearing after each update would be to assign a fixed IP address to your WHS box. You can do this by manually entering TCP/IP settings on your WHS box, or even better configure your network DHCP server (probably your router) to do this (DHCP reservation). Check your router manual for how-to.

    Monday, March 3, 2008 11:02 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, I actually tried all of this already. But for argument sake, i tried it all again and nothing. Every time i attempt to reconfigure the router it fails on the "Verilying remote access is available on your router". It is almost like the updates blew away everything regarding the webserver and remote desktop, but everything seems to be running accourding to the services. Is the a chance the updates would have affected the compatability with the router? Thus killing the configuration that was previously working before the updates? I don't know, i am lost.

    Tuesday, March 4, 2008 10:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Correction: I can not even connect to the WHS Console from another PC.

    Tuesday, March 4, 2008 2:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
     SConnett wrote:

    Well, I actually tried all of this already. But for argument sake, i tried it all again and nothing. Every time i attempt to reconfigure the router it fails on the "Verilying remote access is available on your router". It is almost like the updates blew away everything regarding the webserver and remote desktop, but everything seems to be running accourding to the services. Is the a chance the updates would have affected the compatability with the router? Thus killing the configuration that was previously working before the updates? I don't know, i am lost.

     

    If the router config page only shows (orange triangle) warning signs for the lines you mention there should be no problem as far as remote (web) access is concerned, as long as the router is configured properly. Normally the updates do not require you to reconfigure the router. However you may check portforwarding in your router. To check if remote access is working you can best test this from a remote system outside you network, and not simply go by the messages in the config pages.

     

    If you are also unable to access the WHS console from client PC's you may need to reinstall the connector software from \\server\software.

     

    Are you sure your WHS TCP/IP poroperties are properly configured? Did you check IP address, netmask, gateway, DNS server address of your WHS?

    Tuesday, March 4, 2008 3:07 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yep, I have check and rechecked the IP Settings. That is not a problem. Like I mentioned, it all worked prior to the updates running. And like I said earlier, I can not even hit the webpage by going to HTTP://localhost. It errors out the same it would from another PC on the network or the internet for that matter. I tried reinstalling the connector software and it still will not let me connect to the console. Though I can get in to the share folders fine.

     

    Also, I don't think it is a port forwarding issue any more. I remoted in to my router and put my desktop PC in the DMZ and I can remote desktop in to it from the NET fine. I had the WHS in the DMZ and still could not connect to it. My problem seems to be within the WHS completely.

     

    I really do not want to have to reload the server again as it will be the third time loading it. A co-worker mentioned reloading and manually installing the updates 1 at a time just to see which one it was that causes it to fail. Do you know of a location on the net that shows an actual list of update currently available for WHS with out having to be logged in to the server running the updates? I was curious to look at the list from work.

     

     

     

    Tuesday, March 4, 2008 4:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Status Update:

     

    Well, after additional playing around found what appears to be an issue when testing the firewall/port forwarding.

     

    Regardless what I did it would fail on Remote Access under Router configuration/setup. Turns out that someone ended up using the domain name I was using under 'old.livenode.com' and used it for 'old.homeserver.com' during a 17-day period. I ended up skipping the firewall setup and configured the domain name by creating a new domain under 'new.homeserver.com'. Low-and-behold, the firewall setup successfully and configured without error.

     

    Very surprised that there isn't a flag in the code to check against this!

     

    My issue is resolved..

     

     

     

    Hey Sconnect,

     

    I'm having the exact same problem as you are. Only happened after pulling the updates from Microsoft. The funny thing is, my other server which is running RC1 never had this issue. I was able to take the WHS RC1 server and connect it up and everything works perfect. Something in Microsoft updates broke the servers ability to connect remotely.

     

    Tuesday, April 1, 2008 12:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey Guys,

    Can someone close to uncle Bill (Microsoft) tell him that there was an update they sent to the W H S that corrupts remote desktop and Windows Home Server console connectors on the client PCs. No one should tell you otherwise. We are only human and we all make mistakes.

    What SConnett has gone through, I have done five reinstalls and every time the Server gets updates, the same thing happens again. Remote Desktop and the Connectors on the client PCs work fine before the updates. I have done many tests, all that mentioned previously and more!

    All remote shares and even automatic backup work fine but those two (Remote Desktop and the Connectors) are doing my head in!

    Please help!

    I have even thought about using OpenFiler or Virtualization with Windows Server 2008 Hyper-V but that means I can't use SageTV in the Server like I do with Windows Home Server.

    This info. is not important but for one of the machines I used in the tests.

    Component Details Subscore Base score
    Processor
    Intel(R) Core(TM)2 Extreme CPU Q6850 @
    3.00GHz 5.9
    5.4
    / Determined by
    lowest subscore
    Memory (RAM) 8.00 GB 5.8
    Graphics NVIDIA GeForce 8800 GTX 5.9
    Gaming graphics 2814 MB Total available graphics memory 5.9
    Primary hard disk 138GB Free (233GB Total) 5.4
    Windows Vista (TM) Ultimate


    Kind Regards.

    Eman.
    Monday, February 23, 2009 1:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Eman_Systems said:

    Hey Guys,

    Can someone close to uncle Bill (Microsoft) tell him that there was an update they sent to the W H S that corrupts remote desktop and Windows Home Server console connectors on the client PCs. No one should tell you otherwise. We are only human and we all make mistakes.

    What SConnett has gone through, I have done five reinstalls and every time the Server gets updates, the same thing happens again. Remote Desktop and the Connectors on the client PCs work fine before the updates. I have done many tests, all that mentioned previously and more!

    All remote shares and even automatic backup work fine but those two (Remote Desktop and the Connectors) are doing my head in!

    Please help!

    I have even thought about using OpenFiler or Virtualization with Windows Server 2008 Hyper-V but that means I can't use SageTV in the Server like I do with Windows Home Server.

    This info. is not important but for one of the machines I used in the tests.

    Component Details Subscore Base score
    Processor
    Intel(R) Core(TM)2 Extreme CPU Q6850 @
    3.00GHz 5.9
    5.4
    / Determined by
    lowest subscore
    Memory (RAM) 8.00 GB 5.8
    Graphics NVIDIA GeForce 8800 GTX 5.9
    Gaming graphics 2814 MB Total available graphics memory 5.9
    Primary hard disk 138GB Free (233GB Total) 5.4
    Windows Vista (TM) Ultimate


    Kind Regards.

    Eman.


    Hi,


    I don't think this is the same exact problem as the thread above as those posts were prior to the release of Power Pack 1 so those updates would no longer be on Windows Update but rather would be included in Power Pack 1. 

    Can you submit a bug on Connect for this?

    Thank you
    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Monday, February 23, 2009 3:48 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I believe I am experiencing a similar issue.

    I can perform a fresh reinstall of WHS, and I have verified I can remote desktop and connect via Internet Explorer before performing updates.

    Without making any other changes beyond performing all Windows Updates, after the updates have installed and the machine has rebooted all remote desktop and Internet Explorer access to WHS fails.  The Settings section for the router and web site still show as "working" and have the same green check marks for each of the services.  But for some reason after the Windows Updates have gone through I lose RD functionality...

    I have verified the internal IP assigned by the router to the server is still the same as well, and this very same thing happens on two totally different networks running two different routers/ISPs.

    If I have to uninstall and reinstall and skip every update I will...this is beyond frustrating at this point.  Any suggestions? =\

    Saturday, March 21, 2009 9:05 AM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Hi Eman and Deuce,
    do you have a NVidia or ATI graphiccard in your home server? If yes, the drivers for this card can break Remote Desktop (and that way also WHS console) access to the server (eventually also after an update of other components sharing the same ressources like .NET Framework).
    Uninstalling the video drivers or applying the following lines into the registry may help. (Save the next lines in a text file with the extension .reg and import it after logging in locally to your server in its registry, reboot the server.)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    “SessionImageSize”=dword:00000020

    (Btw. it is not a good idea to post different bugs in another persons thread.)
    Best greetings from Germany
    Olaf
    Saturday, March 21, 2009 2:43 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Fantastic Olaf, I uninstalled the Nvidia display driver and rebooted.  Works as it should now!!  =D

    Sorry about the thread hijack, but I really appreciate the answer.  Cheers!
    Saturday, March 21, 2009 6:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Eman and Deuce,
    do you have a NVidia or ATI graphiccard in your home server? If yes, the drivers for this card can break Remote Desktop (and that way also WHS console) access to the server (eventually also after an update of other components sharing the same ressources like .NET Framework).
    Uninstalling the video drivers or applying the following lines into the registry may help. (Save the next lines in a text file with the extension .reg and import it after logging in locally to your server in its registry, reboot the server.)

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    “SessionImageSize”=dword:00000020

    (Btw. it is not a good idea to post different bugs in another persons thread.)
    Best greetings from Germany
    Olaf

    I had the NVidia drivers installed on my WHS.  Your registry change fixed both my Console and Remote Desktop problems.

    THANK YOU, THANK YOU, THANK YOU
    Tuesday, May 19, 2009 2:11 AM