Hey Wayne, this problem is resolved. The problem appeared to be within the machine which the image was uploaded from. The hard disk containted IO errors which were untracable by Windows scandisk and chkdsk. Using a different hard drive resolved the problem.
Thanks for your help!.
@Wayne-Workman Hi Wayne,
It seems that the problem is resolved now. The problem appeared to be in the image upload with this 102 MB partition. I’ve booted a gparted iso from CD and removed this partition, then I booted a Windows 7 DVD to recover the drive as it didn’t want to boot with this 102 MB partition.
I totally agree with your remark about the vulnerabilities provided by the manufacturer’s image, but I’ve been completely striping that out.
Besides, I cannot use an OEM license key when I install Windows myself. For this reason I’m stuck with this image. I need to buy retailer CD key’s instead for about 60 machines.
Thank you very much for your help though, if others have simular problems with OEM images provided by manufacturer’s, I might be able to help them.
@Wayne-Workman I have the exact same problem in a callcenter. The problem seems to occur from a cold start but resolves itself when booting to Windows first. This is impacting all images here.
Sttange this is; When I connect the workstation directly into the switchport in the patch cabinet/rack cabinet, the issue doesn’t seem to occur. It only happens when I connect the workstation to a floorport which contains a cable distance of about 25-30 meters.
I think electric or magnetic field causes this problem.
Once I boot-up the workstation into Windows, the issue is resolved, but can return at random timeframes.
Wayne, I just did a SVN checkout and I’m getting the message below:
Checked out revision 4830.
I only see a difference for about +300 revisons, where can I get the revison like you desribed (2000+ revisions ahead)
I did: vn co https://svn.code.sf.net/p/freeghost/code/trunk %path
@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:
@Jbob Thanks for the information!
The problem has been resolved. Thanks for all help.
@Jbob Thanks for the information!
@Tom-Elliott Hi Tom,
I just did a rollback over VMware to our server backup from last night. It is working fine now. Now I have updated the the most recent revison and no errors show up. I am currently monitoring if the problem reappears.
@Tom-Elliott I could do a rollback to an older version. I did update the certificate because this server had an IP change.
@Tom-Elliott Rev 7252:
21-4-2016 17:13 Client-Info Version: 0.9.12
21-4-2016 17:13 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt
21-4-2016 17:13 Data::RSA FOG Server CA cert found
21-4-2016 17:13 Data::RSA ERROR: Certificate validation failed
21-4-2016 17:13 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Kan de handtekening van het certificaat niet controleren. (NotSignatureValid)
21-4-2016 17:13 Middleware::Authentication ERROR: Could not authenticate
21-4-2016 17:13 Middleware::Authentication ERROR: Certificate is not from FOG CA
21-4-2016 17:13 Service Sleeping for 120 seconds
21-4-2016 17:14 Bus Registering ParseBus in channel Power
21-4-2016 17:14 Bus Became bus client
21-4-2016 17:14 Bus Registering OnNotification in channel Notification
21-4-2016 17:14 Bus Registering OnUpdate in channel Update
@Tom-Elliott Different errors this time:
21-4-2016 17:04 Client-Info Version: 0.9.12
21-4-2016 17:04 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt
21-4-2016 17:04 Data::RSA FOG Server CA cert found
21-4-2016 17:04 Data::RSA ERROR: Certificate validation failed
21-4-2016 17:04 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Kan de handtekening van het certificaat niet controleren. (NotSignatureValid)
21-4-2016 17:04 Middleware::Authentication ERROR: Could not authenticate
21-4-2016 17:04 Middleware::Authentication ERROR: Certificate is not from FOG CA
21-4-2016 17:04 Service Sleeping for 120 seconds
21-4-2016 17:05 Bus Registering ParseBus in channel Power
21-4-2016 17:05 Bus Became bus client
21-4-2016 17:05 Bus Registering OnNotification in channel Notification
21-4-2016 17:05 Bus Registering OnUpdate in channel Update```@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:
@Tom-Elliott Hi Tom, I do have revision 7248.
The only difference I have, for this revision there is not token.dat created in c:\windows\system32\
@Tom-Elliott Hi Tom, I do have revision 7248.
@Tom-Elliott Besides I did all your provided steps as well, clearing the security token data.
@Tom-Elliott I have the exact same problem, started recently. I have also upgraded the fog server to a newer revision.
21-4-2016 16:24 Client-Info Version: 0.9.12
21-4-2016 16:24 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt
21-4-2016 16:24 Data::RSA FOG Server CA cert found
21-4-2016 16:24 Middleware::Authentication Cert OK
21-4-2016 16:24 Middleware::Communication POST URL: http://10.10.2.250/fog/management/index.php?sub=authorize
21-4-2016 16:24 Middleware::Communication ERROR: Failed to POST data
21-4-2016 16:24 Middleware::Communication ERROR: De externe server heeft een fout geretourneerd: (417) Expectation Failed.
21-4-2016 16:24 Middleware::Authentication ERROR: Could not authenticate
21-4-2016 16:24 Middleware::Authentication ERROR: Object reference not set to an instance of an object.
21-4-2016 16:24 Service Sleeping for 120 seconds