PrinterManager Failed to connect to fog server
-
Server
- FOG Version: 1.3.4 SVN version 6066
- OS: CentOS Linux 6.8
Client
- Service Version: 3
- OS: Windows 7 Professional fully updated
Description
I’m using the legacy client from the FOG server as the new version keeps giving me security errors:
Changing hostname and joining the domain work well but the PrinterManager keeps giving the error as listed in the excerpt from the log file:
2017-03-09 17:06 FOG::UserTracker Event: LOGIN for Bib06\Administratör
2017-03-09 17:06 FOG::UserTracker Record processed by server!
2017-03-09 17:06 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:06 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:06 FOG::PrinterManager Sleeping for 1 minute.
2017-03-09 17:06 FOG::SnapinClient Attempting to connect to fog server…
2017-03-09 17:06 FOG::SnapinClient Module is active…
2017-03-09 17:06 FOG::SnapinClient No Tasks found for: 40:6C:8F:28:69:30
2017-03-09 17:07 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:07 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:07 FOG::PrinterManager Sleeping for 1 minute.
2017-03-09 17:08 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:08 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:08 FOG::PrinterManager Sleeping for 1 minute.
2017-03-09 17:09 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:09 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:09 FOG::PrinterManager Sleeping for 1 minute.
2017-03-09 17:10 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:10 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:10 FOG::PrinterManager Sleeping for 1 minute.
2017-03-09 17:11 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:11 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:11 FOG::PrinterManager Sleeping for 1 minute.
2017-03-09 17:11 FOG::SnapinClient Attempting to connect to fog server…
2017-03-09 17:11 FOG::SnapinClient Module is active…
2017-03-09 17:12 FOG::SnapinClient No Tasks found for: 40:6C:8F:28:69:30
2017-03-09 17:12 FOG::PrinterManager Failed to connect to fog server!
2017-03-09 17:12 FOG::PrinterManager This is typically caused by a network error!
2017-03-09 17:12 FOG::PrinterManager Sleeping for 1 minute.Is there a solution?
-
Here’s the printer config as output by FOG PrinterManagerHelper
192.168.0.247
BIB_247
HP Universal Printing PCL 6 (v6.3.0)
C:\Windows\inf\ntprint.inf -
Two things,
First maybe try RC 12 of 1.3.5? I believe there was an issue with the legacy client on 1.3.4 that I’m pretty sure was addressed during one of the RC’s of 1.3.5.
Second, I’d recommend updating your clients to the new client. The legacy client, while still supported currently, is rather outdated and inefficient, and less stable the “newer” the OS applied to.
The legacy client was designed around when Windows XP was the “big” thing, which was from 2007 until about 2009. It didn’t change much between 2009 and 2013 (which FOG 1.X.X was released.)
With the release of 1.3.X came a new client. This new client is far faster, and less resource intensive to the servers than the legacy clients, and comes with a lot more security factors as well. I would highly recommend updating to the RC’s and even more so suggest updating to use the New FOG Client.
-
I’ll download the RC 12 and start over with the new client. I’m experimenting with just a few hosts just now instead of 879 hosts until I get it right.
-
How do I download the RC 12?
-
The coffee hadn’t kicked in yet , I found the instructions here https://wiki.fogproject.org/wiki/index.php?title=Installation#Additional_information_on_SVN_and_git_.26_FOG_Trunk
-
@cajos001 And we’re up to RC 13 now
-
Yes I that’s what was downloaded. I deleted all my hosts except my master so I can get on the right side of the encryption. I’ve added back six hosts in the library nearest my office to test.
Everything worked! Hostname, domain and installing and removing printers. Now I can go home and have a happy Friday
-
That’s what we are hoping for. All of us IT people being able to go home without a worry and feeling “accomplished”.
Glad it worked.
For what it’s worth, the new client will also enable your hosts to “re-associate” themselves. There is a little involvement as you will have to “approve” the hosts, but you don’t even need to go through the whole registration process.
