| Beth,
WINSOCK error: select() = 10050 is described in the Winsock documentation as
follows:
WSAENETDOWN ENETDOWN 10050
As in BSD. This error may be reported at any time if the Windows Sockets
implementation detects an underlying failure.
This is a low level TCP/IP protocol error, which I'm told that TeamLinks (or any
other application) could not cause (even if it tried). It seems to indicate
network/config problems.
A couple questions.
1. What operating system, and Winsock (Windows 95 with Microsoft's TCP/IP?) are
they using? What TeamLinks version?
2. How many users experience this problem? How frequently? Only with new mail
notification, or do they also occasionally get disconnected in Infoman?
3. When the new mail notification error occurs, can they immediately restart it
and have it working again (get notifications)?
Since this error is occurring in Winsock I'm not particularly optimistic about
being much help with this. I don't know how to pinpoint whatever the "underlying
failure" that Winsock is detecting is.
John
|
| John,
Below are the answers from the customer.
1. What operating system, and Winsock (Windows 95 with Microsoft's
TCP/IP?) are they using? What TeamLinks version?
**Windows 95 with Microsoft TCP/IP stack
**TeamLinks 2.7
2. How many users experience this problem? How frequently? Only with
new mail notification, or do they also occasionally get disconnected
in Infoman?
**Only one user has reported the problem.
**Happens 2-3 times a day. User reports he almost always
**sees the error on his screen when he arrives in the morning.
**User reports no problems when using INFOMAN, and he uses
**INFOMAN several times throughout the day.
3. When the new mail notification error occurs, can they immediately
restart it and have it working again (get notifications)?
**Yes, user invokes INFOMAN, restarts new mail notification and
**it continues to run properly for a while.
Also, the OA$PC_NOTIFY log has the following error recorded for the
user. However, this error is recorded numerous times for all users
and I think is indicative of a PC that's powered off or not running
New Mail Notification.
26-FEB-1997 08:10:17.68 ************ ************************
Error occurred notifying node SAGARM using transport T with
message: New ALL-IN-1 mail for SAGARM from Rajan %X22C)
%SYSTEM-F-TIMEOUT, device timeout
|
| Beth,
I've included some info on this particular Winsock error. It appears that it
make indicate a hardware problem. Can the user suggestions listed below help
any? Anyone out there with any Winsock knowledge please jump in.
If this is only happening for one user, maybe their PC's network adaptor is
flaky. I can't really do any more than guess at this point.
John
WSAENETDOWN (10050) Network is down.
Berkeley description: A socket operation encountered a dead network.
WinSock description: Same as Berkeley. As you can see from the comprehensive
list of WinSock
functions, this error is the catch-all. When it occurs, it could indicate a
serious failure of your
network system (i.e. the protocol stack that the WinSock DLL runs over).
User suggestions: Check your WinSock, protocol stack, network driver and
network interface
card configuration. Note that this error occurs rarely since a WinSock
implementation cannot
reliably detect hardware problems.
WinSock functions: accept(), bind(), closesocket(), connect(),
gethostbyaddr(), gethostbyname(),
gethostname(), getpeername(), getprotobyname(), getprotobynumber(),
getservbyname(),
getservbyport(), getsockname(), getsockopt(), ioctlsocket(), listen(), recv(),
recvfrom(), select(),
send(), sendto(), setsockopt(), shutdown(), socket(), WSAAsyncGetHostByAddr(),
WSAAsyncGetHostByName(), WSAAsyncGetProtoByName(),
WSAAsyncGetProtoByNumber(), WSAAsyncGetServByName(), WSAAsyncGetServByPort(),
WSAAsyncSelect(), WSACancelAsyncRequest(), WSACancelBlockingCall,
WSACleanup(),
WSASetBlockingHook(), FD_ACCEPT, FD_CLOSE, FD_OOB, FD_READ, FD_WRITE
Additional functions: All functions capable of failing can fail with this
error. A couple functions that
the v1.1 specification missed are WSASetLastError() and
WSAUnhookBlockingHook().
|