FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Client installed, but not contacting server

Client installed, but not contacting server 17 Dec 2009 20:34 #164

  • mike.oliveri
  • mike.oliveri's Avatar Topic Author
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 3
  • Thank you received: 0
I've got a client that had to be blown way and reinstalled from an Image. I deleted the (old) client from the Xadmin Clients & Groups, then used the Client Installer Assistant to reinstall FileWave on the new, imaged client. The dialog box, etc., indicate the installation was successful.

However, when I go to the Client Manager and try to add a new client from the server, this client doesn't show up.

What could be causing this?

Thanks,
Mike


There are a number of things 17 Dec 2009 23:43 #720

  • FileWave
  • FileWave's Avatar
  • Offline
  • User is blocked
  • User is blocked
  • Posts: 218
  • Thank you received: 0
There are a number of things that could prevent a client from showing up in the list of new clients ranging from the client not running to network connectivity issues between the client and server.


I would first use the Cilent Status Monitor to manually connect to the IP of the client and see what the status is. This verifies that the client is both running, and configured correctly. The ideal status message should be "Unknown client name" to indicate it has reached the server but the server has not recognized the name of the client.


If the client appears to not be running, it's best to SSH or ARD into the client and verify the fwcld process is running and that you can ping the DNS name/IP of the server from the client.


It's difficult to say what steps to take from here on without knowing more about the state of the client.

Client installed, but not contacting server 12 Apr 2010 16:06 #762

  • John Robertson
  • John Robertson's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 36
  • Thank you received: 1
FW 4.0.4, Mac OS X 10.6.3


I tried reinstalling the FW client and fwcld and fwgui are running. I rebooted the MacBook.


I am trying to update a client. It is showing the wrong IP address in FW Client Monitor and the status is [disconnected]. If I manually change the IP to the current one, FW Client Monitor updates and I get the client name and the status changes to Cannot connect to FW Server... I click on Verify and it says it sent the verify command to the client. Other computers in this building are connecting and updating based on seeing the most current model number.


I can ping the server's DNS and IP. It appears the fwcld and fwgui are running on the client.


Any insight to procedures in getting this client to reconnect will be appreciated.


The client log contains




============= HEADER =============


12/Apr/10 11:10:28.185|0xa04d4500|INFO|CLIENT|FileWave Client 4.0.4 (9496)


12/Apr/10 11:10:28.187|0xa04d4500|INFO|CLIENT|Setting debug level to: 10


12/Apr/10 11:10:28.188|0xa04d4500|INFO|CLIENT|Running on Mac OS 10.6.2 (Intel)


12/Apr/10 11:10:28.190|0xa04d4500|INFO|CLIENT|cannot find the catalog file: /private/var/FileWave/theCatalog


12/Apr/10 11:10:28.220|0xb0185000|INFO|Status Server listening on port: 20010


12/Apr/10 11:10:30.376|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0


12/Apr/10 11:12:30.573|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0


12/Apr/10 11:14:22.734|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0




12/Apr/10 11:18:15.850|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0


============= HEADER =============


12/Apr/10 11:18:39.044|0xa04d4500|INFO|CLIENT|FileWave Client 4.0.4 (9496)


12/Apr/10 11:18:39.072|0xa04d4500|INFO|CLIENT|Setting debug level to: 10


12/Apr/10 11:18:39.072|0xa04d4500|INFO|CLIENT|Running on Mac OS 10.6.2 (Intel)


12/Apr/10 11:18:39.133|0xb0185000|INFO|Status Server listening on port: 20010


12/Apr/10 11:18:42.556|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0


12/Apr/10 11:20:42.749|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0


12/Apr/10 11:22:42.990|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0




12/Apr/10 11:39:50.720|0xa04d4500|INFO|CLIENT|Reset Catalog, new user or differentID 0
John Robertson | Technology Coordinator
Ravenna Public Schools | 12322 Stafford Street | Ravenna, MI 49451

Client installed, but not contacting server 12 Apr 2010 17:56 #763

  • John Robertson
  • John Robertson's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 36
  • Thank you received: 1
I ended up reimaging, renaming the computer and installing FW client 4.0.4. It began updating before I got FW Admin fired up to look at the Client Monitor. It looks like reimaging was the ticket.
John Robertson | Technology Coordinator
Ravenna Public Schools | 12322 Stafford Street | Ravenna, MI 49451

Client installed, but not contacting server 13 Apr 2010 14:46 #764

  • rolf.david.wessel
  • rolf.david.wessel's Avatar
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 1
  • Thank you received: 0
I have the exact same symptoms on one client, tried reimage the machine, and even changed the computer name, but it still gets the "Cannot connect to the FW Server..." version is 4.0.4 on both server and client. And server is running on an intel xserve with 10.6.2. Other machins on the network can connect fine to the server, and modelupdates works fine.


Client log is:



13/Apr/10 16:16:44.600|0xa05ca500|INFO|CLIENT|Reset Catalog, new user or differentID 0


============= HEADER =============


13/Apr/10 16:17:43.732|0xa05ca500|INFO|CLIENT|FileWave Client 4.0.4 (9496)


13/Apr/10 16:17:43.735|0xa05ca500|INFO|CLIENT|Setting debug level to: 10


13/Apr/10 16:17:43.735|0xa05ca500|INFO|CLIENT|Running on Mac OS 10.6.2 (Intel)


13/Apr/10 16:17:43.748|0xb0185000|INFO|Status Server listening on port: 20010


13/Apr/10 16:17:45.883|0xa05ca500|INFO|CLIENT|Reset Catalog, new user or differentID 14301


============= HEADER =============


13/Apr/10 16:18:52.549|0xa05ca500|INFO|CLIENT|FileWave Client 4.0.4 (9496)


13/Apr/10 16:18:52.589|0xa05ca500|INFO|CLIENT|Setting debug level to: 10


13/Apr/10 16:18:52.590|0xa05ca500|INFO|CLIENT|Running on Mac OS 10.6.2 (Intel)


13/Apr/10 16:18:52.619|0xb0185000|INFO|Status Server listening on port: 20010


============= HEADER =============


13/Apr/10 16:23:38.994|0xa05ca500|INFO|CLIENT|FileWave Client 4.0.4 (9496)


13/Apr/10 16:23:39.062|0xa05ca500|INFO|CLIENT|Setting debug level to: 10


13/Apr/10 16:23:39.063|0xa05ca500|INFO|CLIENT|Running on Mac OS 10.6.2 (Intel)


13/Apr/10 16:23:39.198|0xb0185000|INFO|Status Server listening on port: 20010
  • Page:
  • 1