oneill#robin%e.mfenet@NMFECC.arpa (07/30/87)
I have a slight problem with an ONYX machine running UNIX system III and
KERMIT. Whenever I attempt to CONNECT, using KERMIT, to another site I
get the following message:
Can't get character: No such file or directory.
[Back at local system]
However, this wasn't always the case. I was once able to issue the
CONNECT command with success. If anyone has run into this before, or
if you can help in any way, please respond to me personally. I am not
a member of your bulletin board. I will post any responses back to the
board. Thank you.
Robin O'Neill
National Magnetic Fusion Energy Computer Center
Lawrence Livermore National Laboratory
oneill@nmfecc.arpafranco@MIKEY.BBN.COM (Frank A. Lonigro) (07/31/87)
Robin:
You may or may not know this about kermit, but I wrote this memo
for our engineers and felt that if you tried using kermit this way that
if you still have a problem then I believe something changed with your
connection to the remote host.
>>>>>NOTE<<<<< Please note that if you are connecting to a
remote computer thru a hard wired tty line the same steps apply except
you set the baud rate to 9600 and you of course skip the modem commands.
The memo follows:
CONNECTION THRU MODEM:
To establish a connection to dial out, you must first be
sure the modem is connect to a non-login port (for Boeing and
Hughes 801, tty03 is a login and tty02 is a non-login, for our
vax, ttyh2 is free to be either a login or a non-login). Once
the modem is connected and turned on, you can connect to it by
typing the following:
kermit -l /dev/tty02 -b 1200 -c /* connect to modem */
This will connect you to the modem connected to
/dev/tty02 at 1200 baud. The "-c" tells kermit to establish an
interactive connection. Once connected, you can talk to the
modem as we have done before, i.e..(at<cr>, atDT1234567<cr> and
so on).
TRANSFERRING FILES:
Once you login to the computer you want to connect to,
you must start up "kermit" in "server' mode. This will set up
the connection to send and receive files back and forth between
the machines. :::NOTE::: Before doing this you will need to be
in the directory where you want to take files from or send files
to. To put kermit in server mode just type:
kermit -x /* start remote kermit in server mode */
After this command you will see some garbage characters
which you should ignore. The next step is to get back to your
local machine. To do so just type:
ctrl-\c /* control backslash and then a lower case "c" */
/* "NOT" control backslash and then control "c" */
Now that you are back to the local machine you can either
take files from or send files to the remote computer.
TAKING FILES:
To take files from the current directory on the remote
machine you can use the standard shell wild cards such as "*",
"?" or "[]" to form file names so multiple files can be taken. A
typical command might be to take all the ".c" and ".h" files.
kermit -l /dev/tty02 -b 1200 -g "*.[ch]"
SENDING FILES:
To send files to the current directory on the remote
machine you can follow the same syntax as taking files. A
typical command might be to send the files you made changes to.
kermit -l /dev/tty02 -b 1200 -s "scndis.c scn.h"
Both taking and sending commands give you statistics on
the files kermit is transferring and tells you when the process
is finished.
CLOSING CONNECTION:
Once you are done transferring files, you must take the
remote kermit out of server mode. You might also want to do this
if you need to re-connect to the remote computer and change
directories or some such command as that. The following command
will stop the remote server.
kermit -l /dev/tty02 -b 1200 -f
Once you do that, you can re-connect to the remote
computer by doing the connection command above and then either
log out or change directories and start the transfer process all
over again or what ever you want, but be sure you eventually log
out of the remote machine.
If you log out from the remote computer, you will once
again be talking to the modem itself, so you will need to enter
the "ctrl-\c" command to finally close the connection thru the
modem.oneill#robin%e.mfenet@nmfecc.arpa (08/13/87)
Robin:
You may or may not know this about kermit, but I wrote this memo
for our engineers and felt that if you tried using kermit this way that
if you still have a problem then I believe something changed with your
connection to the remote host.
>>>>>NOTE<<<<< Please note that if you are connecting to a
remote computer thru a hard wired tty line the same steps apply except
you set the baud rate to 9600 and you of course skip the modem commands.
The memo follows:
CONNECTION THRU MODEM:
To establish a connection to dial out, you must first be
sure the modem is connect to a non-login port (for Boeing and
Hughes 801, tty03 is a login and tty02 is a non-login, for our
vax, ttyh2 is free to be either a login or a non-login). Once
the modem is connected and turned on, you can connect to it by
typing the following:
kermit -l /dev/tty02 -b 1200 -c /* connect to modem */
This will connect you to the modem connected to
/dev/tty02 at 1200 baud. The "-c" tells kermit to establish an
interactive connection. Once connected, you can talk to the
modem as we have done before, i.e..(at<cr>, atDT1234567<cr> and
so on).
TRANSFERRING FILES:
Once you login to the computer you want to connect to,
you must start up "kermit" in "server' mode. This will set up
the connection to send and receive files back and forth between
the machines. :::NOTE::: Before doing this you will need to be
in the directory where you want to take files from or send files
to. To put kermit in server mode just type:
kermit -x /* start remote kermit in server mode */
After this command you will see some garbage characters
which you should ignore. The next step is to get back to your
local machine. To do so just type:
ctrl-\c /* control backslash and then a lower case "c" */
/* "NOT" control backslash and then control "c" */
Now that you are back to the local machine you can either
take files from or send files to the remote computer.
TAKING FILES:
To take files from the current directory on the remote
machine you can use the standard shell wild cards such as "*",
"?" or "[]" to form file names so multiple files can be taken. A
typical command might be to take all the ".c" and ".h" files.
kermit -l /dev/tty02 -b 1200 -g "*.[ch]"
SENDING FILES:
To send files to the current directory on the remote
machine you can follow the same syntax as taking files. A
typical command might be to send the files you made changes to.
kermit -l /dev/tty02 -b 1200 -s "scndis.c scn.h"
Both taking and sending commands give you statistics on
the files kermit is transferring and tells you when the process
is finished.
CLOSING CONNECTION:
Once you are done transferring files, you must take the
remote kermit out of server mode. You might also want to do this
if you need to re-connect to the remote computer and change
directories or some such command as that. The following command
will stop the remote server.
kermit -l /dev/tty02 -b 1200 -f
Once you do that, you can re-connect to the remote
computer by doing the connection command above and then either
log out or change directories and start the transfer process all
over again or what ever you want, but be sure you eventually log
out of the remote machine.
If you log out from the remote computer, you will once
again be talking to the modem itself, so you will need to enter
the "ctrl-\c" command to finally close the connection thru the
modem.oneill#robin%e.mfenet@nmfecc.arpa (08/13/87)
I'd say Kermit isn't finding the name of the tty device you're trying
to connect through. I assume you are using UNIX kermit. If this is indeed the
case, make sure that the device you specify in the "set line" command really
does exist and is world readable and writable. Hope this helps!
Jeff