02-04-2011
No - the reverse. The network is not the problem. The application loses data because it cannot handle the traffic.
If your network guy knows what he/she is doing, the likelihood of your applications being at fault is pretty good.
Your goal should be: correlate times of network data with good performance and bad performance.
9 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hello guys , i have a big big problem.
At the company that i work for there are like 4 pcs that are sending and recieving a lot of packets to the point that the network is down.
we think that it might be a virus, we run all the antivirus that you could posible think of and nothing so far.
... (2 Replies)
Discussion started by: josramon
2 Replies
2. SuSE
Hullo everyone,
I have recently installed SUSE 9.1 and attached it to my Network router (Actiontec 54Mbps Wireless DSL Gateway) but can't connect to the internet. It comes up with the following error message:
An error occurred while loading "http://www.yahoo.com":Timeout on server - connection... (2 Replies)
Discussion started by: sybella1
2 Replies
3. Slackware
I recently installed slackware 11 and have been very happy with it until I found out that some gnome related apps can cause gnome's network manager to alter the rc.init1 script by adding 3 lines to the script containing only the command, eth_up. This causes the script not to run properly and not... (1 Reply)
Discussion started by: djtrippin
1 Replies
4. Solaris
Hey. i have a SPARCstation 5 running solaris 8 and CDE,
i know this hardware is really old but its the only Solaris machine i can afford at this time, (Student) but im having a hard time getting it on the internet, im using a cable modem, andt DHCP IPv4, but i can`t get a connection, i have heard... (0 Replies)
Discussion started by: mads-nielsen
0 Replies
5. Solaris
Hi
I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1).
But when I try to install using
# boot net -s
I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies
6. Solaris
recently I've setup a Solaris 10 box & am having network disruption, e.g. disconnects, interrupted pings, etc) when I
connect to it from another machine, how should I troubleshoot this !
The machine is a x86 box with 3 NICs (Differnet providors). The Current NIC is a Intel Gigabit, which is... (4 Replies)
Discussion started by: stevie_velvet
4 Replies
7. SCO
SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that.
thanks (8 Replies)
Discussion started by: ajantha
8 Replies
8. SCO
hello, i am new to unix and need support</SPAN></SPAN>
</SPAN></SPAN>The problem is:
I have a SCO 5.0.5 server, and has no local network access, I think my problem are the drivers for network card.
my network card is Kingston EtheRx PCI Fast Ethernet Adapter KNE120TX and already installed the... (9 Replies)
Discussion started by: daniel_cie
9 Replies
9. UNIX for Advanced & Expert Users
i need help, i will always accord mine if my scope allows me, help me in this one..
am running vmware 7.0 in winserver 2008 on a cq61-425el, my network driver is installed correctly. and my vmware network drivers have added as well (in the device manager section).
During installation i wasnt... (0 Replies)
Discussion started by: baitz
0 Replies
LO(4) BSD Kernel Interfaces Manual LO(4)
NAME
lo -- software loopback network interface
SYNOPSIS
pseudo-device
loop
DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication.
As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be
used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured,
as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard-
ware interfaces exist.
DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4), ns(4)
HISTORY
The lo device appeared in 4.2BSD.
BUGS
Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1). Use of that
address is now discouraged; a reserved host address for the local network should be used instead.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution