[cvsnt] Re: login problem

[Volker Hohmann]

As AV I use Norton-AV not NOD32.

In between I loaded the sources of cvsnt (Version 2.5.01.1976), to make some tracing of the problem.

I see the following steps:

cvs connects to cvsservice (via 2401). cvsservice accepts the connect.
(If I implement a recv, cvsservice can receive the data from cvs).
cvsservice create a new cvs process. The open_osfhandle of this process fails.
If I set the inherit property in cvsservice (with SetHandleInformation),
open_osfhandle returns no error, but a read from the socket handle returns "invalid handle".

Is that what you mean with "breaks TCP/IP stack" ?

Volker


"Tony Hoyle" <tony.hoyle at march-hare.com> schrieb im Newsbeitrag 
news:dam5vg$tn$1 at paris.nodomain.org...
> Volker Hohmann wrote:
>> Yes, I have both. But if I deactive them, I still have the same problem.
>
> Nod32 breaks the TCP/IP stack... best thing to do with that is to uninstall it (there is 
> apparently a workaround that lets it work but I'm not sure of what it is right now.. disabling 
> some of its checking functions I think).
>
> Also check with cvsdiag do see if something's sitting in your Winsock breaking it (eg. spyware). 
> The basic stack just has:
>
> Installed Winsock protocols:
>
> 1001: MSAFD Irda [IrDA]
> 1002: MSAFD Tcpip [TCP/IP]
> 1003: MSAFD Tcpip [UDP/IP]
> 1005: RSVP UDP Service Provider
> 1006: RSVP TCP Service Provider
>
> Anything else may be suspect (barring MS supported protocols like netware which sometimes appears 
> there).
>
> WinsockXPFix will try to correct any problems & might work for you.. it's best to know what's 
> causing it first though.
>
> Tony