Re: help Novell...

Willem Scholten (willem@futureinfo.com)
Fri, 30 Sep 1994 16:45:41 -0400


There is yet another method to make this all work also, take scenario B:
but change to:

b- start the PC
> call lsl.com
> call 3c509
> call ipxodi
add odipkt -> generic paket driver using LSL and ODI
> call netx
> call tcpip -> ellimenate this
add: winpkt
> call win
> click on WS-ftp
> it works !!!!!
> click on Cu-Seeme

This scenario works with success for me.

odipkt -> is available on the net, and was written I believe by Harvard.

-Willem.

On Fri, 30 Sep 1994 HEBERTO@MEAKINS.Lan.McGill.CA wrote:

> Hi I have a problem with Novell. I have a 386 pc with w3.1 + w32s and
> a 3c509 thin ethernet card, Winsock Trumpet 1.0b
> Consider the following scenarios:
>
> a- start the PC
> call 3c509
> call winpkt
> call win
> click on Cu-Seeme
> it works !!!!!
> click on WS-ftp
> it works !!!!!
>
> b- start the PC
> call lsl.com
> call 3c509
> call ipxodi
> call netx
> call tcpip
> call win
> click on WS-ftp
> it works !!!!!
> click on Cu-Seeme
> 1- Gethostname() failed (11004)
> 2- error binding to UDP port (10048)
>
> it is not always the same, sometimes it is 1 and sometimes it is
> 2
> I tried cleaning both Autoexec.bat and Config.sys of extra
> stuff and the errors are the same.
> Unfortunately I need to connect to the Novell server.
> Any help will be appreciated.
>
> heberto@meakins.lan.mcgill.ca
>
>