Announcement

Collapse
No announcement yet.

DOS Server with MS Network Client

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Gustavo Asplanatti
    replied
    Hi Herman

    I am confused...
    Does lsl work only with odi drivers?
    ODI driver is not just for Novell?
    Am I able to work with ODI drivers in MS Client 3.0?

    I have tried lsl in autoexec.bat... No error, but the PC still lock up.

    I have tried without qemm, same thing...

    Thank four your help...

    Any other idea ??


    ------------------
    Gustavo Asplanatti
    [email protected]

    Leave a comment:


  • Herman Kieskamp
    replied
    Originally posted by Herman Kieskamp:
    Gustavo I miss the LSL in the autoexec.bat, that is a socket layer,
    you need this if you want to bind more than 1 type of networking !
    its lsl.com, that accepts in native mode 4 different layers !

    Also your using Qemm, you to run optimize to make sure no network driver
    is put in the wrong place by qemm !! Make sure it works without qemm first !!
    Qemm can easily cause hangs. After having a good working situation without qemm,
    add qemm, so you know it works, than you can fine tune with qemm !!

    Herman.




    ------------------
    You gotta run, and don't loop back.

    Leave a comment:


  • Herman Kieskamp
    replied
    Gustavo I miss the LSL in the autoexec.bat, that is a socket layer,
    you need this if you want to bind more than 1 type of networking !
    its lsl.com, that accepts in native mode 4 different layers !

    Herman.


    ------------------
    You gotta run, and don't loop back.

    Leave a comment:


  • Gustavo Asplanatti
    replied
    Hi Herman...

    Thank for your reply!

    Well, I will try to explain:

    I need more info, what can you do and what can't you do ?
    I believe that to answer your question, first I should you clarify
    to you what it is what I need to make...

    A - Send data from a PC that a program runs in PB DOS 3.5 to another PC
    (Running Windows 2000/XP) through a LAN, this can make it with the
    TCPABI library, using the NIC packet driver.
    This is the DOS program, just if you wish to snoop!
    http://www.computecsrl.com.ar/cptraf_english/cptraf.htm

    B - To be able to access through that LAN to the files generated by the
    DOS PC and to recover them.

    OK, for the first problem can use the following thing:

    Adding in the AUTOEXEC.BAT File:


    RTSPKT 0x60 << NIC Packet Driver
    SET IP=10.0.0.121
    SET NETMASK=255.255.255.0
    NTCPDRV


    Working well !!!

    For the second point, I use the MS Client 3.0 with the add on
    Server capabilities, with only TCP/IP protocol.
    This also works well. I can access the DOS PC disk and retrieve
    data.

    But, I need to use the two options as a whole!

    So, I have tried to configure the MS Client 3.0 with TCP/IP and the
    packet driver, but here the problems begin.

    The DOS PC freeze when I try to access from other (Windows) PC.

    The following are the main files that I use in this configuration:


    PROTOCOL.INI


    Code:
    [network.setup]
    version=0x3110
    netcard=RTL8139,1,RTL8139,1
    transport=tcpip,TCPIP
    transport=pktdrv,pktdrv
    lana0=RTL8139,1,tcpip
    lana1=RTL8139,1,pktdrv
    
    [TCPIP]
    NBSessions=6
    SubNetMask0=255 255 255 0
    IPAddress0=10 0 0 121
    DisableDHCP=1
    DriverName=TCPIP$
    BINDINGS=RTL8139
    LANABASE=0
    
    [protman]
    DriverName=PROTMAN$
    PRIORITY=MS$NDISHLP
    
    [RTL8139]
    DriverName=rtsnd$
    Medium=_Auto
    
    [pktdrv]
    DriverName=PKTDRV$
    BINDINGS=RTL8139
    INTVEC=0x60
    LANABASE=0

    SYSTEM.INI


    Code:
    [network]
    sizworkbuf=1498
    filesharing=yes
    printsharing=yes
    autologon=yes
    computername=DTC
    lanroot=C:\NET
    username=GUSTAVOA
    workgroup=COMPUTEC
    reconnect=yes
    dospophotkey=N
    lmlogon=0
    logondomain=COMPUTEC
    preferredredir=basic
    autostart=
    maxconnections=8
    
    [network drivers]
    netcard=rtsnd.dos
    transport=dis_pkt9.dos,tcpdrv.dos,nemm.dos
    devdir=C:\NET
    LoadRMDrivers=yes
    
    [Password Lists]
    *Shares=C:\NET\Shares.PWL
    
    [386enh]
    TimerCriticalSection=5000
    UniqueDosPSP=TRUE
    PSPIncrement=2

    AUTOEXEC.BAT


    Code:
    C:\NET\net initialize
    @ECHO OFF
    C:\QEMM\LOADHI /R:2 /LO C:\DOS\SMARTDRV.EXE /X
    PROMPT $p$g
    PATH C:\NET;C:\DOS;C:\NC
    SET TEMP=C:\DOS
    C:\DOS\SHARE.EXE
    C:\NET\netbind.com
    C:\NET\umb.com
    C:\NET\tcptsr.exe
    C:\NET\tinyrfc.exe
    C:\NET\nmtsr.exe
    C:\NET\emsbfr.exe
    C:\NET\net start server
    SET IP=10.0.0.122
    SET NETMASK=255.255.255.0
    NTCPDRV
    Note: I have tried o use the same IP(10.0.0.121).

    Can you ping the pc's ?
    Yes, but the system freeze..

    You must make sure you have good tcp/ip stack, on top of that lays
    the client(windows networking) side. But why using windows networking ?
    Isn't tcp/ip itself good enough ?
    Of course TCP/IP itself is good enough. If I could make both things at
    the same time.

    There is also a trumpet winsocket driver, have you tried that ?
    Yes, I know... But I don't know very well how configuring it.

    Another thing ...
    I have proven to use MS Client 3.0 and Trumpet /packet
    driver with 2 NICs... and all work well, in spite of using more (valuable) memory.
    Of course that I would prefer to use a single NIC.

    Thanks for your time!!!
    If you need adicional information, please let me know...



    ------------------
    Gustavo Asplanatti
    [email protected]

    Leave a comment:


  • Herman Kieskamp
    replied
    I need more info, what can you do and what can't you do ?
    Can you ping the pc's ?
    You must make sure you have good tcp/ip stack, on top of that lays
    the client(windows networking) side. But why using windows networking ?
    Isn't tcp/ip itself good enough ?
    There is also a trumpet winsocket driver, have you tried that ?

    Herman.



    ------------------
    You gotta run, and don't loop back.

    Leave a comment:


  • Gustavo Asplanatti
    replied
    Herman:

    I have installed the wfw311 and the TCP/IP-32, the system works well,
    but I don't have very clear how can I add the trumpet socket driver
    to be able to send data TCP/IP it has more than enough, just as I could
    make with MS Client 3.0.

    Are you able to help me?

    ------------------
    Gustavo Asplanatti
    [email protected]

    Leave a comment:


  • Herman Kieskamp
    replied
    Originally posted by Gustavo Asplanatti:
    Hi Herman....
    Thank for your reply, I am using a Realtek 8139D PCI 10/100...

    In the Realtek site talk about NDIS2 driver for DOS, apparently
    doesn't support NDIS 3... I will try another NIC...

    And ... yes, it is a really old technology, but in my case the
    application that run this PC should be dedicated and without
    interruptions, I don't have another option that to use DOS....

    Thank you....

    So it seems that a pure dos environment only supports Ndis2, But
    what about installing wfw311 ? Realtek have a ndis3 driver win windows
    for workgroups, configurate a working network in wfw, go back to
    Dos and issue "net start" command, this should load all network drivers
    and give you connectable state ! Use the command "net ?" to see what
    options are there ! If you need a wfw driver, give me a mail addrees and I'll send
    it to you.

    Good luck !

    Herman.


    ------------------
    You gotta run, and don't loop back.

    Leave a comment:


  • Gustavo Asplanatti
    replied
    Hi Herman....
    Thank for your reply, I am using a Realtek 8139D PCI 10/100...

    In the Realtek site talk about NDIS2 driver for DOS, apparently
    doesn't support NDIS 3... I will try another NIC...

    And ... yes, it is a really old technology, but in my case the
    application that run this PC should be dedicated and without
    interruptions, I don't have another option that to use DOS....

    Thank you....

    ------------------
    Gustavo Asplanatti
    [email protected]

    Leave a comment:


  • Herman Kieskamp
    replied
    The NIC needs to support at least Ndis 3.0. Most times I found that
    things did not work, were that NDIS 3.0 was not supported by the NIC.

    WOW Trumpetsocket driver thats a long time ago for me, this was my first setup
    for a tcp/ip stack, and my first internetconnection, brings back memories.

    Succes.

    Herman.


    ------------------
    You gotta run, and don't loop back.

    Leave a comment:


  • Gustavo Asplanatti
    started a topic DOS Server with MS Network Client

    DOS Server with MS Network Client

    Hi...

    I am using TCPABI library from Gerhard Zugarek... I send TCP/IP
    data thruogh the packet driver and NTCPDRV (DOS Trumpet ABI)...
    Up to now... No problem... But I need retrieve some files from this
    PC from other PC using MS Network Client 3.0, so I try to configurate
    these two things (MS Network Client & Trumpet over packet driver)...
    But I have not get them to work together. That is to say:

    Network Client XOR Trumpet & Pktdrv

    I follow the instruction write by Gerhard to configurate both things...

    DOS machine with installed Network Client V3.0 for MSDOS or
    MSDOS Workgroup-Add-On V3.11 ; for details see :

    http://ourworld.compuserve.com/homep...g/Dosclnt3.htm
    http://ourworld.compuserve.com/homep...g/Dosservr.htm

    Because MS uses a NDIS Driver for the NIC, you need instead of a Packet Driver
    DIS_PKT.DOS , which can be downloaded from e.g. :

    http://dopey.rediris.es/ftp/pub/msdos/pktdrvr/

    DIS_PKT.DOS is a so called "shim", which provides an Ethernet or a Token Ring
    Packet Driver interface to programs built to operate over Packet Drivers, talks
    to NDIS (3Com/Microsoft) and shares the NIC with NDIS users.

    Copy DIS_PKT9.DOS and NTCPDRV.EXE to e.g. C:\NET .
    Add this to PROTOCOL.INI:

    [pktdrv]
    DriverName=PKTDRV$
    BINDINGS=EP325 <--- NDIS Driver of your NIC (e.g. EP325.DOS)
    INTVEC=0x60

    Add 'dis_pkt9.dos' to the line starting with 'transport=' in SYSTEM.INI

    [network drivers]
    netcard=ep325.dos
    transport=ndishlp.sys,*netbeui,dis_pkt9.dos <--- add here
    devdir=C:\NET
    LoadRMDrivers=yes

    Change the following lines according to your configuration and add them to e.g.
    AUTOEXEC.BAT :

    NET START SERVER <--- includes loading of dis_pkt9 shim
    rem NET STOP <--- shim is still active
    SET IP=169.254.0.16
    SET NETMASK=255.255.0.0
    C:\NET\NTCPDRV

    Somebody that can help me?

    Thanks....



    ------------------
    Gustavo Asplanatti
    [email protected]
Working...
X