locked
Not able to connect to WHS server with the WHS Enterprise Console any longer RRS feed

  • Question

  • I'm running the HP SmartMedia EX470 server, and I have suddenly got a problem trying to reach my WHS with the Enterprise Console (EC).
    Using Remote Desktop is working fine, and I'm still able to start WHS EC via the RDP connection.
    All updates/patches are automatically deployed (both WHS and HP SmartMedia).



    The clients involved are Windows Vista 64bit and several Windows XP 32bit. All are updated with the latest available patches at all times.
    They all lost contact at approximately the same time so I suspect a server side problem.

    Trying to reinstall the connector software fails (tried on several clients) from the share on the WHS server holdign the install-files.
    Error message is related to installing the file esClient.exe which cannot be found in cabinet Sample.cab "due to multiple different reasons".

    The Windows Home Server Tray Icon on the different connected clients is always indicating the correct status (can see it shifts), so communication back and forth are working (...to some extent), so I guess I can rule out DNS problems.
    I have tried to disable all firewalls on both the server and the clients, so I guess I can rule out FW problems as well even though this was my most likely theory initially.


    I can't state for sure that this is related to patch updates, but I highly suspect it. I can't give the exact timing of when the problems started other than the last week (15-2009), so I cannot be too sure...
    Looking into the Event logs on the WHS does not give any clues (at least not to me...)
    I might have made a mistake running Windows Update directly on the server via RDP (and not through WHS EC). A lot more patches were installed that way...


    All clients are able to access the defined shares on the WHS, and the backup program is working fine.

    To me it could look like that some services have been stopped or reconfigured, but I'm a bit "lost in space" at the moment.


    Nmap (v4.68) done on the internal private network towards the WHS shows the following:
    nmap in it simplest form without options (just nmap ip-address)

    PORT    STATE    Service
    20/tcp        closed    ftp-data
    21/tcp        closed    ftp
    22/tcp        open    ssh
    80/tcp        open    http
    135/tcp        open    msrpc
    139/tcp        open    netbios-ssn
    443/tcp        open    https
    445/tcp        open    microsoft-ds
    1025/tcp    open    NFS-or-IIS
    3389/tcp    open    ms-term-serv
    3689/tcp    open    rendezvous
    4125/tcp    open    rww
    9999/tcp    open    abyss




    Seen from the outside (a random node on the internet hitting the front side of the router/ADSL-modem):
    PORT     STATE  SERVICE
    20/tcp   closed ftp-data
    21/tcp   closed ftp
    22/tcp   open   ssh
    80/tcp   open   http
    443/tcp  open   https
    1720/tcp open   H.323/Q.931
    4125/tcp closed rww
    6000/tcp closed X11
    6001/tcp closed X11:1
    6002/tcp closed X11:2
    6003/tcp closed X11:3
    6004/tcp closed X11:4
    6005/tcp closed X11:5
    6006/tcp closed X11:6
    6007/tcp closed X11:7
    6008/tcp closed X11:8
    6009/tcp closed X11:9
    6017/tcp closed xmail-ctrl
    6050/tcp closed arcserve

    The router has a FW, and NAT is properly configured to route traffic to the actual inside machines
    Remember: This was working, and no changes has lately been done on my router (to my knowledge).
    I'm still able to connect to my WHS through ssh (or http(s)) from the same external node.


    netstat -an run on the WHS reveals the following:

    Active Connections

      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:22             0.0.0.0:0              LISTENING
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:1138           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:8912           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:9999           0.0.0.0:0              LISTENING
      TCP    0.0.0.0:10243          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:55000          0.0.0.0:0              LISTENING
      TCP    0.0.0.0:56000          0.0.0.0:0              LISTENING
      TCP    127.0.0.1:445          127.0.0.1:1032         ESTABLISHED
      TCP    127.0.0.1:1027         127.0.0.1:5354         ESTABLISHED
      TCP    127.0.0.1:1028         127.0.0.1:5354         ESTABLISHED
      TCP    127.0.0.1:1029         127.0.0.1:5354         ESTABLISHED
      TCP    127.0.0.1:1031         127.0.0.1:32000        ESTABLISHED
      TCP    127.0.0.1:1032         127.0.0.1:445          ESTABLISHED
      TCP    127.0.0.1:1039         0.0.0.0:0              LISTENING
      TCP    127.0.0.1:1056         127.0.0.1:8009         ESTABLISHED
      TCP    127.0.0.1:1058         127.0.0.1:8009         ESTABLISHED
      TCP    127.0.0.1:1061         127.0.0.1:5432         ESTABLISHED
      TCP    127.0.0.1:1063         127.0.0.1:5432         ESTABLISHED
      TCP    127.0.0.1:1090         127.0.0.1:8912         ESTABLISHED
      TCP    127.0.0.1:1133         127.0.0.1:8009         ESTABLISHED
      TCP    127.0.0.1:1134         127.0.0.1:8009         ESTABLISHED
      TCP    127.0.0.1:1136         127.0.0.1:8009         ESTABLISHED
      TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING
      TCP    127.0.0.1:5354         127.0.0.1:1027         ESTABLISHED
      TCP    127.0.0.1:5354         127.0.0.1:1028         ESTABLISHED
      TCP    127.0.0.1:5354         127.0.0.1:1029         ESTABLISHED
      TCP    127.0.0.1:5432         0.0.0.0:0              LISTENING
      TCP    127.0.0.1:5432         127.0.0.1:1061         ESTABLISHED
      TCP    127.0.0.1:5432         127.0.0.1:1063         ESTABLISHED
      TCP    127.0.0.1:8009         127.0.0.1:1056         ESTABLISHED
      TCP    127.0.0.1:8009         127.0.0.1:1058         ESTABLISHED
      TCP    127.0.0.1:8009         127.0.0.1:1133         ESTABLISHED
     TCP    127.0.0.1:8009         127.0.0.1:1134         ESTABLISHED
     TCP    127.0.0.1:8009         127.0.0.1:1136         ESTABLISHED
     TCP    127.0.0.1:8079         0.0.0.0:0              LISTENING
     TCP    127.0.0.1:8081         0.0.0.0:0              LISTENING
     TCP    127.0.0.1:8912         127.0.0.1:1090         ESTABLISHED
     TCP    127.0.0.1:32000        0.0.0.0:0              LISTENING
     TCP    127.0.0.1:32000        127.0.0.1:1031         ESTABLISHED
     TCP    192.168.1.105:139      0.0.0.0:0              LISTENING
     TCP    192.168.1.105:445      192.168.1.7:2003       ESTABLISHED
     TCP    192.168.1.105:1138     192.168.1.7:2001       ESTABLISHED
     TCP    192.168.1.105:3389     192.168.1.7:2186       ESTABLISHED
     UDP    0.0.0.0:445            *:*
     UDP    0.0.0.0:500            *:*
     UDP    0.0.0.0:1026           *:*
     UDP    0.0.0.0:4500           *:*
     UDP    0.0.0.0:8912           *:*
     UDP    127.0.0.1:123          *:*
     UDP    127.0.0.1:1030         *:*
     UDP    127.0.0.1:1072         *:*
     UDP    127.0.0.1:1900         *:*
     UDP    192.168.1.105:68       *:*
     UDP    192.168.1.105:123      *:*
     UDP    192.168.1.105:137      *:*
     UDP    192.168.1.105:138      *:*
     UDP    192.168.1.105:1900     *:*
     UDP    192.168.1.105:5353     *:*




    Any good ideas are most welcome
    Friday, April 17, 2009 5:06 PM

