locked
Unable to connect to the server RRS feed

  • Question

  • Need some help. My problem : I've a home build WHS 2011. I already connected 6 PCs to the server (Win 7 32 and 64 bits). For the last one, the most important for me (64 bits) .... i get the message (In french but i think the english tranlation is "unable to connect to the server") asking for the name or IP adress of the server. When i enter the information (both ways) : no success.

    I've to say that when i ping the server by name : everything is OK. The same when if enter in IE http://ServerName. And i can access the Public server share.
    I'm using IE8. I don't use proxy.

    If someone could give me an idea...
    Alain

    What's really suprising is that : FindMyServe.exe generates this http://192.168.1.20:65510/CONNECT/ and that when i click on the link the answer is "unable to locate the server".... I'm really puzzled

    Some more information : X8SIA is the name of the server
    C:\Users\Alain>nbtstat -a 192.168.1.20

    Connexion au réseau local:
    Adresse IP du noeud : [192.168.1.3] ID d'étendue : []

        Table de noms NetBIOS des ordinateurs distants

           Nom                Type         État
        ---------------------------------------------
        X8SIA          <00>  UNIQUE      Inscrit
        WORKGROUP      <00>  Groupe      Inscrit
        X8SIA          <20>  UNIQUE      Inscrit

        Adresse MAC = 00-26-5A-BF-90-74

    C:\Users\Alain>nslookup
    Serveur par dÚfaut :   UnKnown
    Address:  192.168.1.1

    > X8SIA
    Serveur :   UnKnown
    Address:  192.168.1.1

    C:\Users\Alain>ping x8sia

    Envoi d'une requête 'ping' sur X8SIA [192.168.1.20] avec 32 octets de données :
    Réponse de 192.168.1.20 : octets=32 temps<1ms TTL=128
    Réponse de 192.168.1.20 : octets=32 temps<1ms TTL=128
    Réponse de 192.168.1.20 : octets=32 temps<1ms TTL=128
    Réponse de 192.168.1.20 : octets=32 temps<1ms TTL=128

    Statistiques Ping pour 192.168.1.20:
        Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
    Durée approximative des boucles en millisecondes :
        Minimum = 0ms, Maximum = 0ms, Moyenne = 0ms
    • Changed type aa15 Thursday, August 18, 2011 9:58 AM
    Thursday, August 18, 2011 9:58 AM

Answers

  • Yes, i tried all this... and all the other ideas i found on the forums including yours of course (and there is a lot).

    What i did'nt mention is that this client was connected to a WHS v1 (as all the other clients i migrated successfully).

    Nethertheless, since that time, i reinstalled windows on this client !

    2 days work... not done since 2 years... A good for a bad.

    Thnak you for your reply.

    Alain


    Alain
    Tuesday, August 23, 2011 3:07 PM

All replies

  • Is there any 3rd party security software (containing firewall or other network traffic monitoring functions) installed on this client?

    If so, try to uninstall it temporary.

    Are time, date and timezone correct and identical on both the client and the server?

    Best greetings from Germany
    Olaf

     

    Tuesday, August 23, 2011 2:27 PM
    Moderator
  • Yes, i tried all this... and all the other ideas i found on the forums including yours of course (and there is a lot).

    What i did'nt mention is that this client was connected to a WHS v1 (as all the other clients i migrated successfully).

    Nethertheless, since that time, i reinstalled windows on this client !

    2 days work... not done since 2 years... A good for a bad.

    Thnak you for your reply.

    Alain


    Alain
    Tuesday, August 23, 2011 3:07 PM
  • I have the same problem.  Win 7 64 bit.  Can see the server from this computer may different ways, but Computerconnect.exe does not see it and asks for name, which it cannot resolve, or IP, which it cannot find.
    Monday, September 5, 2011 12:07 PM