I think in this context it may be the IP address of the machine trying to access 192.168.1.12. Quite why it should think it is unreadable when it is on the same subnet (assuming you have the typical subnet mask of 255.255.255.0) is not clear - sounds like there may be a networking issue at the host (perhaps a reboot will clear it).