DOS Telnet with Microsoft TCP/IP??

DOS Telnet with Microsoft TCP/IP??

Post by Bryan Cha » Mon, 25 Nov 1996 04:00:00



I have three PCs on my network.  One of them is running Windows 95 with
TCP/IP, another is running Linux with Samba, and the last one can only
run DOS (being a 286).  I have installed the MS LanMan TCP/IP client
from the Microsoft FTP site on the 286, and enabled it to share disks
and printers with the other two.  I would like to know now if there is a
telnet/ftp application that will work in DOS and with the LanMan
client?  Some telnet applications (like NCSA Telnet for DOS) require the
use of a separate packet driver for this purpose.  Is there a way to
make use of the TCP/IP stack (and sockets) in the LanMan client
instead?  Thanks.

Bryan Chan______________________________________________________________


              http://www-ug.eecg.toronto.edu/~chanb/

 
 
 

DOS Telnet with Microsoft TCP/IP??

Post by Con Sultan » Tue, 03 Dec 1996 04:00:00



> I have three PCs on my network.  One of them is running Windows 95 with
> TCP/IP, another is running Linux with Samba, and the last one can only
> run DOS (being a 286).  I have installed the MS LanMan TCP/IP client
> from the Microsoft FTP site on the 286, and enabled it to share disks
> and printers with the other two.  I would like to know now if there is a
> telnet/ftp application that will work in DOS and with the LanMan
> client?  Some telnet applications (like NCSA Telnet for DOS) require the
> use of a separate packet driver for this purpose.  Is there a way to
> make use of the TCP/IP stack (and sockets) in the LanMan client
> instead?  Thanks.

First, you need to load socks.exe, or sockets.exe, or socktsr.exe.  I
don't remember the real name off hand.  It is part of the LanMan
distribution.  That will get the required sockets in memory.  Be
prepared to run out of memory, as it is a large TSR.  Then programs like
Kermit will do the telnet for you.  Look for Kermit on the web.  I think
it is still freeware as long as you do not ask for tech support.

--

Sysop - Home Brew University BBS   Brew City Campus       414-238-9074
Genealogy Search:  Brickner, Kane, Kimbro, LaClaire, Snyder|Snider,
                   Seecs|Seetch|Sich, and Thorton.
  Visit my homepage for more ...          http://www.execpc.com/~jkane

 
 
 

DOS Telnet with Microsoft TCP/IP??

Post by Bryan Cha » Thu, 05 Dec 1996 04:00:00



> First, you need to load socks.exe, or sockets.exe, or socktsr.exe.  I
> don't remember the real name off hand.  It is part of the LanMan
> distribution.  That will get the required sockets in memory.  Be
> prepared to run out of memory, as it is a large TSR.  Then programs like
> Kermit will do the telnet for you.  Look for Kermit on the web.  I think
> it is still freeware as long as you do not ask for tech support.

Thanks to this and many other messages, I have successfully loaded the
MS LanMan client for DOS and the NDIS-to-pktdrv shim DIS_PKT9.DOS
together.  The shim is then supposed to let Kermit work on my MS-DOS
machine.  But I can't get this to work, whether or not I load
sockets.exe.  Kermit (version 3.14) starts fine, and when I type in the
command to telnet to an IP address (a Linux machine) on the LAN, it
actually works for a while, then comes back with:

  Unable to ARP resolve 198.xxx.yyy.zzz
  Unable to contact the host.
  The host may be down or a gateway may be needed.

However, ping shows that the two machines can find each other, and
net-using the Windows shares also works.  What am I doing wrong?

Bryan Chan______________________________________________________________


              http://www-ug.eecg.toronto.edu/~chanb/

 
 
 

DOS Telnet with Microsoft TCP/IP??

Post by Monica Salas Blanc » Thu, 05 Dec 1996 04:00:00