Answers

  • The tip is the very last line: Version Information:  Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

    You have somehow managed to turn on .NET version 1.1 while the WHS pages require .NET 2.0. Perhaps you have installed some application the uses .NET 1.1 with a bad installer that has changed the setting on the whole server?

    Change ASP.Net version to 2.0 via the IIS management console and I think you'll get rid of the error.
    HP MediaSmart EX475, 2GB ram, 2x512 + 1x120 GB storage. Author of WHS File Manager Add-In, WHS Jungle Disk Add-in and WHS Media Connect Configuration Add-in. http://blog.paks.no/whs-add-ins/
    Saturday, April 18, 2009 1:02 PM

All replies

  • Hi,
    an "Enterprise" console on a "Home" Server? That's funny.
    Can you execute the Home Server console from within the Remote Desktop session?
    Which version numbers does the console show?
    To get the connector software reinstalled, try to update, rename or remove the OEM folder in the software share in the folder Home Server Connector Software, since the error message seems to come from an OEM component.
    (Did you ever run the HP updates for your home server?)
    Best greetings from Germany
    Olaf
    Friday, April 17, 2009 6:46 PM
    Moderator
  • I guess I might have been to fast in the "Enterprise" description.  I mean "Home" of course :-)

    Yes, I can execute the Home Server console from within the RDP session when logged into the WHS.
    It is when I try to run the Console from any of the clients directly, it fails.

    Yes, I have run the HP updates manually several times to make sure that I'm on the latest patch level, but only once succeeded in finding an update. Automatic updates has been enabled, so that has taken care of the upgrade process I believe.


    Not sure if I understand your version question correctly, but here is a try:

    Windows Home Server, SP2
    The latest PowerPack from HP is applied (last update 23/1-2009).
    Other programs you were wondering about?
    Using the normal procedure (finding About or Help) does not give me much version information, but most of it is stamped 2009 at least.


    I did have some hazzle when configuring this server for the very first time (having a 64bit Vista OS as my inital primary source) 6 months ago, but using a 32bit VMWare package got me going, and have had no problems since then.  One of the first things I did was upgrading the memory/RAM to 2 GB.

    A question to your "reinstall" procedure. Is this the way to go?
    1) Rename folder on WHS server
    2) Insert original WHS CD on a 32bit client, and then what?
    3) Install the WHS connector on a 32bit OS platform
    3) Do the upgrade procedure to get 64bit support?
    4) Install the 64bit WHS connector?


    Friday, April 17, 2009 7:39 PM
  • Version numbers in the console you find under Settings/Ressources.
    Reinstall means in this case:
    Uninstall the Connector software from the Client PC, not the server. (After that you can delete eventual remains in C:\Program Files\Windows Home Server.
    Open http://server:55000 and install the Connector software from here, or open the software share in Shared Folders on Server shortcut, open to the folder Home Server Connector Software. Try to run setup. If this fails again, move the OEM folder out of that folder (cut and paste somewhere else) and try to perform the installation without the HP specials.

    (The server recovery from the original medium is something, which you should only perform in worst case scenarios.)

    Best greetings from Germany
    Olaf
    Friday, April 17, 2009 8:00 PM
    Moderator
  • Ok, I'll give it a try. Thanks for your feedback so far.

    Version info:
    Windows Home Server Console: 6.0.2030.0
    Windows Home Server Backup & Restore: 6.0.2030.0
    Windows Home Server Drive Extender: 6.0.2030.0
    Windows Home Server Remote Access: 6.0.2030.0
    Windows Home Server Storage Manager: 6.0.2030.0
    Friday, April 17, 2009 8:19 PM
  • Hi,
    this is the most current version and includes Windows Home Server Power Pack 2 already.
    If you run into an error again during the connector software installation, try to reboot the server first and install again.
    If that not works, please provide exact error messages.
    (Eventually uninstalling Power Pack 2 on the server and reinstalling it later would fix the problem, if it is really server based, but try this only as one of the last resorts.)

    Best greetings from Germany
    Olaf
    Friday, April 17, 2009 8:52 PM
    Moderator
  • First results:
    XP 32bit client
    Uninstalled previous SW, and removed the remains from the Windows Home Server folder

    Loaded the browser and the http://server:55000   URL
    Pressed the button: Download now  (Connector software)


    Saw the program trying to locate the Home server and an indicator showing 0% for a very short time, before this message suddenly came up:




    Downloaded the diagnostic toolkit from MS:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=71ef4793-5f81-4ef7-8c7d-fe905094ab13&displaylang=en

    The result was presented in a completely unreadable form, giving no indications of where the real problem were.
    Downloaded a trouble shooting guide: http://www.microsoft.com/downloads/details.aspx?FamilyID=42426d83-2c54-446e-86ed-e3e9e7e33a98&displaylang=en

    1)  From a home computer, connect to http:// <YourServerName> using a Web browser, where <YourServerName> is the name of your home server.
    ==> Passed

    2) From a home computer, connect to http://<YourServerName>:55000/enrollid/id.xml

    You should see the following text in the browser window:

    <ID>1</ID>

    ==> Passed

    3)  connect to https://<YourServerName>:56000/enroll/id.xml

    You should see the following text in the browser window:

    <ID>2</ID>


    ==> Passed

    4)  connect to  http://<YourServerName>:55000/enrollid/id.aspx

    ==> I belive I pass even though I see an errormessage. I had RemoteAccess via WEB trouble a little earlier than the connector-trouble started (I believe, not 100% sure). Bad IIS configuration when I manually added my own webserver to the current IIS config. WebShare and my own "home-pages" are working fine, but not RemoteAccess.

    The errormessage I get is:

    Server Error in '/EnrollId' Application.

    Runtime Error

    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

    <!-- Web.Config Configuration File -->

    <configuration>
    <system.web>
    <customErrors mode="Off"/>
    </system.web>
    </configuration>

    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

    <!-- Web.Config Configuration File -->

    <configuration>
    <system.web>
    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
    </configuration>

    Recommended action from the manual: Reinstall the Windows Home Server.


    Another recommendation from this manual is to be careful with the HOSTS-file. I have indeed modified that, but I know what I'm doing. But just for this test, I moved the modified file away as well.

    There is a long list of specific FW-openings too. It will take me some time to go through that.


    Removing the OEM-folder from the installation directory on the Home Server did not help. Exactly the same result.
    • Edited by SverreO Friday, April 17, 2009 9:37 PM
    Friday, April 17, 2009 9:30 PM
  • hmm ,the screen shots was peeled off when I pressed the submit button ...

    The main message when trying to install the connector software: "Please wait while your Home Server is located" is flashing for some seconds.
    Then: The operation cannot be completed at this time. If the problem persists, please contact Product Support.

    And I did this attempt with the client FW disabled.
    Friday, April 17, 2009 9:37 PM
  • I had very similar symptoms one time, and it was in fact the firewall on the SERVER side. The firewall requires exceptions for port TCP port 55000 and 56000 for the local subnet.

    Good Luck
    Friday, April 17, 2009 9:50 PM
  • Hi,

    The actual ports are open on the server.
    If I specifically try to define these ports, I got the message that they are already assigned to http/https
    http has 80 and 55000
    https has 443 and 56000

    The test results above (step 2,3,4) are also indicating that this is not the problem. I'm able to connect on these two ports via the browser.

    Anyway, thanks for your attempt to help.
    Friday, April 17, 2009 10:02 PM
  • I'm honestly starting to believe that it is my IIS-webserver that is the problem.
    I have tried to remove all my own stuff, but I don't seem to get it right. The error messages will not go away.

    Does anyone have a tip for restoring the IIS-server to its "original" state without reinstalling the whole server?
    Saturday, April 18, 2009 8:03 AM
  • IIS is by default configured not to show details error messages to remote hosts. That's why you get the strange error when you try http://<YourServerName>:55000/enrollid/id.aspx from a client PC. The easiest way to see the actual error message is to remote desktop into your home server. Then open Internet Explorer and use localhost instead like this: http://localhost:55000/enrollid/id.aspx

    You will then see the actual error message. But weather this has anything to do with the connection problems with the console I don't know.
    HP MediaSmart EX475, 2GB ram, 2x512 + 1x120 GB storage. Author of WHS File Manager Add-In, WHS Jungle Disk Add-in and WHS Media Connect Configuration Add-in. http://blog.paks.no/whs-add-ins/
    Saturday, April 18, 2009 10:53 AM
  • I should have known that :-(
    But honestly, checking locally didn't give very much more detail:  (http://localhost:55000/enrollid/id.aspx )

    Server Error in '/EnrollId' Application.

    Configuration Error

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: Unrecognized configuration section 'connectionStrings'

    Source Error:

    Line 2:  <configuration>
    Line 3: <appSettings/>
    Line 4: <connectionStrings/>
    Line 5: <system.web>
    Line 6: <compilation debug="true"/>

    Source File: C:\inetpub\intranet\web.config    Line: 4




    Testing
    https://localhost:56000/enrollid/id.aspx didn't provide much more ....

    Server Error in '/EnrollId' Application.

    Configuration Error

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: Unrecognized configuration section 'connectionStrings'

    Source Error:

    Line 2:  <configuration>
    Line 3: <appSettings/>
    Line 4: <connectionStrings/>
    Line 5: <system.web>
    Line 6: <compilation debug="true"/>

    Source File: C:\inetpub\intranet\web.config    Line: 4


    Version Information:  Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407



    Saturday, April 18, 2009 12:50 PM
  • Does anyone have a tip for restoring the IIS-server to its "original" state without reinstalling the whole server?
    Unfortunately, the original state isn't documented; modifications to that original state aren't supported, so I assume that Microsoft felt anyone making such modifications would make careful notes along the way. You don't say what modifications you've made, BTW. That might be useful information...

    In any case, you have more than one problem at this point; a server reinstallation is probably going to be the fastest way to get your server back to a supported and fully functional state. There is no simple set of steps that you can follow to remove and reinstall IIS and the Windows Home Server web applications; they are installed when WHS itself is installed, and then updated (not reinstalled) with each power pack or update.

    I'm not on the WHS team, I just post a lot. :)
    Saturday, April 18, 2009 12:54 PM
    Moderator
  • The tip is the very last line: Version Information:  Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

    You have somehow managed to turn on .NET version 1.1 while the WHS pages require .NET 2.0. Perhaps you have installed some application the uses .NET 1.1 with a bad installer that has changed the setting on the whole server?

    Change ASP.Net version to 2.0 via the IIS management console and I think you'll get rid of the error.
    HP MediaSmart EX475, 2GB ram, 2x512 + 1x120 GB storage. Author of WHS File Manager Add-In, WHS Jungle Disk Add-in and WHS Media Connect Configuration Add-in. http://blog.paks.no/whs-add-ins/
    Saturday, April 18, 2009 1:02 PM
  • I haven't really installed much software (as add-ins, or stand-alone) directly on the WHS server, but ____ happens :-(

    Could you please elaborate a little bit more about the .NET change?
    Where exactly do I make this change? I could only find a reference to .NET 1 and 2 on the "Web Service Extensions" panel, but nothing about a "replace" option.

    I don't know very much about IIS as such, besides adding "sites"

    Thanks for your help.
    Saturday, April 18, 2009 1:23 PM
  • Hey, I found it :-)


    That did the trick. The connector is now working again.

    Thank you very much for your tip.
    Saturday, April 18, 2009 1:27 PM
  • I'll note that having both ASP.Net 1.1 and 2.0 registered on the same web site, in the same application pool, has been known to cause problems, such as IIS "hanging" or restarting unexpectedly. If the OP has issues of that sort, the options are fairly limited:
    • You set up different application pools, putting the ASP.NET 1.1 applications in one and the 2.0 applications in another. This is definitely not supported, and while I don't think it should have any negative impact on Windows Home Server, it's a possibility.
    • You set up a separate web server if your router supports functioning as a reverse proxy.
    • You abandon one or the other of the web applications, in this case the ASP.NET 1.1 app.

    I'm not on the WHS team, I just post a lot. :)
    Saturday, April 18, 2009 2:09 PM
    Moderator
  • I'll note that having both ASP.Net 1.1 and 2.0 registered on the same web site, in the same application pool, has been known to cause problems, such as IIS "hanging" or restarting unexpectedly. If the OP has issues of that sort, the options are fairly limited:
    • You set up different application pools, putting the ASP.NET 1.1 applications in one and the 2.0 applications in another. This is definitely not supported, and while I don't think it should have any negative impact on Windows Home Server, it's a possibility.
    • You set up a separate web server if your router supports functioning as a reverse proxy.
    • You abandon one or the other of the web applications, in this case the ASP.NET 1.1 app.

    I'm not on the WHS team, I just post a lot. :)
    Hi,

    I don't actually need ASP 1, but thanks for the tip. You never know when you suddenly need it.

    Sverre
    Saturday, April 18, 2009 10:19 PM
  • I don't actually need ASP 1, but thanks for the tip. You never know when you suddenly need it.
    You installed something that needed it at some point. :)

    I'm not on the WHS team, I just post a lot. :)
    Sunday, April 19, 2009 1:29 PM
    Moderator