Error occurred during unpacking the remote end
Steps, which I followed: On system A (remote):
The only "pipe closed" error on Egit is mentioned in bug 314107 and isn't related to your case.
The only suspicious element in your scenario is the address of your remote repo. With the file protocol, I would specify:
file:///192.168.100.28/Git/repo.git
As the OP Abhay comments, the destination folder was write protected, which was enough to trigger that error message.
This issue is not specific to Egit. It occurs when git cannot write to the destination folder on the remote system. This could be, as noted in another answer, that the folder did not have the correct permissions. It could also be for other reasons, such as in my case where the file system had reached full capacity.