Sponsored Content
Special Forums IP Networking Help determining what's blocking ports Post 302269339 by Lazydog on Wednesday 17th of December 2008 12:05:02 PM
Old 12-17-2008
OK, do a TRACEROUTE to get the path that the packets are traversing.
Then you will have a path of devices to check.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

determining open ports

hi all 1) how to determine available ports in a box (solaris) do i have to go for a netstat on all the ports? 2) how to block a particular port for a particular type of connection. Any help would be greatly appreciated Thanks (7 Replies)
Discussion started by: matrixmadhan
7 Replies

2. UNIX for Dummies Questions & Answers

Determining file length

How can I determine what UNIX thinks the record size of any given file is?? (1 Reply)
Discussion started by: jbrubaker
1 Replies

3. SCO

Blocking ports and reseting conections

Hi folks! We have SCO Open System V 5.0.5 here. When I type "netstat -n" I found a line mentioning a conection at the port 1025, as follows: tcp 0 0 quartzo.1025 200-203-8-90.csl.aas ESTABLISHED Here we use only conections thru ports 22,23 and 25. I would like to... (0 Replies)
Discussion started by: Marcio Moraes
0 Replies

4. Shell Programming and Scripting

Determining directory path

Hello, I have a script where I get the full directory path of the script being executed: BASE=$0 echo "BASE:" $BASE The output looks like this: BASE: /webapps/appsdev/ACURA/rlz/oses3.sh I'd like to truncate the shell name, leaving just the directory path. The directory path can be... (2 Replies)
Discussion started by: cwalsek
2 Replies

5. Shell Programming and Scripting

Problem determining file

I got the following code, it partially works. Can someone tell me why it partially doenst work? #!/bin/sh file=$1 if then echo "File is a directory" else echo "File is not a directory!" fi heres the output: philip@philip-laptop:~/Desktop$ sh exFive.sh test.java File is... (4 Replies)
Discussion started by: philmetz
4 Replies

6. Solaris

determining miniroot revision

Hi guys I have a bunch of x4100's x4140's etc with solaris 10 update4 running on them but I suspect that when a lot of these boxes were originally built, the jumpstart process used an update2 miniroot, now as far as i understand it, the miniroot used at jumpstart is the miniroot that stays on... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

7. Solaris

Blocking outgoing connection to ports/host in solaris

Hi, I want to block all outgoing connection ( the IMAP ) to my exchnage . I have to do it in my solaris server; from solaris host no outgoing connection can be made to the imap server. Please help me to configure that. I am new in solaris. Kind regards, Akhtar (2 Replies)
Discussion started by: akhtarbd
2 Replies

8. Programming

determining the IP of a function

Is there a way to determine the "Instruction Pointer" of a function in c++, and if so can someone tell me? (5 Replies)
Discussion started by: neur0n
5 Replies

9. UNIX for Dummies Questions & Answers

Determining Disk Speed

Hi, I went to a computer store and the salesman sold me a SATA cable and told me that all SATA cables are the same. Another salesman at a different store told me a cable rated for SATA 2, which I bought, MIGHT work as well as one rate for SATA 3 but it is not guaranteed. I decided to run a... (3 Replies)
Discussion started by: mojoman
3 Replies

10. Programming

Which are blocking and non-blocking api's in sockets in C ?

among the below socket programming api's, please let me know which are blocking and non-blocking. socket accept bind listen write read close (2 Replies)
Discussion started by: VSSajjan
2 Replies
elcsd.conf(5)							File Formats Manual						     elcsd.conf(5)

Name
       elcsd.conf - error logging configuration file

Description
       The  file  contains information used by the daemon to configure error logging for the system.  The system manager maintains this file.  The
       error logging daemon is dependent on the current order of the entries in the file.  Do not change the order.

       The information in the file shows any defaults and describes what you can enter.  A newline is used to delimit each entry in  the  file,  a
       null entry consists of a newline alone, and comments begin with #.
       #
       #    elcsd - errlog configuration file
       #

       {	   # delimiter DON'T remove or comment out!
       1	   # status 1-local,2-logrem,4-remlog,5-remlog+priloglocal
		   # errlog file size limit num. of blocks
       /usr/adm/syserr # errlog dir. path
		   # backup errlog dir. path
       /	   # single user errlog dir. path
       /usr/adm/syserr # log remote hosts errlog dir. path
		   # remote hostname to log to
       }	   # delimiter DON'T remove or comment out!
       #  hosts to log :S - separate file or :R - remotes file (together)
       remote1:S
       remote2:S
       #remote3:S	   # disabled
       remote4:S
	  .
	  .
	  .
       The status line of the file describes where you can log error packets, also called error messages:

	    Logs error packets locally =
		   1, the default.

	    Logs error packets from a remote system or systems to the local machine =
		   2.

	    Logs local and remote error packets locally =
		   3.

	    Logs error packets from the local system to a remote system =
		   4.

	    Logs error packets from the local system remotely and logs high
		   priority messages locally = 5.

       The  errorlog  file  size  defines  the	maximum size of an errorlog file.  If disk space is limited, you can specify the maximum number of
       blocks (512 bytes each) you want the errorlog file to be.  If you do not specify the maximum number of blocks, the system will  notify  you
       when the file system is 98% full.

       The  default  errorlog  directory path is You can direct error packets to a different directory; if you do, you must change the default for
       also. For further information, see

       If the error-logging daemon cannot write to the primary errorlog directory path, it attempts to log to the backup errorlog  directory  path
       automatically.

       The  root  directory  is  the default for the single-user errorlog directory path.  When the system makes the transition to multiuser mode,
       errors logged in single-user mode are transferred to the default errorlog directory path  You  can  direct  single-user	error  packets	to
       another directory.

       To log error packets from a remote system locally, set up an errorlog directory path on the local system.  The default is

       Errorlog  packets  from	remote systems can be logged to separate files or to one file.	S sets up a separate errorlog file for each remote
       system that logs locally.  R logs packets from the corresponding remote system to the file syserr.remotes.  The default is S.

Restrictions
       You must have superuser privileges to change the file.  However, anyone can view the file.

Files
       elcsd daemon messages

See Also
       elcsd(8), eli(8), uerf(8)
       Guide to the Error Logger System

																     elcsd.conf(5)
All times are GMT -4. The time now is 01:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy