10 More Discussions You Might Find Interesting
1. AIX
Hello,
I have two AIX6.1 machines that can communicate with each other through ssh.
The problem is that one of them somehow closes the connection after some time and i don't know the reason of that.
For example today i send through rsync command 7 files from one server to the other. It send... (7 Replies)
Discussion started by: omonoiatis9
7 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I am trying to winscp to RHEL5 server and i am ending up with following error.
Network error:connection timed out
The system is up and running but not able to winscp.
Tried SFTP,SCP and FTP protocols in winscp but none worked.
I can ssh into this server from another server... (3 Replies)
Discussion started by: lramsb4u
3 Replies
3. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
4. Red Hat
hello everyone
i hav LITTLE issue, pending for just last week regarding postfix/sendmail server.
M not able to forward mail to outer domain.
I hav not configured DNS server uptill now, so nvr tried to receive mail from any domain, as i don require that as of now.
Can anybody suggest a... (4 Replies)
Discussion started by: oracle.test2
4 Replies
5. Solaris
I have Ultra 45 Sun solaris box with Solaris 10 installed.
My problem is when i boot the unix box, i got the message:
What does this message meant?
then it does not continue to boot successfully.
Please help. Thanks in advance. (5 Replies)
Discussion started by: etcpasswd
5 Replies
6. Programming
When i put the target IP as 127.0.1.1, the program is working fine, can catch blocked & open ports. But when i try to scan remotely, i get connection timed out! Can you tell me why? :(
Here is my code - Look at between where i put astriks - at the bottom:
#include<iostream>... (3 Replies)
Discussion started by: f.ben.isaac
3 Replies
7. UNIX for Dummies Questions & Answers
Hello,
How can I set up events to be executed at a certain time? And do I need some kind of privilege such as being in cron group? (2 Replies)
Discussion started by: rayne
2 Replies
8. Linux Benchmarks
Hai All,
I have problem during HTTP benchmarking with polygraph tool on EM64T machine.
Benchmarking results are getting problem bcas of connection timed out system errors. Machine log information is as,
/var/log/messages.3:Feb 18 16:17:44 proxy64 network: Bringing up interface eth0: ... (0 Replies)
Discussion started by: muthukumar
0 Replies
9. UNIX for Advanced & Expert Users
We recently installed a new release of SCO UNIX (5.0.6) and when I try to relay e-mail from the UNIX box to my NT server (the mail server) I get the following message from sendmail.
Deferred: Connection timed out with nt
I have nt set up as my relay server in sendmail.cf and the mail seems to... (8 Replies)
Discussion started by: jmossman
8 Replies
10. UNIX for Advanced & Expert Users
I connect to a Sun Box through telnet but it timed out in couple of minutes.
Advance thanks for any idea...help... (2 Replies)
Discussion started by: s_aamir
2 Replies
OWLTTB(1) ICI executables OWLTTB(1)
NAME
owlttb - one-way light time transmission delay simulator
SYNOPSIS
owlttb own_uplink_port# own_downlink_port# dest_uplink_IP_address dest_uplink_port# dest_downlink_IP_address dest_downlink_port# owlt_sec.
[-v]
DESCRIPTION
owlttb delays delivery of data between an NTTI and a NetAcquire box (or two, one for uplink and one for downlink) by a specified length of
time, simulating the signal propagation delay imposed by distance between the nodes.
Its operation is configured by the command-line parameters, except that the delay interval itself may be changed while the program is
running. owlttb offers a command prompt (:), and when a new value of one-way light time is entered at this prompt the new delay interval
takes effect immediately.
own_uplink_port# identifies the port on owlttb accepts the NTTI's TCP connection for uplink traffic (i.e., data destined for the NetAcquire
box).
own_downlink_port# identifies the port on owlttb accepts the NTTI's TCP connection for downlink traffic (i.e., data issued by the
NetAcquire box).
dest_uplink_IP_address is the IP address (a dotted string) identifying the NetAcquire box to which owlttb will transmit uplink traffic.
dest_uplink_port# identifies the TCP port to which owlttb will connect in order to transmit uplink traffic to NetAcquire.
dest_downlink_IP_address is the IP address (a dotted string) identifying the NetAcquire box from which owlttb will receive downlink
traffic.
dest_downlink_port# identifies the TCP port to which owlttb will connect in order to receive downlink traffic from NetAcquire.
owlt specifies the number of seconds to wait before forwarding each received segment of TCP traffic.
The optional -v ("verbose") parameter causes owlttb to print a message whenever it receives, sends, or discards (due to absence of a
connected downlink client) a segment of TCP traffic.
owlttb is designed to run indefinitely. To terminate the program, just use control-C to kill it or enter "q" at the prompt.
EXIT STATUS
0 Nominal termination.
1 Termination due to an error condition, as noted in printed messages.
EXAMPLES
Here is a sample owlttb command:
owlttb 2901 2902 137.7.8.19 10001 137.7.8.19 10002 75
This command indicates that owlttb will accept an uplink traffic connection on port 2901, forwarding the received uplink traffic to port
10001 on the NetAcquire box at 137.7.8.19, and it will accept a downlink traffic connection on port 2902, delivering over that connection
all downlink traffic that it receives from connecting to port 10002 on the NetAcquire box at 137.7.8.19. 75 seconds of delay (simulating a
distance of 75 light seconds) will be imposed on this transmission activity.
FILES
Not applicable.
ENVIRONMENT
No environment variables apply.
DIAGNOSTICS
The following diagnostics may be printed to stdout:
owlttb can't spawn uplink thread
The program terminates.
owlttb can't spawn uplink sender thread
The program terminates.
owlttb can't spawn downlink thread
The program terminates.
owlttb can't spawn downlink receiver thread
The program terminates.
owlttb can't spawn downlink sender thread
The program terminates.
owlttb fgets failed
The program terminates.
owlttb out of memory.
The program terminates.
owlttb lost uplink client.
This is an informational message. The NTTI may reconnect at any time.
owlttb lost downlink client
This is an informational message. The NTTI may reconnect at any time.
owlttb can't open TCP socket to NetAcquire
The program terminates.
owlttb can't connect TCP socket to NetAcquire
The program terminates.
owlttb write() error on socket
The program terminates if it was writing to NetAcquire; otherwise it simply recognizes that the client NTTI has disconnected.
owlttb read() error on socket
The program terminates.
owlttb can't open uplink dialup socket
The program terminates.
owlttb can't initialize uplink dialup socket
The program terminates.
owlttb can't open downlink dialup socket
The program terminates.
owlttb can't initialize downlink dialup socket
The program terminates.
owlttb accept() failed
The program terminates.
BUGS
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>
perl v5.14.2 2012-05-25 OWLTTB(1)