locked
client not recognized (does not find server) RRS feed

  • Question

  • I installed WHS 2011 back on the 31st of last month on a raid 5 array of 2.72 TB (single drive).  I found that 745 gig was not recognized because of a 2TB limit for boot drive.

    So......

    I have reconfigured the array as a raid 10 which is just under 2 TB and reinstalled WHS 2011 (everything is fine, all space is allocated).  Install went find, all functioning as it should.

    I can log in to WHS 2011 using RDP

    I can access the shared server folders using windows explorer from a client machine

    But....

    The accounts that were set up before cannot log in.  The error says "The server appears to be offline. Do you want to sign in to off line mode"  This is the error I got when the server was powered off (not online as the error says)  Now I get this error from client log in and I know the server is online because I can use RDP and windows explorer to get to the server desktop and folders (from the client machine that is failing the client log in).

     

    In the dashboard (from RDP) I have:

    1) joined the "workgroup" in server settings

    2) created all of the user accounts that were previously installed using the same ID/pswrd as before (all worked before)

    3) set the permissions on folders (read/write)

    So what have I forgotten?  I don't recall the set up being very complex last time and everything went smooth as glass but this time there are issues.

     

    Friday, June 10, 2011 5:41 PM

Answers

  • OK... the magic bullet is.....

     

    If WHS 2011 needs to be reinstalled and client software has already been installed you must UN-install all client software (control panel > uninstall programs)

    Then...  reinstall each client individual (http://backup-server-name/connect)

     

    All is happy once again in WHS 2011 back up land

    :)

    • Marked as answer by turtle_dude Friday, June 10, 2011 6:01 PM
    Friday, June 10, 2011 6:01 PM

All replies

  • OK... the magic bullet is.....

     

    If WHS 2011 needs to be reinstalled and client software has already been installed you must UN-install all client software (control panel > uninstall programs)

    Then...  reinstall each client individual (http://backup-server-name/connect)

     

    All is happy once again in WHS 2011 back up land

    :)

    • Marked as answer by turtle_dude Friday, June 10, 2011 6:01 PM
    Friday, June 10, 2011 6:01 PM
  • For my friend Fred:

    I got Launchpad to work.  After starting my laptop I went to Events and checked all Errors within the last hour.  I started with the first one and reviewed them with Microsoft using the Event Log Online Help.  It showed the following information.

    ----------------------------------------------------------------------------------

     

    Event ID 7009 — Basic Service Operations

     Updated: January 6, 2009 at http://technet.microsoft.com/en-us/library/dd349435(WS.10).aspx

     

    Applies To: Windows Server 2008 R2 

     Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.

     

    Event Details

     Product: Windows Operating System

     ID: 7009

     Source: Service Control Manager

     Version: 6.1

     Symbolic Name: EVENT_CONNECTION_TIMEOUT

     Message: Timeout (%1 milliseconds) waiting for the %2 service to connect.

     Resolve

     

    Increase the service timeout period

     

    The Service Control Manager will generate an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). To resolve this problem, use the Registry Editor to change the default timeout value for all services.

     

    To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. 

     Caution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data. 

     To change the service timeout period: 

    1.Click the Start button, then click Run, type regedit, and click OK. 

    2.In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. 

    3.In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.

     Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.

     

    4.Click Decimal, enter the new timeout value in milliseconds, and then click OK. 

    5.Restart the computer. 

      

    ----------------------------------------------------------------------------------

     So I had to create the ServicesPipeTimeout and I gave it a 100000 millisecond setting.  Shut down my laptop.  I restarted my laptop and immediately went back to my Event Viewer and selected to review all the errors for the last hour.  So there were about 12 errors cleared up with this one entry so I selected Launchpad to run.  It popped up connected in just a couple seconds.

    Sunday, June 12, 2011 10:27 PM
  • I installed WHS 2011 back on the 31st of last month on a raid 5 array of 2.72 TB (single drive).  I found that 745 gig was not recognized because of a 2TB limit for boot drive.

    So......

    I have reconfigured the array as a raid 10 which is just under 2 TB and reinstalled WHS 2011 (everything is fine, all space is allocated).  Install went find, all functioning as it should.

    I can log in to WHS 2011 using RDP

    I can access the shared server folders using windows explorer from a client machine

    But....

    The accounts that were set up before cannot log in.  The error says "The server appears to be offline. Do you want to sign in to off line mode"  This is the error I got when the server was powered off (not online as the error says)  Now I get this error from client log in and I know the server is online because I can use RDP and windows explorer to get to the server desktop and folders (from the client machine that is failing the client log in).

     

    In the dashboard (from RDP) I have:

    1) joined the "workgroup" in server settings

    2) created all of the user accounts that were previously installed using the same ID/pswrd as before (all worked before)

    3) set the permissions on folders (read/write)

    So what have I forgotten?  I don't recall the set up being very complex last time and everything went smooth as glass but this time there are issues.

     


    This happened to me and in my case it was caused by a reinstallation of the server. If you reinstall the server for any reason, you have to remove/reinstall the connector.
    Stuart
    Tuesday, June 14, 2011 6:17 PM