10-03-2010
Sounds like a network problem then.
The busintr shouldn't make any difference.
I would suspect the problem network is not enabled for large send.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wrote a script to test many systems to see if they are up or not. if a system is down, i am notified by email
now, most of the time,when systems are down in my enviroment, it is because the user accidentally or purposely (not knowing the consequences) hit the power button. so these problems... (3 Replies)
Discussion started by: TRUEST
3 Replies
2. Shell Programming and Scripting
Hi all,
I'm trying to write a shell script that will ping a site and and write the date and 1 or 0 (for success or no success) to a file.
it looks roughly like this:
#/bin/sh
set mydate = `date`
set myvar = `ping -c 1 hostname | grep -c "100%"`
if ($myvar == 1) then
echo... (1 Reply)
Discussion started by: TylerDurden
1 Replies
3. UNIX for Dummies Questions & Answers
I can ping by ip address but not by host name
everything is on the same subnet
check all of the normal files
I can telnet in to the unix box but can not open a connect to
the share dir.
unix ver sunSO 5.9
all the other computers ar Windows XP (with firewall turn off)
Thanks... (1 Reply)
Discussion started by: vviscomi
1 Replies
4. UNIX for Dummies Questions & Answers
I want to access window file system through Samba. when i ping Window machine through linux machine it connect, but in reverse case it shows "Request time out". could any one suggest what problem may be. (1 Reply)
Discussion started by: sonirajesh
1 Replies
5. IP Networking
Comp1=192.168.100.2
Comp2=192.168.100.6
both the comp have win2000 Os.
Using Cross cable i have connected back to Back.
When i ping From Comp1 to Comp2 its working fine.
But
When i ping From Comp2 to Comp1 its not working.
I know don't know what went wrong please help me out.... (4 Replies)
Discussion started by: ashokmeti
4 Replies
6. Solaris
Can someone tell me how I can get the following bolded output without having to issue the control C key when a ping is running?
ping -s cca-wl6
PING cca-wl6: 56 data bytes
64 bytes from cca-wl6: icmp_seq=0. time=0.796 ms
64 bytes from cca-wl6: icmp_seq=1. time=0.581 ms
64 bytes from... (5 Replies)
Discussion started by: SkySmart
5 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a list of 500 IP address and need to ping all the IP address. I had written a script to do this and its working if the IP is valid one. If any invalid IP present, the process got hang up.
Also I have tried with -c , -I and -w options, its not working.
Any one help me on this... (2 Replies)
Discussion started by: Rksiva
2 Replies
8. Solaris
Hi friends,
I am running Solaris 10, which is connected to a DSL router running DHCP. During the installation I chose not to use DHCP and assigned a permanent IP address to solaris machine. I also did not choose any name service as well. The rest of the details are as under.
Solaris Machine
IP... (4 Replies)
Discussion started by: gabam
4 Replies
9. HP-UX
I am having a problem with a new server build that has got me completely baffled. This server has a private back end network so the way it is supposed to work is that the server thinks its ip address is 10.131.0.48 but the rest of the world knows it as 199.68.100.100 per DNS. It has to be this way... (2 Replies)
Discussion started by: keelba
2 Replies
10. Shell Programming and Scripting
How can I get the following result of the "ping" command?
Example:
root@OpenWrt:~# ping google.com -c1 | sed -n 1p
PING google.com (216.58.210.14): 56 data bytes
How can I get the data only in the range of ()?
The result of what I want to get it:
216.58.210.14
Please use code... (4 Replies)
Discussion started by: andrewxxx
4 Replies
LEARN ABOUT OSF1
niffconfig
niffconfig(8) System Manager's Manual niffconfig(8)
NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF)
SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...]
OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options.
Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there
is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If
num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic
monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t
option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this
option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already
being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame-
ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the
specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor
thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num
is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout).
Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout).
DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters
that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter-
faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command.
Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified.
EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to
declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being
monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0
SEE ALSO
Daemons: niffd(8)
Information: EVM(5), nifftmt(7)
niffconfig(8)