1 of 1 people found this helpful
this problem is only on one machine or every new machine you install ?
r u able to telnet both server and client on thier spicific ports (default 5555, 5556) vice-versa ?
could you please post LOGS here (you will get it from) SCMLOG.txt (in safeboot foldeR)
try to synchronize after safeboot Client manager service restart
Can you send Snapshot of installation set creation ? (the tab where you are selecting Available Database connection)
Message was edited by: rbdudani on 6/26/11 9:06:38 PM CDT
This is on every new machine, not just one.
I can telnet to the server on port 5555, but can't telnet to the local client (127.0.0.1 from the client) on port 5556. Seems strange...
I've attached a SCMLOG.txt from one of these machines. I've just put a clean image on it, and installed SafeBoot on it, so the log isn't very big, but it shows you where it gets stuck.
Here's a screenshot of the database configuration I'm choosing on the installation set creation
And here's the information of the selected database
SCMLOG.TXT.zip 670 bytes
logs says machines are synching with server.. (so there is no connectivity issue as Machine ID is created)
are you getting any error on server or client when you add users ?
When I add a user to a machine on the server, it appears to work fine. If I go back and look at the properties of the machine then I can see it is added fine. The user never actually gets set up on the laptop though. If I try and log in past SafeBoot as the user I have added, it tells me it is an unknown user. The logs should also show a user being added when it is synchronising, which it isn't doing.
r u sure you are adding user to right machine ?? for example if we talk about machine for which you posted logs here
its machine ID is 000008bc
so please croass verfiy that you are adding user to right machine..
Yes, user is definitely added to right machine. You can see from the logs that although it can connect to the server, it isn't actually synchronising properly. It does the initial synchronisation (where it creates the machine object, etc.) fine, but after that it doesn't. It gets stuck on 'Checking for screen saver updates'. On a computer that works, it shows 'Synchronisation complete', and then 'Automatically synchronising again in 60 minute(s)'. I don't get those entries on the new machines that aren't working.
And also like I mentioned earlier, I can't telnet to the client on port 5556, however on the old machines that are still synchronising fine I CAN telnet to them on port 5556. So it's something wrong with the client, just not sure what.
hmmmm, got you
please send me snap shot of preoperties > Files
1. for working
2. for not working
(Just wanted to know what is selected in file group)
and on every not workling machine r u geting same as below logs
06/27/11 12:53:46 recovering from power failure
Here's something interesting... I left this laptop going and on the network last night. Since SafeBoot was only installed yesterday morning, the hard drive was still encrypting. Naturally, it takes a number of hours to finish the encryption. After the encryption had completed, it successfully synchronised. If I now perform a manual synchronisation, it works fine.
So basically the behaviour I'm seeing, is that a machine will only synchronise after the hard drive encryption is completed. I have attached the log from this machine I've been testing which verifies this behaviour. Surely this is not by design? Am I missing something?
SCMLOG.TXT.zip 931 bytes