sorry for lack of updates on this... As an fyi.. there was a few causes to this error... the first was that the f: drive being mapped by the agent was already mapped. I have to create a new configuration to map the drive to g: and this has now been fixed by the GS3 HF update..
The second cause was due to an existing ghost2.5 client on some of the machines! This caused the older ghost partition to boot instead of the automation partition ghost and it was trying to connect to the older ghost server! After i removed the old ghost agent everything worked