Use the Line Mode Browser as a test tool. Type
www http://myhost.domain/What happens?
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
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
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
If you are running with the inet daemon, then check both the services
(/etc/services) or database (yellow pages, netinfo)
if your system uses it, and the
Check the service name matches between these two (e.g.
Did you remember to kill -HUP the
inetd when you changed
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
Try running the deamon from a shell window to see better what happens.
There is more information you can get. Use the "verbose" option on the LineMode browser to find out what went wrong:
www -v http://myhost.domain:80/What do you get? A load of trace messages. There are several cases.
/etc/hostsfile, or quoting the IP number of the host in decimal notation (like 220.127.116.11) instead.
Connection refusedstatus back.
root,it will automatically switch it to
nobodyjust before serving the document. This can be changed with the
inetd has started a process to run your server but it
immediately failed. Possibilities include:
inetd, the daemon may not be in the file specified, or may not be executable by the specified user (or, if a user id is not specified in your variety of
email@example.com. Try running the daemon from a terminal window to see what happens.
/etc/httpd.conf) if you have one. Think out way the document name will be mapped successively by each line, and what the result will be.
These are some ideas:
www -source http://my.host.domain/
> telnet my.host.domain 80 Connected to my.host.domain on port 80 Escape is ^[ GET /document/name