I once had a similar issue (but not fully the same), alas I forgot how I fixed it.
Some suggestions:
Any mention of *.0.2 in your host file? FF might read it differently from other programs
if nothing there perhaps you can add a link to *.0.2 in the host file?
clear the dns cache etc via ipconfig in a command prompt
Firefox proxy settings, set something else, close ff, open it again then revert to no proxy
Disable the FF safebrowsing thing (forgot the name and can’t currently check)
Disable FF secure dns features, don’t let firefox choose one nor set a custom one, just put it on isp provided only <- also, use this one in windows tcp/ip settings, not a google one etc.
is the subnet mask set correctly? If behind a switch and 2nd network/NAT
make a new empty FF profile and try the adress from there
I once had a similar issue (but not fully the same), alas I forgot how I fixed it.
Some suggestions:
Percussive maintenance? ;-)
Hope you get it resolved.