Have any Win2000 users seen these errors? Is there some way to
eliminate them?
Thanks
Geoff
> David Huffman wrote:
>
> Hi Geoff
> Is there a chance you will get around to looking at the socket error I
> get on NT machines.
> It is just very annoying.
> Dave
>
> This is the error message.
> Unexpected UDP failure WIN32 Socket Library Error 10054
>
> This is a reference I found about it.
>
> WSAECONNRESET
> (10054)
> Connection reset by peer.
> An existing connection was forcibly closed by the remote host. This
> normally results if the peer application on the remote host is
> suddenly stopped, the host is rebooted, or the remote host uses a hard
> close (see setsockopt for more information on the SO_LINGER option on
> the remote socket.) This error may also result if a connection was
> broken due to keep-alive activity detecting a failure while one or
> more operations are in progress. Operations that were in progress fail
> with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
- Replies:
- Re: [Fwd: socket errors] matthias muntwiler
- RE: [Fwd: socket errors] Jeff Hill
- Navigate by Date:
- Prev:
RE: Apropos making fields configurable Redman, Russell O.
- Next:
CA connect delays under Windows Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
scaler record: int -> float Tim Mooney
- Next:
Re: [Fwd: socket errors] matthias muntwiler
- Index:
1994
1995
1996
1997
1998
1999
2000
<2001>
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|