> I have three PCs on my network.  One of them is running Windows 95 with
> TCP/IP, another is running Linux with Samba, and the last one can only
> run DOS (being a 286).  I have installed the MS LanMan TCP/IP client
> from the Microsoft FTP site on the 286, and enabled it to share disks
> and printers with the other two.  I would like to know now if there is a
> telnet/ftp application that will work in DOS and with the LanMan
> client?  Some telnet applications (like NCSA Telnet for DOS) require the
> use of a separate packet driver for this purpose.  Is there a way to
> make use of the TCP/IP stack (and sockets) in the LanMan client
> instead?  Thanks.

        You can use a shim driver. (A shim driver emulates a protocol
over other protocolo). There is a protocol that emulates the
packet driver over a ndis driver (The protocol that uses LanMan).
The file is pdether.zip. Use archie to found it.
> Bryan Chan______________________________________________________________


>               http://www-ug.eecg.toronto.edu/~chanb/

 
 
 

DOS Telnet with Microsoft TCP/IP??

Post by Joe Doupn » Fri, 06 Dec 1996 04:00:00




>> First, you need to load socks.exe, or sockets.exe, or socktsr.exe.  I
>> don't remember the real name off hand.  It is part of the LanMan
>> distribution.  That will get the required sockets in memory.  Be
>> prepared to run out of memory, as it is a large TSR.  Then programs like
>> Kermit will do the telnet for you.  Look for Kermit on the web.  I think
>> it is still freeware as long as you do not ask for tech support.

> Thanks to this and many other messages, I have successfully loaded the
> MS LanMan client for DOS and the NDIS-to-pktdrv shim DIS_PKT9.DOS
> together.  The shim is then supposed to let Kermit work on my MS-DOS
> machine.  But I can't get this to work, whether or not I load
> sockets.exe.  Kermit (version 3.14) starts fine, and when I type in the
> command to telnet to an IP address (a Linux machine) on the LAN, it
> actually works for a while, then comes back with:

>   Unable to ARP resolve 198.xxx.yyy.zzz
>   Unable to contact the host.
>   The host may be down or a gateway may be needed.

> However, ping shows that the two machines can find each other, and
> net-using the Windows shares also works.  What am I doing wrong?

---------
        You are running into two problems: primarily difficulties with
ARP caching in some editions of Linux (it forgets and does not reacquire
information ) and a TCP keepalive problem in MSK v3.14. I can't help with
the Linux part but MSK v3.15 is in open beta testing and should be acquired
from kermit.columbia.edu.
        Joe D.
 
 
 

1. HELP: WfW and DOS-TCP/IP vs. WinSocket-TCP/IP

I'm using a LanManager/X server under a SVR4 UNIX OS.

The clients ar running under WfW.

  - If I use the DOS TCP/IP stack the basic LM/X services are o.k.,
    but I cannot run any programs accessing the WinSocket API.

  - If I use the WinSocket TCP/IP stack from ftp.microsoft.com there
    is a problem calling programs like MS-Office from a shared
    ressource. The first user can link that ressource and call a
    program (Excel); the second user can also link, but calling the
    program he gets the error message, that the file is in use.

Since it is possible for many users to call programs like Excel from
the server, I think the problem is the client configuration (???).

Thanks in advance.


Universitaet Goettingen / Stabsstelle DV             fon: (49) 551 394160
Gosslerstrasse 5/7                                   fax: (49) 551 399612
37073 Goettingen                                     --------------------------

2. just talked to MS about my beta kit

3. MSDOS Telnet for Microsoft TCP/IP Stack

4. Pro/Engineer Support - Boston MA & San Jose CA

5. Changed TCP/IP - Now Can't use telnet, ping, ftp

6. How different is R5 from R4?

7. Telnet for TCP/IP

8. TCP/IP protocol possible in dos??

9. DOS Client very *slow* with TCP/IP

10. TCP/IP Dos/Windows Clients

11. MS/DOS TCP/IP Client

12. How do I run Netbios over TCP/IP on DOS?