Keeping hostname when imaging



  • Hi,
    How to keep hostname of XP host when imaging?
    Regards



  • Hi,
    When I install fog client with server hostname (not IP server), it seem’s OK. fog 252 must be defined in hosts file like :
    10.1.1.252 fog252



  • Me, also. Last thing to verify. My dhcp is on another server. To morrow I reinstall fog with dhcp on the same server. Thanks a lot for help.


  • Developer

    I surrender :(
    I don’t know where is the problem.
    You can make ping to the server, you can get a response from the server in a navigator (you don’t obtain a forbidden response)
    But the FOG client says that he can’t connect to the server, the access is forbidden.
    I don’t understand nothing :mad:



  • Yes

    ------------------------------------------------------------------------

    What is the ip address or hostname of the webserver?

    ------------------------------------------------------------------------

        ipaddress=10.1.1.252

  • Developer

    And the config.ini in the client?
    The server address is right in config.ini?



  • #!ok=GEA156 #AD=0 #ADDom= #ADOU= #ADUser= #ADPass=


  • Developer

    Ok :) you can make ping to the server. But can you see the webui from the client?
    Open a navigator and try the next direction:
    [I]10.1.1.252/fog/service/hostname.php?mac=XX:XX:XX:XX:XX:XX[/I]
    Where XX:XX:XX:XX:XX:XX is the mac addreess.
    What response the server?

    In my servet the response is like this:
    [I]#!ok=U103666 #AD=0 #ADDom= #ADOU= #ADUser= #ADPass=[/I]



  • Microsoft Windows XP [version 5.1.2600]
    © Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\USER>ping 10.1.1.252

    Envoi d’une requête ‘ping’ sur 10.1.1.252 avec 32 octets de données :

    Réponse de 10.1.1.252 : octets=32 temps<1ms TTL=64
    Réponse de 10.1.1.252 : octets=32 temps<1ms TTL=64
    Réponse de 10.1.1.252 : octets=32 temps<1ms TTL=64
    Réponse de 10.1.1.252 : octets=32 temps<1ms TTL=64

    Statistiques Ping pour 10.1.1.252:
    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
    Durée approximative des boucles en millisecondes :
    Minimum = 0ms, Maximum = 0ms, Moyenne = 0ms

    C:\Documents and Settings\USER>



  • Hi,
    fog252@fog252:/$ sudo iptables -L
    [sudo] password for fog252:
    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination


  • Developer

    Are you sure that you don’t have firewall?

    # iptables -L
    Chain INPUT (policy ACCEPT)
    target    prot opt source              destination       
     
    Chain FORWARD (policy ACCEPT)
    target    prot opt source              destination       
     
    Chain OUTPUT (policy ACCEPT)
    target    prot opt source              destination
    

    You can do a ping from client to the server?

    You can see a pretty info in /var/log/httpd/access_log, like this:

    10.227.15.30 - - [03/Dec/2012:16:19:16 +0100] "GET /fog/service/servicemodule-active.php?mac=18:03:73:1B:62:DC%7C08:00:27:00:B0:3F&moduleid=ho
    stnamechanger HTTP/1.1" 200 4 "-" "-"
    10.227.15.30 - - [03/Dec/2012:16:19:16 +0100] "GET /fog/service/hostname.php?mac=18:03:73:1B:62:DC%7C08:00:27:00:B0:3F HTTP/1.1" 200 51 "-" "-
    "
    


  • it receives packets because “Le serveur distant a retourné une erreur : (403) Interdit.” the distant server return an error 403 Forbidden. Thanks for help. I think to go back to my old Rembo or to invest with Acronis. Too much time to resolve problems.



  • You could try running Wireshark (or tcpdump but Wireshark is easier) on the server to check if the server is actually receiving the packets from the client. Its probably best to filter to the clients IP as you will get a whole load of useless information shown.



  • Hi,
    Help needed to debug. What to test, to verify?
    0.32, ubantu 12.04, XP prof Host SP3. Imaging OK, Deploy OK. No firewall on XP and server.

    fog.log
    10/12/2012 15:27 FOG::GreenFog Sleeping for 1 minute.
    10/12/2012 15:28 FOG::ClientUpdater Attempting to connect to fog server…
    10/12/2012 15:28 FOG::ClientUpdater Failed to connect to fog server!
    10/12/2012 15:28 FOG::ClientUpdater Le serveur distant a retourné une erreur : (403) Interdit.
    10/12/2012 15:28 FOG::ClientUpdater à System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
    à System.Net.WebClient.DownloadString(Uri address)
    à System.Net.WebClient.DownloadString(String address)
    à FOG.SnapinClient.startUpdate()
    10/12/2012 15:28 FOG::ClientUpdater Sleeping for 1 minute.
    And so one for other services



  • I have our clients setup just using the default host-name (fogserver), /fog shouldn’t be needed.



  • I wonder if setup client needs ip-server or ip-server/fog ? I try to morrow morning.



  • No firewall on server!



  • No,
    I just update hosts file on XP host with server ip and server hostname. Testing in progress. I shall verify permissions on server itself as you say. Thanks a lot for help.



  • Have you changed any file/folder/firewall permissions on the server itself?



  • Hi,
    XP host log file contents for hostnamechanger :

    08/12/2012 10:49 FOG::HostnameChanger Attempting to connect to fog server…
    08/12/2012 10:49 FOG::HostnameChanger Failed to connect to fog server!
    08/12/2012 10:49 FOG::HostnameChanger Le serveur distant a retourné une erreur : (403) Interdit.
    08/12/2012 10:49 FOG::HostnameChanger à System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
    à System.Net.WebClient.DownloadString(Uri address)
    à System.Net.WebClient.DownloadString(String address)
    à FOG.HostNameChanger.changeHostName()
    08/12/2012 10:49 FOG::HostnameChanger Sleeping for 1 minute.

    Idea, help! I see something like that here, but where?
    Regards


Log in to reply
 

482
Online

38916
Users

10686
Topics

101369
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.