Subj : [--- SLIP/PPP FTP ? ---] To : WINSTON SMITH From : CHARLES ANGELICH Date : Sun Sep 03 2000 08:31 am 1230d2b9f52a tcpip Hello Winston - CA>> Generally, if you were to telnet to an FTP port you would be CA>> unable to do a transfer because telnet does not 'shift' into an CA>> FTP protocol (none I've seen so far). WS> Hmm... FTP services have to be on the modem gateway? No, only if you are connected via shell access (as a remote terminal). Access via a PPP account, for instance, requires that you execute the FTP app on your system. WS> I thought everything was TCP/IP. Everything I have mentioned uses TCP/IP but there are other protocol layers (many) used not only to operate the Internet but also for intranet use. WS> I was hoping that I could telnet connect a command channel and WS> telnet connect a data channel and issue commands off of my PC and WS> be in business. Not quite clear on what you refer to but it sounds wrong. It's not that complicated from a user's point of view once the software is configured and working properly. WS> I am still trying to figure out how to make an FTP link from my WS> PC, through the server, through the internet, to the desktop with WS> Synchronet BBS on it. For me when I do this the modem is installed in my PC and I `dialup' my ISP (Internet Service Provider) and login via PPP. The ISP then becomes my `server'. Once I am logged into my ISP the TCP/IP protocol is used between my PC and my server and telnet, FTP, or HTTP (or other) are all using TCP/IP through my installed packet driver (daemon?). The sequence (for me) looks something like this: 1) execute a batch file that calls DIALR to dialup my ISP and by using a script file give my username and password via a PPP login protocol (blind login - no dispaly until a connect or failed attempt to connect). 2) if this PPP login is successful the batch file then automatically loads my EPPPD.EXE packet driver which simulates an ethernet II card and driver to my software and maintains the connection with the ISP via my modem. 3) once EPPPD is loaded and running I drop back to the command line and see the normal DOS prompt. At this point I can chose to either use a telnet terminal app (MSKermit is one of them) or I can execute FTP07 and connect to an FTP server after doing the FTP login sequence of username (email address) and password (for public FTP servers this is "anonymous"). These applications contain code to use the TCP/IP protocol of the internet and now `see' my modem as an ethernet card. 4) When I finish with any of these I am back at the DOS prompt but my EPPPD packet driver (daemon?) maintains my connect to my ISP and I can execute a different app or FTP to a different server and so on and so on until I specifically execute another app that requests a disconnect from my ISP and the EPPPD packet driver can be removed from memory. It seems from your description that you have the ethernet card and appropriate driver installed and only need to tell the FTP or MSKermit app where to `hook' (memory location) to this driver (you won't need to load EPPPD)? If your server is already connected to the Internet then you only need the URL to the BBS FTP server to connect with it. WS> I figured with soon to be Internet only BBSes, that I better find WS> a TCP/IP/FTP capable program to add as an adjunct to my terminal WS> program. Yes, I agree with your logic on that one. That was the reason I located the proper apps and set them up here. To maintain connection to BBS and to FIDO. What you want to do is doable but in a slightly different way than what I do here. I must call my ISP via modem then use a packet driver to simulate the ethernet card. > > , , > o/ Charles.Angelich \o , > <| AngelFirecom |> __o/ > / > USA, MI < \ __\__ --- * ATP/16bit 2.31 * .... Composed for you - on an 6/12mhz `286 with 1meg using DOS 16bit telnet. * Origin: Eastpointe Amiga (1:120/228) .