NT4WS & Netware client32

[Gérard Leymarie]

What are the difference between head code and "normal" code

Gerard





Aaron Rainwater <aar at cypress.com> on 08/12/99 01:11:40 AM

Please respond to aar at cypress.com
To:   Multiple recipients of list SAMBA-NTDOM <samba-ntdom
cc:    (bcc: Gérard Leymarie)
Subject:  Re: NT4WS & Netware client32


-------------- next part --------------

I encountered similar behavior (winlogon.exe crashed and gave me
BSOD) from Win95 machines (both A & B) until I started using the
head code, instead of 2.0.4b.  I don't know if that would fix
your problem, and somebody with much more to offer will probably
give you a better solution.  I'm just sharing my own experience.

Gerard LEYMARIE wrote:
>
> All,
> I'm using samba as a PDC for 4 months, no problems. (thanks samba team)
> Now, the samba version is 2.0.5a on slackware 3.5
> 20 Clients under NT4WS + SP5, all in french
>
> I must integrate a novell 3.12 server onto the network.
> this server run financial applications.
>
> So I installed Intranetware client 32 4.11a, and when I log on samba
> Winlogon.exe crash and I got the Blue screen of death.
>
> Since this installation, on the computer log, I Have the following error
> (previously no errors, everything find)
>
> [1999/08/11 22:11:04, 0] rpc_parse/parse_prs.c:prs_grow(126)
>   prs_grow: Buffer overflow - unable to expand buffer by 2 bytes.
>
> [1999/08/11 22:11:04, 0] rpc_parse/parse_prs.c:prs_grow(126)
>   prs_grow: Buffer overflow - unable to expand buffer by 2 bytes.
>
> [1999/08/11 22:13:51, 0] lib/util_sock.c:read_socket_data(507)
>   read_socket_data: recv failure for 4. Error = Connection reset by peer
>
> [1999/08/11 22:14:31, 0] rpc_parse/parse_prs.c:prs_grow(126)
>   prs_grow: Buffer overflow - unable to expand buffer by 2 bytes.
>
> [1999/08/11 22:14:31, 0] rpc_parse/parse_prs.c:prs_grow(126)
>   prs_grow: Buffer overflow - unable to expand buffer by 2 bytes.
>
> [1999/08/11 22:39:03, 0] lib/util_sock.c:read_socket_data(507)
>   read_socket_data: recv failure for 4. Error = No route to host
>
> Please, can you help me.
>
> Many thanks, gerard

--
Aaron Rainwater
CADC Intern