none
Cannot connect through Connector or Remote Desktop RRS feed

  • Question

  • I have been running Windows Home server for about three months with no trouble.  I am running the 120- day Evaluation software to test it before I go all the way with it.  I have had very little trouble with it until this week.  All of a sudden I could not connect with the home server through the connector or through remote desktop.  The server is still backing up and I can access the shared folders.  I can log in to my web url for the shared folders and computers.  But if I try and connect with the home server with either the connector, remote desktop or through the web I get the following error.

    This computer cannot connect to your home server.  Check your network connection and make sure your home server is powered on.  If your home server has recently restarted, try again in a few minutes.

    What I have done so far is check to make sure RDC is on by going to remote and making sure there is a checkmark in the box.  I have run "discovery.exe" and it goes through and asks me for my password and says that there is an update and then sets up backup.  I have searched through quite a few of the forums and tried multitude of things.  It did work correctly for about three months and then all of a sudden this week (and I am not sure of any changes).

    Thanks in advance for help.

    Jerry Fowler
    fowlerjerryd@sbcglobal.net

    FowlerJ
    Sunday, October 26, 2008 2:00 AM

All replies

  • Cobol Kid said:

    I have been running Windows Home server for about three months with no trouble.  I am running the 120- day Evaluation software to test it before I go all the way with it.  I have had very little trouble with it until this week.  All of a sudden I could not connect with the home server through the connector or through remote desktop.  The server is still backing up and I can access the shared folders.  I can log in to my web url for the shared folders and computers.  But if I try and connect with the home server with either the connector, remote desktop or through the web I get the following error.

    This computer cannot connect to your home server.  Check your network connection and make sure your home server is powered on.  If your home server has recently restarted, try again in a few minutes.

    What I have done so far is check to make sure RDC is on by going to remote and making sure there is a checkmark in the box.  I have run "discovery.exe" and it goes through and asks me for my password and says that there is an update and then sets up backup.  I have searched through quite a few of the forums and tried multitude of things.  It did work correctly for about three months and then all of a sudden this week (and I am not sure of any changes).

    Thanks in advance for help.

    Jerry Fowler
    fowlerjerryd@sbcglobal.net


    FowlerJ




    Are you able to ping the server, both by name and by IP address?  Can you run ipconfig /all on both the client and the server and post the results here?
    Sunday, October 26, 2008 4:17 AM
    Moderator
  • On top of what kariya asked:
    Did you change anything in your network topology? (i.e. added WLAN ...)
    Do you get access, if you use the IP address of your WHS instead of the name?
    Check the Remotedesktop exception in the Windows Firewall on your WHS. Try to uncheck it, apply and set it again.
    If you have different subnets, you may also wish to try to change the scope of the Remotedesktop exception to All networks.
    Best greetings from Germany
    Olaf
    Sunday, October 26, 2008 1:05 PM
    Moderator
  • says that there is an update and then sets up backup.



    Did WHS download a new Connector update? If so, run the updated connector software. Hope it helps!
    Sunday, October 26, 2008 2:02 PM
  • I was able to ping the server and this is what I got

    ping 192.168.0.197

    Pinging 192.168.0.197 with 32 bytes of data:
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.0.197:
           Packet: Sent = 4, Received = 4, Lost = 0 <0% loss>
    Approximate round trip times in milli-seconds:
           Minimum = 0ms, Maximum = 0ms, Average = 0ms

    ping fowlserv

    Pinging fowlserv [192.168.0.197] with 32 bytes of data:
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128
    Reply from 192.168.0.197: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.0.197:
           Packet: Sent = 4, Received = 4, Lost = 0 <0% loss>
    Approximate round trip times in milli-seconds:
           Minimum = 0ms, Maximum = 0ms, Average = 0ms

    I ran ipconfig /all but I am unable to copy and paste the results, how can I do that from a command prompt window?

    I also tried uninstalling the windows connector software and re-installing it from the server, it went through all the way and when I went to connect it gave me the same error.

    Thanks for the help so far

    Jerry

    FowlerJ
    Sunday, October 26, 2008 10:18 PM
  • Hi Jerry,
    in a command prompt window you can click the system menu of the window (upper left corner in the title bar), select Edit and click Mark. Use the mouse to mark the output and hit Enter.
    Now you should have the marked block in the clipboard, from which you can past the content by the usual methods.
    Best greetings from Germany
    Olaf

    Sunday, October 26, 2008 10:23 PM
    Moderator
  • I have not changed anything in my network

    I have not gotten access be either the name or the IP address

    I check the remotedesktop exception, and I did the uncheck and re check.  When this first happened I did and I was able to get into the  Home Server Console on the server

    Thanks

    Jer

    FowlerJ
    Sunday, October 26, 2008 10:25 PM
  • Here is the results from the ipconfig /all on my client, its rather long and I do not remember seeing all those tunnel adapters before.

    C:\Users\jf0394092>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : jf0394092-LT
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Wireless LAN adapter Wireless Network Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
       Physical Address. . . . . . . . . : 00-13-E8-20-83-1D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::12b:fdb3:7799:eaa2%9(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.195(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, October 26, 2008 4:48:00 PM
       Lease Expires . . . . . . . . . . : Monday, October 27, 2008 5:01:56 PM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
    it Ethernet NIC (NDIS 6.0)
       Physical Address. . . . . . . . . : 00-1B-24-42-52-C9
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::f0d1:41a9:e178:ef67%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.191(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Sunday, October 26, 2008 4:48:00 PM
       Lease Expires . . . . . . . . . . : Monday, October 27, 2008 5:01:56 PM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 11:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{B22BAEC4-E9DE-495D-AD07-4BCB5C317
    106}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:146d:1f1d:3f57:ff40(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::146d:1f1d:3f57:ff40%11(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{DECC5085-360E-4EF3-BE6A-90999F2F2
    28E}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 10:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : 6TO4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 17:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{DECC5085-360E-4EF3-BE6A-90999F2F2
    28E}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 18:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{B22BAEC4-E9DE-495D-AD07-4BCB5C317
    106}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 19:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{B22BAEC4-E9DE-495D-AD07-4BCB5C317
    106}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 24:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{DECC5085-360E-4EF3-BE6A-90999F2F2
    28E}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 25:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{DECC5085-360E-4EF3-BE6A-90999F2F2
    28E}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 27:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{B22BAEC4-E9DE-495D-AD07-4BCB5C317
    106}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 28:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #9
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 29:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #10
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    FowlerJ
    Sunday, October 26, 2008 10:28 PM
  • Hello,
    this is the output from the client PC.
    If possible, do the same for your Windows Home Server.
    There is one issue, which may be a reason for your issues:
    You have two active network cards in your PC - the wired and the wireless. At any time there should only one network card be used, since multihomed scenarios are often causing trouble.
    So disable one of the connections and try again after a reboot.

    About the tunneling - this may have to do with IPv6.
    http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

    Best greetings from Germany
    Olaf
    Sunday, October 26, 2008 10:56 PM
    Moderator
  • Here is the ipconfig /all from the home server

    C:\Documents and Settings\Administrator>ipconfig /all

     

    Windows IP Configuration

     

       Host Name . . . . . . . . . . . . : fowlserv

       Primary Dns Suffix  . . . . . . . :

       Node Type . . . . . . . . . . . . : Unknown

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

     

    Ethernet adapter Local Area Connection:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller

       Physical Address. . . . . . . . . : 00-13-72-DA-CF-56

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       IP Address. . . . . . . . . . . . : 192.168.0.197

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 192.168.0.1

       DHCP Server . . . . . . . . . . . : 192.168.0.1

       DNS Servers . . . . . . . . . . . : 192.168.0.1

       Lease Obtained. . . . . . . . . . : Sunday, October 26, 2008 3:03:17 PM

       Lease Expires . . . . . . . . . . : Monday, October 27, 2008 3:03:17 PM

     

    C:\Documents and Settings\Administrator>

     

    And then I tried the other suggestion and disabled the wireless adapter, with no success.

    Thanks you for all your help, you have made quite a few suggestions.  I do appreciate them all.

    Thanks,

    Jerry Fowler

    FowlerJ
    Monday, October 27, 2008 3:25 AM
  • Please also enable NetBIOS over TCP/IP (Control Panel/Network/ Right click LAN Connection / Double click TCP/IP and select Advanced button) on the WINS tab of the WHS.
    Best greetings from Germany
    Olaf
    Monday, October 27, 2008 9:11 AM
    Moderator
  • I tried this and the option to enable NetBIOS over TCP/IP was not checked so I did and applied and even shut down and re-booted.  But I am still getting the error.

    Thanks Olaf

    Jer 
    FowlerJ
    Tuesday, October 28, 2008 3:06 AM
  • Hi Jerry,
    Since you can ping the system by name and by IP address and the IP settings look fine, name resolution seems to work.
    On your Vista-PC try the following.
    • Open Network and Sharing Center.
    • Click Manage Network Connections.
    • In menu Advanced/Advanced Settings arrange the network adapter you are using for the connection to be in the top position.
    Please also verify the scope of the RemoteDesktop exception on your WHS. Try to set it to All Networks. What happens, if you temporary disable the Windows Firewall on the server?
    Do you have any 3rd party security software on your client PC installed? If yes, try to disable or uninstall.

    Please check also the event log of the server, if you see there events corresponding to the failed connection attempts.
    To do so, log on locally to your server, click Start/Run and enter eventvwr.

    Best greetings from Germany
    Olaf
    Tuesday, October 28, 2008 9:34 AM
    Moderator
  • Olaf, you have been more than helpful with all of your suggestions, all but a couple of them I had never even thought of.  But no avail, I am still unable to get into the windows server console.  I am at my wits end and you have been the only one to come up with any suggestions.  I want to thank you, but I am beginning to think enough is enough.  I would be happy to keep trying things, but I hate to take up all your time.  Maybe its time for either just to start over with a re-install (if that is possible) or just delete and give up.

    If you do think of other things I will give them a try, what do you think?

    Thanks again you have been more than kind.

    Jerry

    FowlerJ
    • Edited by Cobol Kid Thursday, October 30, 2008 2:03 AM
    Thursday, October 30, 2008 2:03 AM
  • Hi Jerry,
    sometimes networking is simple, sometimes not. Troubleshooting over distance, without own access to a system, is even more complicated.
    But you don't need to care about my time, if I can help, it's fine.
    I also understand, that all this troubleshooting of things, which should simply run, can become a pain. But other solutions - other troubles ...
    Sometimes a server reinstall helps, and as long as you don't activate, the trial version can run 30 days again.

    Can you open the WHS console from start menu, if you are locally logged in to the server?

    Best greetings from Germany
    Olaf
    Thursday, October 30, 2008 9:08 AM
    Moderator
  • Hi Olaf, thanks for the pep talk and I am willing to continue if you are.

    Yes I am able to get into the WHS console when I am on the server, Luckily I do have a monitor and a keyboard hooked up to it.

    The wierd part is I have been able to log into the server using the connector software, or by using remote desktop, and by getting on the internet and going to myservername.homeserver.com  But all of a sudden (and for some reason I think there was a update in there) I cannot hook up using any of the ways I did before.

    What would a re-install do to my system?  Is that a possibility? or is it a lot more destructive than what I would want.  The other lucky thing is that I have kept my previous backup systems running along side with WHS.  So far I would not be out of anything important.

    Thanks and I look forward to trying other things.

    Jerry

    FowlerJ
    Thursday, October 30, 2008 6:43 PM
  • Hi Jerry,
    what would a reinstall do. It would wipe the C: drive, reinstall a clean system, taking away the user accounts, installed Add-Ins and other modifications. I assume, the server will also receive a different IP address (maybe you configure a fixed instead). The data will be preserved.
    So if the reason is server side, a reinstallation may fix your trouble, if it is a client side issue, this will be wasted time.
    But since you can use the WHS console locally, I am nearly sure, that there is an issue with security settings either on a client or on the server (Windows Firewall).
    Can you try to use RDP to connect to your server from within the server local console session?
    The problem may be mainly RDP, since the WHS console sits on top of a RDP session.

    Again the question - did you check the event log of your WHS?
    To do that, open Control Panel/Administrative Tools/Event Viewer and search for errors (red) or warnings (yellow) around the time of failed connection. If Windows components are guilty, you may find infos in the system log or the application log, if the security is the reason, you may have to enable logging for this by creating an Audit policy on your server:
    An Audit Policy may be configured using the Group Policy editor to track logon success and failures. From the Start | Run command window type gpedit.msc. Navigate to Local Computer Policy | Computer Configuration | Windows Settings | Security Settings | Local Policies | Audit Policy | Audit logon events. Highlight and right-click and select Properties. Configure as desired. You would be mainly interested in Errors here, but Success with subsequent disconnect may also give us some informations.
    You could find related events in all 3 logs, but mainly in security.

    Best greetings from Germany
    Olaf
    Thursday, October 30, 2008 7:56 PM
    Moderator
  • Olaf,

    I did look at the event log and did not find an error that looked like it would be associated with Remote Desktop.

    I am a little confused, how do I go about connecting tom my sever from within the server local console session?  I log onto my server and then click on the icon for the console and it gives me a few things in a ribbon toolbar at the top and the I think I remember a settings and something else.  What would I do from there to access my server?

    Thanks (from the mid-west, along the old mississippi

    Jer :)

    FowlerJ
    Thursday, October 30, 2008 8:38 PM
  • Hi Jerry,
    to try a Remote Desktop session from within your WHS (connected with keyboard and monitor) click on Start/All Programs/Accessories/Communication and select Remote Desktop.
    Enter the name if your server as target. Something should happen - in my system I get a second session to the server desktop within a Remotedesktop window.
    Best greetings from Germany
    Olaf

    Thursday, October 30, 2008 9:40 PM
    Moderator
  • Olaf,

    I did the remote session and I get the same error message on the server that I am getting on the clients when I try to hook up with the server.  I more step I tried hooking up with my vista laptop and when I went to browse for a connection it told me that there were no terminal services on this network

    Thanks,

    Jer

    FowlerJ
    Friday, October 31, 2008 3:10 AM
  • Hi Jerry,
    well, the server should know himself at least, so I think we can exclude name resolution for now.
    On the server, click Start/Run and type services.msc
    Sort the services by Startup type. Are  there services not started, which are set to Autostart?
    Is the service Terminal Services (free translated from German Windows) started?
    Did you try the Auditing stuff?
    Best greetings from Germany
    Olaf
    Friday, October 31, 2008 10:36 AM
    Moderator
  • I was out of town for work, just got home today and tried your suggestions.  I looked at the event logs and did not see anything out of the ordinary, did not see any errors on any type of remote connection.

    And the services window had quite a bit of things in it, I exported it and here it is.  Hope you can follow it

    Name Status   Startup Type Log On As
    Application Experience Lookup Service Started Automatic Local System
    Automatic Updates Started Automatic Local System
    COM+ Event System Started Automatic Local System
    Computer Browser Started Automatic Local System
    Cryptographic Services Started Automatic Local System
    DCOM Server Process Launcher Started Automatic Local System
    DHCP Client Started Automatic Network Service
    Distributed File System Started Automatic Local System
    Distributed Link Tracking Client Started Automatic Local System
    Distributed Transaction Coordinator Started Automatic Network Service
    DNS Client Started Automatic Network Service
    Error Reporting Service Started Automatic Local System
    Event Log Started Automatic Local System
    FTP Publishing Service Started Automatic Local System
    Help and Support Started Automatic Local System
    HID Input Service Started Automatic Local System
    IIS Admin Service Started Automatic Local System
    IPSEC Services Started Automatic Local System
    License Logging Started Automatic Network Service
    Logical Disk Manager Started Automatic Local System
    Machine Debug Manager Started Automatic Local System
    Performance Logs and Alerts
    Automatic Network Service
    Plug and Play Started Automatic Local System
    Print Spooler Started Automatic Local System
    Protected Storage Started Automatic Local System
    Remote Procedure Call (RPC) Started Automatic Network Service
    Remote Registry Started Automatic Local Service
    SBCore Service Started Automatic Local System
    Secondary Logon Started Automatic Local System
    Security Accounts Manager Started Automatic Local System
    Server Started Automatic Local System
    Shell Hardware Detection Started Automatic Local System
    System Event Notification Started Automatic Local System
    Task Scheduler Started Automatic Local System
    TCP/IP NetBIOS Helper Started Automatic Local Service
    Windows Audio Started Automatic Local System
    Windows Firewall/Internet Connection Sharing (ICS) Started Automatic Local System
    Windows Home Server Archiver Started Automatic Local System
    Windows Home Server Computer Backup Started Automatic Local System
    Windows Home Server Drive Letter Service Started Automatic Local System
    Windows Home Server Port Forwarding Started Automatic Local System
    Windows Home Server Storage Manager Started Automatic Local System
    Windows Home Server Transport Service Started Automatic Local System
    Windows Live Custom Domains Service Started Automatic Local System
    Windows Management Instrumentation Started Automatic Local System
    Windows Media Connect Service Started Automatic Network Service
    Windows Search Started Automatic Local System
    Windows Time



    Automatic Local Service
    Wireless Configuration Started Automatic Local System
    Workstation Started Automatic Local System
    World Wide Web Publishing Service Started Automatic Local System
    Terminal Services Session Directory
    Automatic Local System
    Alerter
    Disabled Local Service
    ClipBook
    Disabled Local System
    Distributed Link Tracking Server
    Disabled Local System
    IMAPI CD-Burning COM Service
    Disabled Local System
    Indexing Service
    Disabled Local System
    Intersite Messaging
    Disabled Local System
    Kerberos Key Distribution Center
    Disabled Local System
    Messenger
    Disabled Local System
    Net.Tcp Port Sharing Service
    Disabled Local Service
    NetMeeting Remote Desktop Sharing
    Disabled Local System
    Network DDE
    Disabled Local System
    Network DDE DSDM
    Disabled Local System
    Routing and Remote Access
    Disabled Local System
    Telnet
    Disabled Local Service
    Themes
    Disabled Local System
    WebClient
    Disabled Local Service
    Windows Image Acquisition (WIA)
    Disabled Local Service
    .NET Runtime Optimization Service v2.0.50727_X86
    Manual Local System
    Application Layer Gateway Service Started Manual Local Service
    Application Management
    Manual Local System
    ASP.NET State Service
    Manual Network Service
    Background Intelligent Transfer Service
    Manual Local System
    COM+ System Application
    Manual Local System
    Drive Extender Migrator Service Started Manual Local System
    File Replication
    Manual Local System
    HTTP SSL Started Manual Local System
    Logical Disk Manager Administrative Service Started Manual Local System
    Microsoft Office Diagnostics Service
    Manual Local System
    Microsoft Software Shadow Copy Provider
    Manual Local System
    Net Logon
    Manual Local System
    Network Connections Started Manual Local System
    Network Location Awareness (NLA) Started Manual Local System
    Network Provisioning Service
    Manual Local System
    NT LM Security Support Provider
    Manual Local System
    Office Source Engine
    Manual Local System
    Portable Media Serial Number Service
    Manual Local System
    Remote Access Auto Connection Manager
    Manual Local System
    Remote Access Connection Manager Started Manual Local System
    Remote Desktop Help Session Manager
    Manual Local System
    Remote Procedure Call (RPC) Locator
    Manual Network Service
    Removable Storage
    Manual Local System
    Resultant Set of Policy Provider
    Manual Local System
    Smart Card
    Manual Local Service
    Special Administration Console Helper
    Manual Local System
    SSDP Discovery Service Started Manual Local Service
    Telephony Started Manual Local System
    Terminal Services Started Manual Local System
    Uninterruptible Power Supply
    Manual Local Service
    Universal Plug and Play Device Host Started Manual Local Service
    Virtual Disk Service Started Manual Local System
    Volume Shadow Copy
    Manual Local System
    Windows CardSpace
    Manual Local System
    Windows Installer
    Manual Local System
    Windows Management Instrumentation Driver Extensions
    Manual Local System
    Windows Presentation Foundation Font Cache 3.0.0.0
    Manual Local Service
    Windows User Mode Driver Framework
    Manual Local Service
    WinHTTP Web Proxy Auto-Discovery Service Started Manual Local Service
    WMI Performance Adapter
    Manual Local System


    FowlerJ
    Monday, November 3, 2008 4:17 AM
  • Hi Jerry,
    Terminal Services Session Directory
    Automatic Local System
    is set to Startup type disabled in my systems.
    Besides that I can't see any strange settings.

    If you stop the Windows Firewall service in the services console, does the connection succeed then?
    Best greetings from Germany
    Olaf
    Monday, November 3, 2008 8:18 AM
    Moderator
  • Olaf,
    Happy November, can you believe where this year has gone?  Originally I had the same service (Terminal Services Session directory) disabled but thought that since it said something about terminal services I should turn it on.  No change either way.  I tried stopping Windows Firewall service and then tried connection, still same error message.

    Thanks for the suggestions, I can't believe that you keep coming up with different things to try!  Who long have you been using WHS? have you had good success with it?

    Thanks, again

    Jerry

    FowlerJ
    Monday, November 3, 2008 2:45 PM
  • Hi Jerry,
    did you enable the Auditing features as mentioned before?
    Without any results from this and with no errors in the event log I am now near the end - server reinstall?
    Maybe you can save the event logs of the server, zip them, put them somewhere to download and drop me a notice (mail address should be in profile).
    I work with Windows Home Server since it's beta.
    With Windows Server and clients much longer.
    Success? Mainly during beta testing (on my life system) I had sometimes unpleasant issues.
    But never lost important data and I could a few times successfully restore systems of my children or myself.
    Automated client backup removes a lot of pain and risk in a household with at least 6 to 7 connected PCs.
    So yes, WHS is a success in my eyes, even if it has still some children sicknesses and missing features.
    But that is what version number 1 stands for.
    Best greetings from Germany
    Olaf
    Monday, November 3, 2008 3:08 PM
    Moderator
  • Hi Olaf,

    I did try the Audit and tried both settings that were available with no change, should have I rebooted between the changes?  I will try and save the even logs when I get home later, if its not too big when zipped do you want me to email it to you?

    I have kids as well two girls 18 and 15, went through the teenage thing with the oldest and just starting with the 15 year old.  It amazes me how different children can be.  Can not imagine life without them.

    It is good to hear you talk well about WHS, this is the first problem I have had, and even with this it is still backing up every day with no errors.

    Luckily I have not had the need to restore a system (and like you I have multiples running, some 24 hrs a day)

    Thanks for the help.

    Jer

    FowlerJ
    Tuesday, November 4, 2008 4:23 AM
  • Hi Jerry,
    while a reboot is not necessary for the success/failure auditing and activation of group policies, it can speed things up.
    Sending the logs by mail would be ok, if the size is not too huge.
    Best greetings from Germany
    Olaf
    Tuesday, November 4, 2008 7:31 AM
    Moderator
  • Hi Olaf;

    It took quite a while but I was able to do a re-install of the home server.  After calling MS to get it re-authorized I am back up and running.  I have been able to connect through the connector software and will try tomorrow from work to connect thru the internet.  I appreciate all your help.  Even we were not able to get mine back running, this does show me that there are ways to get it fixed.  Again thanks for all the suggestions.

    I am sure I will have questions in the future and hope to be using WHS for quite a while.

    your friend,

    Jerry (in the mid-west)

    FowlerJ
    Friday, November 14, 2008 1:03 AM
  • Hi Jerry,
    quick question:
    Do you happen to have an ATI or NVidia graphics card in your server and installed their drivers?
    If yes, I have posted a fix in another thread yesterday.
    Best greetings from Germany
    Olaf
    Friday, November 14, 2008 7:24 AM
    Moderator
  • I checked my hardware and I have Intel 82945 Chipset.  The next thing is, it has been running great, I am scared to install any of the upgrades.  I believe that PP! has already installed.  Do you think that any of the upgrades might have caused my problem?.

    Thanks for all your help

    Jerry

    FowlerJ
    Sunday, November 16, 2008 4:49 AM
  • Cobol Kid said:

    I checked my hardware and I have Intel 82945 Chipset.  The next thing is, it has been running great, I am scared to install any of the upgrades.  I believe that PP! has already installed.  Do you think that any of the upgrades might have caused my problem?.

    Thanks for all your help

    Jerry


    FowlerJ




    That depends.  Do you update your server through the Console (or by logging into the server desktop and running Windows/MS Update)?  If the latter, did you install any Software, Optional updates?
    Sunday, November 16, 2008 3:13 PM
    Moderator