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. On the 192.168.1.102 machine, and similarly with the other address on the other machine. On almost all networking systems, localhost uses the IP address 127.0.0.1. Do NOT comment out the 127.0.0.1 localhost line, nor modify it - leave it as is. The IP address for localhost is 127.0.0.1. 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). 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. And a lot of other packages comes configured this way. 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. macOS Sierra times are much higher than that. On a previous version of OS X it took about 40-50 seconds to finish. And when there is no IP address in the directory services configuration, trying to resolve the name then goes to mDNSResponder which asks DNS.Not sure if that is a smart thing to do. I seem to have a problem with performance of 'sbt test' (which includes looking up localhost names/IP addresses) after upgrading to macOS Sierra. Somehow, the directory services record was out of sync with the /etc/hosts file. PING localhost (127.0.0.1): 56 data bytesĦ4 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.083 msĦ4 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.140 ms Im working on a Mac OS Catalina and have problems when a client is configured to localhost I believe that its only trying to reconcile to only the IPV6 address and not IPV4. append /Hosts/localhost IPAddress 127.0.0.1 Ping: cannot resolve localhost: Unknown hostīash-3.2# dscl. That's cool, but I still don't understand why the /etc/hosts entry isn't working.Įdit: Solved. Go to VirtualBox Preferences -> Network -> Host-only Networks -> click the '+' icon. Appending a trailing dot is meant to bypass searching for the name "localhost" in other search domains. To enable this on OSX I had to do the following: Shut your virtual machine down. I've discovered that "ping localhost." works. if your website is running locally on localhost:3000 and your ip address is 154.31.92.0 then from your phone you can get the website simply by typing 154.31.92.0:3000 into a browser. Must be some setting I've changes somewhere, but I don't know where. So basically with the IP, you can get into any open ports on your local mac e.g. Note that these tunnels are not necessarily specific to ssh/shell traffic. They make it easy to redirect a port on the local machine to the IP address and port of a remote machine. This page says that your index. Instead, look at the -L and -R options in ssh(1). You need to see the following from the image below. I just set up a new mac laptop and it was working until I migrated from my old one. Open the Safari and go to localhost address.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |