03-18-2009
Dear Edfair,
I changed the NIC. also the same problem. we are using 3com 3c90b cards which is automatically detected by Unix. we have another server which is doing the same thing. When you lost the network you have to restart the server.
thanks
10 More Discussions You Might Find Interesting
1. SCO
Happy new year guys.
I have a inspiron 5100 laptop "Dell"
When i'm trying to install SCO openserver 5.0.7 i get this error right after it goes thru the hardware bootup stage.
The error is (PANIC: wdsetparam: no device info for ctlr 1 drive 0
is ctlr 0 , drive 0 not... (0 Replies)
Discussion started by: josramon
0 Replies
2. 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
3. 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
4. SCO
I have several printers setup but nothing prints.
I get the following error email
Subject: Status of lp request aclj3-2297
Your request aclj3-2297 destined for aclj3
encountered an error while printing on printer aclj3.
Reason for failure:
cat: cannot open 0: No such file or... (1 Reply)
Discussion started by: Jessie Nand
1 Replies
5. Post Here to Contact Site Administrators and Moderators
I am installing a HP printer using ./hpnpcfg and I am getting the following:
Please enter selection: 5
Enter the network peripheral name or IP address: hpndlife
The following types of test files can be sent to the printer:
1) text file
... (0 Replies)
Discussion started by: Likando Luywa
0 Replies
6. 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
7. UNIX for Dummies Questions & Answers
Hi,
I've got a really old system we use for call logging. The OS is SCO 3.2
uname -a output
SCO_SV bts7053 3.2 2 i386
the problem we are having is that its no longer doing its backups. The original problem was the tape drive, which has been replaced twice now. Because the company are... (1 Reply)
Discussion started by: johno12345
1 Replies
8. 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
9. 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
10. Shell Programming and Scripting
Hi,
I work on several Sun servers running Solaris (SunOS 5.10). All of these are Application Servers with a propietary software running on it.
It happens that some times (not regularly/deterministic and not so often, i.e. twice a month circa) we register what I think are network problems.
I say... (4 Replies)
Discussion started by: Evan
4 Replies
LEARN ABOUT OPENDARWIN
tcp
TCP(4) BSD Kernel Interfaces Manual TCP(4)
NAME
tcp -- Internet Transmission Control Protocol
SYNOPSIS
#include <sys/socket.h>
#include <netinet/in.h>
int
socket(AF_INET, SOCK_STREAM, 0);
DESCRIPTION
The TCP protocol provides reliable, flow-controlled, two-way transmission of data. It is a byte-stream protocol used to support the
SOCK_STREAM abstraction. TCP uses the standard Internet address format and, in addition, provides a per-host collection of ``port
addresses''. Thus, each address is composed of an Internet address specifying the host and network, with a specific TCP port on the host
identifying the peer entity.
Sockets utilizing the tcp protocol are either ``active'' or ``passive''. Active sockets initiate connections to passive sockets. By default
TCP sockets are created active; to create a passive socket the listen(2) system call must be used after binding the socket with the bind(2)
system call. Only passive sockets may use the accept(2) call to accept incoming connections. Only active sockets may use the connect(2)
call to initiate connections.
Passive sockets may ``underspecify'' their location to match incoming connection requests from multiple networks. This technique, termed
``wildcard addressing'', allows a single server to provide service to clients on multiple networks. To create a socket which listens on all
networks, the Internet address INADDR_ANY must be bound. The TCP port may still be specified at this time; if the port is not specified the
system will assign one. Once a connection has been established the socket's address is fixed by the peer entity's location. The address
assigned the socket is the address associated with the network interface through which packets are being transmitted and received. Normally
this address corresponds to the peer entity's network.
TCP supports one socket option which is set with setsockopt(2) and tested with getsockopt(2). Under most circumstances, TCP sends data when
it is presented; when outstanding data has not yet been acknowledged, it gathers small amounts of output to be sent in a single packet once
an acknowledgement is received. For a small number of clients, such as window systems that send a stream of mouse events which receive no
replies, this packetization may cause significant delays. Therefore, TCP provides a boolean option, TCP_NODELAY (from <netinet/tcp.h>, to
defeat this algorithm. The option level for the setsockopt call is the protocol number for TCP, available from getprotobyname(3).
Options at the IP transport level may be used with TCP; see ip(4). Incoming connection requests that are source-routed are noted, and the
reverse source route is used in responding.
DIAGNOSTICS
A socket operation may fail with one of the following errors returned:
[EISCONN] when trying to establish a connection on a socket which already has one;
[ENOBUFS] when the system runs out of memory for an internal data structure;
[ETIMEDOUT] when a connection was dropped due to excessive retransmissions;
[ECONNRESET] when the remote peer forces the connection to be closed;
[ECONNREFUSED] when the remote peer actively refuses connection establishment (usually because no process is listening to the port);
[EADDRINUSE] when an attempt is made to create a socket with a port which has already been allocated;
[EADDRNOTAVAIL] when an attempt is made to create a socket with a network address for which no network interface exists.
SEE ALSO
getsockopt(2), socket(2), intro(4), inet(4), ip(4)
HISTORY
The tcp protocol stack appeared in 4.2BSD.
4.2 Berkeley Distribution June 5, 1993 4.2 Berkeley Distribution