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.