Sponsored Content
Operating Systems Solaris Open port in Solaris 8 (not accessible from outside) Post 302358253 by Acapulco on Thursday 1st of October 2009 08:28:46 PM
Old 10-01-2009
Hey pupp, thanks for responding!

Uhmm..you see, the problem is...I'm everything...sysadmin, netadmin aaaand....dba.... I know...but we have to get by as it is.

This being said, I have no idea how/why is the port blocked and how to unblock it, so if you have any pointers on where to start looking, it would be of great help. Also, I know some ports are open, and what I did was move my tomcat server to listen to the port 80 and it's working now, but I can't let it stay there.

Could you point me in the right direction please? I checked the inetd.conf, the /etc/services and as far as I know there's no firewall, at least none that I know of.

Where can I start to sort this out?

Thanks again!
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 8 to many open port

hi all, My OS is solaris 8 with core system installation only. so far everything works fine. by i do some testing from my xp pc as client to nmap and scan opening port to my solaris. the result as below: Initiating SYN Stealth Scan against 10.10.10.10 at 16:25 Discovered open port 21/tcp on... (3 Replies)
Discussion started by: hezry79
3 Replies

2. Linux

open port

How can I open a port on linux machine ??? (5 Replies)
Discussion started by: mm00123
5 Replies

3. IP Networking

Unknown open port: "6881/tcp open bittorrent-tracker" found with nmap

Hi. I ran nmap on my server, and I get the following: Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT Interesting ports on -------- (-----): Not shown: 997 closed ports PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 6881/tcp open bittorrent-tracker The... (0 Replies)
Discussion started by: Rledley
0 Replies

4. Solaris

Unable to open 3966 port in solaris

Unable to open 3966 port for buildforge in Solaris 10, anyone pls help me how to open the 3966 port in solaris. Thanks in Advance (1 Reply)
Discussion started by: durgaprasadr13
1 Replies

5. Solaris

Open port on Solaris 10

Hi All, I am installing Infosphere (ETL tool) on solaris 10. One of the requirement is to open multiple ports for different apps that will be installed. I ran netstat -n | grep 9080 (,etc) but that did not return anything. I have attached the requirement. Can anyone guide me about how to... (3 Replies)
Discussion started by: sumeet
3 Replies

6. Solaris

Is it possible to install Solaris softwares on Open Solaris or Open Indiana?

Hi there, I'm sorry in advance if my question seems stupid, but I can't figure out myself. I was wondering. Is it possible to install a Solaris program on an Open Solaris or Open Indiana operating system? After searching the web for a long time, it seems that Open Solaris was released by... (7 Replies)
Discussion started by: firstpost
7 Replies

7. IP Networking

Tcp ip port open but no such process (merged: Release A Port)

i want to kill a tcp connection by killing its pid with netstat -an i got the tcp ip connection on port 5914 but when i type ps -a or ps-e there is not such process running on port 5914 is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies

8. HP-UX

How to open 443 port in HP-UX?

Hello Experts, I want to open the port 443 on my HP-UX system. can you please help ? Thanks in advance. (1 Reply)
Discussion started by: purushottamaher
1 Replies

9. Solaris

Solaris 10: How to just open a port - nothing else

Hi there, I tried just open a port but I failed ;-( # telnet localhost 9876 That should work so I did ... # vi /etc/services myport 9876/tcp # my port # svcadm restart inetd -> New pid, see ps - ef | grep inet # netstat -an | grep 9876 No port 9876 is waiting ;( #... (4 Replies)
Discussion started by: System
4 Replies
svnserve(8)						      System Manager's Manual						       svnserve(8)

NAME
svnserve - Server for the 'svn' repository access method SYNOPSIS
svnserve [options] DESCRIPTION
svnserve allows access to Subversion repositories using the svn network protocol. It can both run as a standalone server process, or it can run out of inetd. You must choose a mode of operation when you start svnserve. The following options are recognized: -d, --daemon Causes svnserve to run in daemon mode. svnserve backgrounds itself and accepts and serves TCP/IP connections on the svn port (3690, by default). --listen-port=port Causes svnserve to listen on port when run in daemon mode. --listen-host=host Causes svnserve to listen on the interface specified by host, which may be either a hostname or an IP address. --foreground When used together with -d, this option causes svnserve to stay in the foreground. This option is mainly useful for debugging. -i, --inetd Causes svnserve to use the stdin/stdout file descriptors, as is appropriate for a daemon running out of inetd. -h, --help Displays a usage summary and exits. --version Print svnserve's version and the repository filesystem back-end(s) a particular svnserve supports. -r root, --root=root Sets the virtual root for repositories served by svnserve. The pathname in URLs provided by the client will be interpreted relative to this root, and will not be allowed to escape this root. -R --read-only Force all write operations through this svnserve instance to be forbidden, overriding all other access policy configuration. Do not use this option to set general repository access policy - that is what the conf/svnserve.conf repository configuration file is for. This option should be used only to restrict access via a certain method of invoking svnserve - for example, to allow write access via SSH, but not via a svnserve daemon, or to create a restricted SSH key which is only capable of read access. -t, --tunnel Causes svnserve to run in tunnel mode, which is just like the inetd mode of operation (serve one connection over stdin/stdout) except that the connection is considered to be pre-authenticated with the username of the current uid. This flag is selected by the client when running over a tunnel agent. --tunnel-user=username When combined with --tunnel, overrides the pre-authenticated username with the supplied username. This is useful in combination with the ssh authorized_key file's "command" directive to allow a single system account to be used by multiple committers, each having a distinct ssh identity. -T, --threads When running in daemon mode, causes svnserve to spawn a thread instead of a process for each connection. The svnserve process still backgrounds itself at startup time. --config-file=filename When specified, svnserve reads filename once at program startup and caches the svnserve configuration and any passwords and authoriza- tion configuration referenced from filename. svnserve will not read any per-repository conf/svnserve.conf files when this option is used. See the svnserve.conf(5) man page for details of the file format for this option. --pid-file=filename When specified, svnserve will write its process ID to filename. -X, --listen-once Causes svnserve to accept one connection on the svn port, serve it, and exit. This option is mainly useful for debugging. Unless the --config-file option was specified on the command line, once the client has selected a repository by transmitting its URL, svnserve reads a file named conf/svnserve.conf in the repository directory to determine repository-specific settings such as what authenti- cation database to use and what authorization policies to apply. See the svnserve.conf(5) man page for details of that file format. SEE ALSO
svnserve.conf(5) svnserve(8)
All times are GMT -4. The time now is 06:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy