none
Cannot connect to server using console RRS feed

  • Question

  • Hi All,

    I am having problems connecting to my server via the console from 2 pcs.

    At first, everything was working fine including the console. I changed the IP settings on my server from DHCP to static with the gateway and the DNS servers (set them up to the same as on my 2 pcs wich are the ISP's dns)

    I also installed (and removed since then) WebGuide 4.

    Now i cannot connect via tha console. I have installed the server toolkit and the connection troubleshooter tells me that the version of the connector is diffrent.

    Uninstalled the connector from my pc and re-installed it from the shred folder on the server as stated in many other posts that i read on the subject, still same issue.

    I also ran the connector troubleshooter with the -a switch to see what's going on, everything passes except the version check.

    Here is the result of that section:

    [4]090312.073019.2425: Network: =========================================================
    [4]090312.073019.2425: Network: =========================================================
    [4]090312.073019.2425: Network: Test Check client Version begin.
    [13]090312.073019.2425: Network: Getting Client Version ...
    [13]090312.073019.2425: Network: Done. Client Version is 6.0.1800.36.
    [13]090312.073019.2425: Network: Getting Server Version ...
    [13]090312.073019.2425: Network: Done. Server Version is 6.0.1800.0.
    [13]090312.073019.2425: Network: versions are different but still all RTM builds.
    [4]090312.073019.2425: Network: Test Check client Version end.
    [4]090312.073019.2425: Network: Information for test Check client Version:
     Server Version: 6.0.1800.0
    Client Version: 6.0.1800.36

    Could this prevent the console from connecting to the server?
    If so, how can this be fixed?

    All the pcs/ server involved are up to date with Windows Update.

    Thank you


    Thursday, March 12, 2009 12:13 PM

Answers

  • I do not understand why but it works now.

    I cleared the event log to run a test to see what i would get and the console just connected and started normally.

    I didn't change any settings anywhere, nor retarted the pc or the server i was using, the only thing i did was to connect remotlly yesterday morrning before i posted my last answer to see the result, maybe that fixed it?

    Anyway thank you for the time you took to help me.
    Saturday, March 14, 2009 11:02 AM

All replies

  • MArkyMArc said:

    Hi All,

    I am having problems connecting to my server via the console from 2 pcs.

    At first, everything was working fine including the console. I changed the IP settings on my server from DHCP to static with the gateway and the DNS servers (set them up to the same as on my 2 pcs wich are the ISP's dns)

    I also installed (and removed since then) WebGuide 4.

    Now i cannot connect via tha console. I have installed the server toolkit and the connection troubleshooter tells me that the version of the connector is diffrent.

    Uninstalled the connector from my pc and re-installed it from the shred folder on the server as stated in many other posts that i read on the subject, still same issue.

    I also ran the connector troubleshooter with the -a switch to see what's going on, everything passes except the version check.

    Here is the result of that section:

    [4]090312.073019.2425: Network: =========================================================
    [4]090312.073019.2425: Network: =========================================================
    [4]090312.073019.2425: Network: Test Check client Version begin.
    [13]090312.073019.2425: Network: Getting Client Version ...
    [13]090312.073019.2425: Network: Done. Client Version is 6.0.1800.36.
    [13]090312.073019.2425: Network: Getting Server Version ...
    [13]090312.073019.2425: Network: Done. Server Version is 6.0.1800.0.
    [13]090312.073019.2425: Network: versions are different but still all RTM builds.
    [4]090312.073019.2425: Network: Test Check client Version end.
    [4]090312.073019.2425: Network: Information for test Check client Version:
     Server Version: 6.0.1800.0
    Client Version: 6.0.1800.36

    Could this prevent the console from connecting to the server?
    If so, how can this be fixed?

    All the pcs/ server involved are up to date with Windows Update.

    Thank you




    The mismatched version numbers in the toolkit are a known issue and if it is only the toolkit that is indicating this error, you can ignore it (i.e. your Windows Home Server tray icon is not red).

    Can you access your shared folders?
    Can you ping the server by name and by IP?
    If you RDP (mstsc.exe) into the server, can you load the Windows Home Server Console on the server itself?

    Thanks!

    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
    Thursday, March 12, 2009 6:39 PM
    Moderator
  • Hi,
    setting the DNS Servers to the addresses of the ISPs DNS servers instead of the routers internal address is in my experience not a good practice in a home network besides for troubleshooting.
    This will cause name resolution attempts being done in the Internet also for your internal server - which may end in a timeout or in the delivery of a wrong address pointing to a machine in the ISPs domain, which has the same name.
    Verify also, that you have not altered the clients hosts file in the past to solve name resolution problems, which now would point to the wrong address.
    Best greetings from Germany
    Olaf
    Thursday, March 12, 2009 8:43 PM
    Moderator
  • "Can you access your shared folders?" -- Yes without any problems

    "Can you ping the server by name and by IP?" -- Yes i can in both cases. I even re-installed the connector using HTTP://servername:55000 and http://serverIpAddress:55000

    "If you RDP (mstsc.exe) into the server, can you load the Windows Home Server Console on the server itself?"  -- If i loggon to the server, i can use the console on the server without any issues.

    "Verify also, that you have not altered the clients hosts file in the past" -- I haven't, it's all default from install on the server and clients side.

    Also, the icon in the tray are green on both pc and the backup is running at 3:00Am on both computers as setup on the server.

    The only part of this that isn't working remotlly is the console, all i get is the Cannot connect to the server error.
    Friday, March 13, 2009 1:16 AM
  • MArkyMArc said:

    "If you RDP (mstsc.exe) into the server, can you load the Windows Home Server Console on the server itself?"  -- If i loggon to the server, i can use the console on the server without any issues.

    did you use Remote Desktop or did you logon locally?
    If the later, try the Remote Desktop client on the PC in Start/Programs/Accessories.
    If this fails, do you have a NVidia graphic card installed in your server?
    Best greetings from Germany
    Olaf

    Friday, March 13, 2009 3:09 AM
    Moderator
  • Tried both and it works in both cases.
    I have the problem from my 2 computers and 1 has an Nvidia card and the other an ATI card.
    The server has an old all-in-wonder 128 pro AGP card.
    Friday, March 13, 2009 9:53 AM
  • Please check the event log of the server for related error messages, warnings and informations around the time you attempt to run the console.
    Are the system times of the server and the clients (including time zones) identical?
    Best greetings from Germany
    Olaf
    Friday, March 13, 2009 11:04 AM
    Moderator
  • I do not understand why but it works now.

    I cleared the event log to run a test to see what i would get and the console just connected and started normally.

    I didn't change any settings anywhere, nor retarted the pc or the server i was using, the only thing i did was to connect remotlly yesterday morrning before i posted my last answer to see the result, maybe that fixed it?

    Anyway thank you for the time you took to help me.
    Saturday, March 14, 2009 11:02 AM