Monday, May 19, 2008

Q: Why does Kali report, "Error: no response from xxx.xxx.xxx.xxx"?

A: Either because the ip# you are trying to attach to is not
running Kali or you don't have Kali configured properly. Try all
of the servers in the list above.

Have you tested your connection yet? Can you ping any or all of
the servers? Have you tried these steps? If not, re-read the
section titled "Testing your TCPIP Setup".


Q: Why can't I ping anything?

A: Good question! This means you are actually trying to test your
connection before using Kali! I'm so happy!

Anyway, this is almost always caused by an incorrect value in
wattcp.cfg. Either your netmask, gateway, or my_ip value is most
likely wrong.

If using a modem, are you sure you connected to your host properly?
Did the host report that SLIP or PPP was started? If using PPP,
did the PPP driver report your ip# (many SLIP hosts will do this
too)? Are you absolutely positive that your modem is configured
for hardware flow control (RTS/CTS) and not software (XON/XOFF)?
For Hayes modems, this is normally done with AT&F2. For USR
modems, try using AT&F1.

PPP users: try using a netmask of 0.0.0.0 and put the line ppp=1 in
wattcp.cfg. Using a netmask of 0.0.0.0 will make the wattcp kernel
think that all nodes are in your local network. It will cause Kali
and other wattcp apps to quit trying to use the gateway. Using
ppp=1 with Kali will cause wattcp to quit trying to resolve
ethernet addresses (which it can't do anyway...but tries).

PPP and SLIP users: if using bootp, try entering your actual ip#
instead.