Running FC4.I have a good interface for config. the swat in web browser like localhost:901.For system admin we have localhost:1000 by the webmin daemon.

similarly i want to know all the services that are config by a browser it self either locally or remotely.I mean what are all the options should my system provides for config like :901,:1000,:641.

I need all the configurable services details above i mentioned.

Thanks

It "sounds" like you would like to know what ports are open for http traffic?

If someone is running icecast (a streaming media server) you can go to http://localhost:8000 ... or http://localhost:8001 to see the stats of the server.

Cups uses http://localhost:631


-- Tony

There are many applications that use different ports on the localhost interface (which is only known/accessible on the machine itself and has the fixed IP address 127.0.0.1).

Listing them all would be a daunting task, I think. Some apps, like webservers, even come with configurable ports. And there always is a thingy called "port forwarding" that allows you to map one port to another.
So, your answer isn't as straight-forward as you might expect.

You could try a utility like "nmap" to find out all open ports on your system, but that's probably not what you are looking for.

So, can you please tell me why you need the port numbers? Maybe we can help you in finding an alternate solution to your problem.

here is my system open ports found using nmap.I do not know how to use those ports effectively.


7/tcp open echo
9/tcp open discard
13/tcp open daytime
19/tcp open chargen
21/tcp open ftp
22/tcp open ssh
23/tcp open telnet
25/tcp open smtp
37/tcp open time
79/tcp open finger
111/tcp open rpcbind
512/tcp open exec
513/tcp open login
514/tcp open shell
515/tcp open printer
540/tcp open uucp
587/tcp open submission
665/tcp open unknown
4045/tcp open lockd
4045/tcp open lockd
6002/tcp open X11:1
6003/tcp open X11:2
6017/tcp open xmail-ctrl
6050/tcp open arcserve
6112/tcp open dtspc

http://localhost:anyport is not working.

What do you mean by
On each open port, there is a program listening to requests. Such a program is often called a daemon or a service.
Most of the standard services are harmless, but opening a port, for instance to the internet, that means that the server that is listening on that port can be "attacked". So, for system security, you should only open the ports you are actually going to use.

For instance, your ports 21 and 22, respectively used by the FTP service and the Ssh service, can be attacked from outside (if your those servers contain bugs/security holes).
If you don't really use either of them, then you should make sure that the port is closed.

The bottom line is, you need to know what kind of network services (like web service, ftp service, etc) you want to have hosted by your system. For instance, if you were installing a web server, then you'll need to keep port 80 (http) open. Other ports, should then be closed as much as possible. But if you want to login on that web server using ssh to update your websites, then you'll need to open up port 22 too. And so on...

Another rule sais that any ports with numbers <1024 are "privileged". These ports may only be used by a certain service (for instance, port 80 is always for web servers/HTTP protocol) and only "root" is allowed to allocate the ports. So if you have a server that needs to listen to those ports, it'll need to run under the "root" user, at least until it has allocated the port. After that, most contemporary servers switch to a different, non-root user for security.
Any ports > 1024 are most likely opened by packages you've installed yourself. For instance, if you install a MySql database, it'll create a daemon program, mysqld, that listens to a port somewhere between 3000 and 4000 (I forgot which port exactly). But any program can allocate ports > 1024.

I'll quickly run over the list that you've provided and show you a few examples of the servers that may be running. But then again, I'm no network expert.

21/tcp open ftp - FTP daemon is running, ie vsftpd, wuftpd
22/tcp open ssh - SSH daemon is running, sshd or Open SSH
23/tcp open telnet - telnet daemon is running. This should be avoided, as telnet is insecure. You should rely on ssh for secure remote logins instead.
25/tcp open smtp - A mail server, like sendmail or postfix, is running.

79/tcp open finger - Some people disable this one, too. I'm not sure why.
111/tcp open rpcbind - This is for Remote Procedure Calls (RPC)

513/tcp open login - Keep this one open for logins.
514/tcp open shell
515/tcp open printer - Printer service
540/tcp open uucp - I believe UUCP has something to do with News feeds, but I'm unsure.
6002/tcp open X11:1 - X11 is for your graphical environment. Keep it open.
6003/tcp open X11:2
6017/tcp open xmail-ctrl - can be dangerous, not sure though.
6050/tcp open arcserve - Probably some program like Arc Server (GIS) or something.
6112/tcp open dtspc - ??

Of course it won't work, unless "anyport" is an alias for some number. URLs are always formed like this:
proto://host[.domain]ortnumber
where
proto = network protocol to use, ie HTTP, FTP, ...
host = name of the host
[.domain] = optional domain of the host (only required if it's not the domain that your host belongs to)
portnumber = numerical port number, ie 80 for the HTTP port. Web browsers assume ":80" at the end if you didn't supply a port number.