Fog no such device or address



  • This is the version information:
    Tue Feb 28, 2017 17:56 pm
    Running Version 1.3.4
    SVN Revision: 6066
    The FOG server is running CentOS Linux 6.8

    I get “no such device or address” in a red dot to the left of the host name when listing hosts in the GUI. This was not the case yesterday. I have followed some of the suggestions from other threads.

    This is the contents of /etc/resolv.conf on the FOG server

    ; generated by /sbin/dhclient-script
    search localdomain
    nameserver 192.168.0.1
    

    This is the result of nslookup 192.168.0.1 from the FOG server

    Server:		192.168.0.1
    Address:	192.168.0.1#53
    
    1.0.168.192.in-addr.arpa	name = ipcop2.localdomain.
    

    This the result of pinging the router by name from the FOG server

    PING ipcop2.localdomain (192.168.0.1) 56(84) bytes of data.
    64 bytes from ipcop2.localdomain (192.168.0.1): icmp_seq=1 ttl=64 time=0.193 ms
    64 bytes from ipcop2.localdomain (192.168.0.1): icmp_seq=2 ttl=64 time=0.141 ms
    64 bytes from ipcop2.localdomain (192.168.0.1): icmp_seq=3 ttl=64 time=0.102 ms
    64 bytes from ipcop2.localdomain (192.168.0.1): icmp_seq=4 ttl=64 time=0.110 ms
    
    

    and by ip-address

    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.184 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.167 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.128 ms
    64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.134 ms
    

    I can ping both the router (192.168.0.1) and the fog server (192.168.0.3) from the Windows client. On the Windows client nslookup shows

    Standard server  ipcop2.localdomain
    Address 192.168.0.1
    

    Like I said, this was working before I rebooted the FOG server.



  • @george1421 It worked!
    I clicked on the host name in the list and in that page reset the encryption data. Now that host has joined the domain and got the right printer.

    I will now do these steps on our master image.

    Thank you for your kind and patient help.


  • Developer

    @george1421 it sounds like you’ve got it right to me


  • Moderator

    @cajos001 OK from the communications side it looks like the windows firewall is blocking ping attempts. You will need to allow this communication for each workstation. (ICMP ping, reply).

    As for the security token, that is out of my realm so I’m guessing here. There should be a “reset security information” option for that host (I can’t seem to find it). What its saying is the certificate finger printed on the client doesn’t match the FOG server. This happens if you reimage your FOG server (wipe and replace) and a new certificate is created.

    @Developers A little guidance would be appreciated.



  • @cajos001 I disabled the Windows firewall and can ping the Windows client by IP address from the FOG server.

    However the log file now shows “Response Invalid security token”

    2017-03-01 17:05 Main Bootstrapping Zazzles
     2017-03-01 17:05 Controller Initialize
     2017-03-01 17:05 Zazzles Creating main thread
     2017-03-01 17:05 Zazzles Service construction complete
     2017-03-01 17:05 Controller Start
    
     2017-03-01 17:05 Service Starting service
     2017-03-01 17:05 Bus Became bus server
     2017-03-01 17:05 Bus {
      "self": true,
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     2017-03-01 17:05 Bus Emmiting message on channel: Status
     2017-03-01 17:05 Service Invoking early JIT compilation on needed binaries
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     2017-03-01 17:05 Client-Info Version: 0.11.9
     2017-03-01 17:05 Client-Info OS:      Windows
     2017-03-01 17:05 Middleware::Authentication Waiting for authentication timeout to pass
     2017-03-01 17:05 Middleware::Communication Download: http://192.168.0.3/fog/management/other/ssl/srvpublic.crt
     2017-03-01 17:05 Data::RSA FOG Server CA cert found
     2017-03-01 17:05 Middleware::Authentication Cert OK
     2017-03-01 17:05 Middleware::Communication POST URL: http://192.168.0.3/fog/management/index.php?sub=requestClientInfo&authorize&newService
     2017-03-01 17:05 Middleware::Response Invalid security token
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     2017-03-01 17:05 Client-Info Version: 0.11.9
     2017-03-01 17:05 Client-Info OS:      Windows
     2017-03-01 17:05 Middleware::Authentication Waiting for authentication timeout to pass
    


  • @george1421 I’ll do that and post the result.


  • Moderator

    @cajos001 ok, can you ensure (or temporarily disable) the windows firewall on a test system. We need to ensure that the firewall isn’t blocking the pings from a unix based computer.

    Also when you set the static IP on the FOG server it must remain the same address as when FOG was installed.



  • @george1421

    I’ve changed the network setting to static and restarted the server.

    I cannot ping the Windows clients by name or IP address from the FOG server.


  • Moderator

    @cajos001 said in Fog no such device or address:

    @george1421 Sorry for the late reply.

    Yes our FOG servers IP is assigned by DHCP.

    The Windows client can ping the FOG server but does not respond to ping from the FOG server.

    I guess point 1, your FOG server needs a consistent IP address. You can do this through dhcp reservations or by assigning a static IP address to your fog server. If your fog server changes IP address (because of dhcp) after FOG is installed, FOG will break.

    And just for clarity, you can ping your windows clients by IP address but not by workstation name from the fog server, correct?



  • @george1421 Sorry for the late reply.

    Yes our FOG servers IP is assigned by DHCP.

    The Windows client can ping the FOG server but does not respond to ping from the FOG server.

    Here’s a partial fog.log from the Windows client.

    --------------------------------PowerManagement-------------------------------

    2017-03-01 14:30 Client-Info Client Version: 0.11.9
    2017-03-01 14:30 Client-Info Client OS: Windows
    2017-03-01 14:30 Client-Info Server Version: 1.3.4
    2017-03-01 14:30 Middleware::Response ERROR: Unable to get subsection
    2017-03-01 14:30 Middleware::Response ERROR: Objektreferensen har inte angetts till en instans av ett objekt.
    (Translation = Object reference not set to an instance of an object.)


    ----------------------------------UserTracker---------------------------------

    2017-03-01 14:30 Client-Info Client Version: 0.11.9
    2017-03-01 14:30 Client-Info Client OS: Windows
    2017-03-01 14:30 Client-Info Server Version: 1.3.4
    2017-03-01 14:30 Middleware::Response ERROR: Unable to get subsection
    2017-03-01 14:30 Middleware::Response ERROR: Objektreferensen har inte angetts till en instans av ett objekt.
    2017-03-01 14:30 Service Sleeping for 60 seconds
    2017-03-01 14:31 Middleware::Communication URL: http://192.168.0.3/fog/management/index.php?sub=requestClientInfo&configure&newService&json
    2017-03-01 14:31 Middleware::Communication ERROR: Could not contact FOG server
    2017-03-01 14:31 Middleware::Communication ERROR: Det går inte att ansluta till fjärrservern
    2017-03-01 14:31 Middleware::Response Success
    2017-03-01 14:31 Service ERROR: Invalid promptTime, using default
    2017-03-01 14:31 Middleware::Communication URL: http://192.168.0.3/fog/management/index.php?sub=requestClientInfo&mac=B8:F6:B1:36:90:08|40:6C:8F:28:51:BE|7C:C3:A1:AE:73:46||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
    2017-03-01 14:31 Middleware::Communication ERROR: Could not contact FOG server
    2017-03-01 14:31 Middleware::Communication ERROR: Det går inte att ansluta till fjärrservern
    2017-03-01 14:31 Middleware::Response Success
    2017-03-01 14:31 Middleware::Communication URL: http://192.168.0.3/fog/service/getversion.php?clientver&newService&json
    2017-03-01 14:31 Service ERROR: Unable to get cycle data
    2017-03-01 14:31 Service ERROR: Det går inte att ansluta till fjärrservern
    2017-03-01 14:31 Middleware::Response Success


    ---------------------------------ClientUpdater--------------------------------

    2017-03-01 14:31 Client-Info Client Version: 0.11.9
    2017-03-01 14:31 Client-Info Client OS: Windows
    2017-03-01 14:31 Client-Info Server Version: 1.3.4
    2017-03-01 14:31 Middleware::Response ERROR: Unable to get subsection
    2017-03-01 14:31 Middleware::Response ERROR: Objektreferensen har inte angetts till en instans av ett objekt.


  • Moderator

    Is your fog server’s IP assigned by DHCP?

    What is the issue is the fog server can not find the IP address of your windows clients.

    It appears that your fog server can ping the router by name, but it can’t ping the windows devices by name?

    Is the FOG client installed on your target computers?



  • I reinstalled FOG from SVN, erased all the hosts and recreated a few but the red dot and the error message “no such device or address” persists.

    Help me please.


Log in to reply
 

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