locked
Connector/Remote Access problem RRS feed

  • Question

  • I had to replace my router and the IP address set up has changed from 192.168.0.1 to 192.168.2.0 etc.

    My new Router (Belkin N1) assigned new addresses to the server and clients. I hooked up a KB, mouse and monitor and then via Console settings, WHS configured the router via UPnP with no problem at all. However despite this I still could not connect from the clients via Remote Access or WHS Connector to the server.

    So I reinstalled Connector on the clients, a slow and cludgy process, and eventually joined up with the server. However I still cannot connect to the server using RA or Connector but I CAN right click on the console sys tray icon and back up the clients with no problem at all.

    I am running PP1 on the server and Vista on the clients with all current fixes in place. I have also manually forwarded 80,443 & 4125 and enabled/disabled firewalls to no effect. I can also ping the server using client name or address with no problem.

    Any thoughts/suggestions eagerly awaited and appreciated.

     

     

    Colin

     

    Friday, August 29, 2008 7:25 AM

Answers

  • GAME OVER!

    Hi Olaf,
    Well I don't know how but we are back up and running now. I changed the server name and then changed it back to the original name, reinstalled the connector software for the second time and boom, everything now works fine!
    Thanks for your input and
    "haben ein gutes Wochenende"

    Colin
    • Marked as answer by corkyboy Friday, September 26, 2008 9:30 AM
    Saturday, August 30, 2008 6:51 AM

All replies

  • You would not have to reinstall the connector software - usually it is enough to run discovery.exe from the folder Program Files\Windows Home Server on the client to get the connector reconnected.

     

    Can you perform a remotedesktop connection (or at least issue a ping) from one of your clients to the server

    a) by using the name

    b) by using the IP address?

     

    If the first doesn't work, but the second does, this would point to some name resolution problems.

    Best greetings from Germany

    Olaf

    Friday, August 29, 2008 7:37 AM
    Moderator
  • As I mentioned in my message, no problems pinging the server, name and IP address both work. I cannot connect via Remote Desktop or Connector.

    Greetings from Australia, where the sun is now setting.

     

     

    Colin

     

    Friday, August 29, 2008 7:49 AM
  • Hi Colin,

     corkyboy wrote:

    As I mentioned in my message, no problems pinging the server, name and IP address both work. I cannot connect via Remote Desktop or Connector.

    \

    oops, bad glasses or to early in the morning I assume.

    Can you check the event log of the server for Terminal services / Remote Desktop related messages?

    Check also the Computer properties of the WHS, if on the Remote tab the toggle for allowing Remote Desktop connections is still set.

    Uncheck it, apply, check it again, apply.

    Check the Windows Firewall on the server, if Remote Desktop connections are allowed.

    Best greetings from Germany

    Olaf

    Friday, August 29, 2008 8:00 AM
    Moderator
  • Olaf,
    With regard to discovery.exe, i have just run this on another client and the end result is the same, Connector and Remote Desktop will not connect but I can back up via the sys tray icon.


    Colin
    Friday, August 29, 2008 8:05 AM
  • I have checked and actioned everything as you suggested but no change I am afraid. Event log shows no problem entries for Remote Desktop, Security or WHS.

     

     

    Colin

     

    Friday, August 29, 2008 9:00 AM
  • Breakthrough!

     

    I have just tried to Remote Desktop the Server again but this time using the IP address instead of the name..........and it worked!

    What are the implications of this I wonder as I cannot connect via the WHS console using just the IP?

     

     

    Colin

     

    Friday, August 29, 2008 9:29 AM
  • Hi Colin,

    try to configure your routers IP address as DNS server for the connected clients and the WHS. If possible in both the DHCP settings of the router and if you used fixed entries for the Windows DNS servers also here, since DHCP does not overwrite preconfigured DNS settings.

     

    Also check in the network card TCP/IP properties of the network on Advanced button/WINS tab, if NetBios over TCP/IP is enabled.

     

    (What is the output of ipconfig /all in a cmd prompt on client and server?)

     

    Best greetings from Germany

    Olaf

    Friday, August 29, 2008 1:00 PM
    Moderator
  • you'll have to change your port forwarding rules, again.

    i had my port forwarding rules for my server to 192.168.0.2 ... then i swapped routers and the server address changed to 192.168.0.4.

    So I port forwarded all incoming traffic data from port 80, and those other ports to the new one; i.e. 192.168.0.4.

    and then went into the console and reconfigured the router and domain address.

    And then everything was fine again.

    If you want to keep the old address, you'll have to reserve the server address to the original one on your router ... (e.g. it would be 192.168.0.2).


    Friday, August 29, 2008 4:24 PM
  • G'Day Olaf,
    Firstly thanks for your replies and to business. My router does not support fixed IP entries, I have assigned an IP address to the server but this makes no difference. I can still ping OK by host name and IP address.
    However, when I looked at the Routing and Remote Access set up on the server via Admin Tools it says that the it is "unconfigured" and the state is "stopped". I looked at the options for configuring it manually but was not sure how or if I should proceed.

    Please find below the results of ipconfig/all firstly for the server and then one of the client PC's:

    Windows Home Server:
    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.

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

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : GothamCity
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Belkin

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : Belkin
       Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet
     NIC
       Physical Address. . . . . . . . . : 00-19-DB-B1-94-A4
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 192.168.2.6
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCP Server . . . . . . . . . . . : 192.168.2.1
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       Lease Obtained. . . . . . . . . . : 30 August 2008 10:47:28
       Lease Expires . . . . . . . . . . : 18 January 2038 20:14:07

    C:\Documents and Settings\Administrator>

    ================================================================================

    Client PC Vista 32 Remote Desktop Connection:

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\Colin>ipconfig/all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Batman
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Belkin

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : Belkin
       Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab
    it Ethernet NIC (NDIS 6.0)
       Physical Address. . . . . . . . . : 00-19-DB-F2-2E-0A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::91c8:1522:2b8:7f2f%8(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Saturday, 30 August 2008 11:25:19 AM
       Lease Expires . . . . . . . . . . : Tuesday, 6 October 2144 6:57:15 PM
       Default Gateway . . . . . . . . . : 192.168.2.1
       DHCP Server . . . . . . . . . . . : 192.168.2.1
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Connection-specific DNS Suffix  . : Belkin
       Description . . . . . . . . . . . : isatap.Belkin
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.2%13(Preferred)
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 192.168.2.1
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Local Area Connection* 10:

       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:814:313:3f57:fdfd(Prefer
    red)
       Link-local IPv6 Address . . . . . : fe80::814:313:3f57:fdfd%11(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\Users\Colin>
    Saturday, August 30, 2008 2:51 AM
  • GAME OVER!

    Hi Olaf,
    Well I don't know how but we are back up and running now. I changed the server name and then changed it back to the original name, reinstalled the connector software for the second time and boom, everything now works fine!
    Thanks for your input and
    "haben ein gutes Wochenende"

    Colin
    • Marked as answer by corkyboy Friday, September 26, 2008 9:30 AM
    Saturday, August 30, 2008 6:51 AM
  • Hi corkyboy

    I was noticing you're client machine has the same network card is I do (RTL8168B).  You may wish to try if you can do a restore on you're client.  I was unable to find the Server while using the Realtek RTL8168B network card.  Even the latest driver from dlink didn't fix it.  It would be interesting to know if you're works.

    Thanks
    -- Andrew
    Thursday, November 20, 2008 1:07 PM