Not sure if that is a smart thing to do. A lot of services intended to run on the local machine use either
127.0.0.1 (which would be no problem with your change) or
localhost (in which case your change would mess things up) to connect to other services on the same machine. And a lot of other packages comes configured this way.
If the purpose is to have the same name to connect crosswise, regardless on which machine you are, I'd rather recommend to use a different name for this. Instead of "localhost" you could e.g. use "crosshost" - and with that follow the hints given by Indrek: Check for your
hosts file (on Linux/Unix and probably also Mac it is
/etc/hosts, on Windows it is
C:\Windows\System32\drivers\etc\hosts (without extension -- so take care here, Windows usually already has some other
hosts.* file in that directory). Do NOT comment out the
127.0.0.1 localhost line, nor modify it -- leave it as is. Just add a line
on the 192.168.1.102 machine, and similarly with the other address on the other machine. Now you can e.g.
ssh crosshost to connect to one machine from the other, or copy files over with
scp filename.ext crosshost:/path/to/put, or whatever you intended.