This means that nobody was listening on that port number. Check the
port numbers match between server and client. Make sure you specify
the port number explicitly in the document address for
www
.
If you are running the daemon standalone (as you should be), check
that it is actually running by taking a list of processes, and that it
is listening to the correct port (specified with -p
port option), or try running it from the terminal with
-v
option as well. The trace for the server should say
"socket, bind and listen all ok".
If it does, and you
still get "connection refused
", then you must be talking
to the wrong host (or, conceivably, different ethernet adapters on the
same host).
If you are running with the inet daemon, then check both the services
file (/etc/services)
or database (yellow pages, netinfo)
if your system uses it, and the /etc/inetd.conf
file.
Check the service name matches between these two (e.g.
http
).
Did you remember to kill -HUP the inet daemon when you changed the inted.conf file?
Be aware that on some systems your local file
/etc/services
will not be consulted E.g. when
ypbind
is running on Suns, then you should type
ypwhich -m servicesand ask the administrator of the machine named to change its own
/etc/services
. Try running the deamon from a shell window to see better what happens.