Search results

  1. W

    ssh won't connect to hostname

    My OSX box was set to use a DNS cache that I was testing. The IP for dnscache (from the djbdns package) did not have reverse/forward info. I discovered this by trying to run nslookup. When you run nslookup, it attempts to find the name of the server it's using, before it actually does any...
  2. W

    ssh won't connect to hostname

    I ran tcpdump on the osx box. - 'ping www': looks up the hostname and pings the right IP address - 'ssh www': ZERO network activity as reported by tcpdump; ssh reports connection refused - 'ssh ip.add.re.ss': connects up just fine I'm quite confused. Sure looks like ssh is broken...
  3. W

    ssh won't connect to hostname

    No, the hostname has only one IP. The machine itself has dozens of IPs and hundreds of names. I can use "uncorrupted" names without issue, and IPs seem to be working thus far. The telnet to port 22 works just fine. Doing some more digging... it would appear the lookup is failing from within...
  4. W

    ssh won't connect to hostname

    OSX 10.1 FreeBSD 4.3 and 4.4 From the OSX box I was able to ssh to the FreeBSD boxen. I did some stuff unrelated to ssh (moved a web dir), logged out, and then later tried to log back in. All I get is this: [osx:~] user% ssh -v -v -v jon@www OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL...
Back
Top