There's not too much to go on here. That "file" is a symbolic link. You can create it by typing the command:
ln -s 1.2.3.4:2747 lock
But it's really only a file if "1.2.3.4:2747" also exists. Otherwise it's just a symbolic link that points nowhere.
If it is a file, a process may have it open. Or I'll bet that some process had a socket connected to 1.2.3.4:2747. Either way, lsof can tell you what the process is.
As I Investigated the probe I think it was because of a system crash while my friend was using my system, I'm not sure about this and I don't think there is any socket associated with the number "2747", though I do not have much knowledge about sockets. Is that possible to be the process id that caused the system crash?