usenet@cps3xx.UUCP (Usenet file owner) (07/25/89)
Somebody a few posts ago was compliaing that dnet would start ftem, exit, start it again and so on... Matt and somebody else blamed it on the modem. Well, I start dent -X -8 -b9600 on the amiga There is a piece of wire between the amiga and the sun, nothing else. I get to the login: get logged in, and type dnet Then the amiga says "DNET RUNNING", an FTERM comes up and then goes away. UNtil recently then another FTERM window would come up and so on. Im not sure what I changed, but now after the FTERM goes away, the DNET v2.01.10 window comes back with the suns name in the window. If i go over to the sun and try starting some dnet program, then wierd chars appear in the amigas dnet window. Any guesses? Iv'e go over and over the dnet docs and im sure all my paths are correct. REAL NAME: Joe Porkka jap@frith.cl.msu.edu
bmacintyre@watdragon.waterloo.edu (Blair MacIntyre) (12/13/89)
New and exciting problems in the wonderfull world of DNET.
I got the second newest version (Nov27th dates) and it worked, except
for the fact that there was no nfs-handler. So when the newest version
came out (Dec2nd dates) I ftp'd it and got the nfs-handler. But it
won't work!
So, I figured that something else must have changed, since the dnet
executable had been updated. So, I moved it to my bin directories, too.
So, now I had the entire newest version installed.
And now nothing works ...
Anybody have the very newest version working??? I had the first posted
version of the 7bit version worked, but no more ...
Symptoms:
- I am using a Sytek network (fast 7bit packet network to hook multiple
machines of different types to lots of terminals) to connect to our
Vax with my Amiga.
- when I run the newest version, the Vax kicks me out! No core file,
no nothing.
what I think might be happening is the dnet on the unix end is stoping.
Whenever I stop in with a break, it dumps me out, so this would make
sence.
Help!
--
-- Blair MacIntyre, Professional Leech on Society ( aka CS Graduate Student )
-- bmacintyre@{watcgl, watdragon, violet}.{waterloo.edu, UWaterloo.ca}
-- Date, verb: prearranged socializing with intent.
-- "Cornflakes should be seen and not heard" - anonymousakl@mentor.cc.purdue.edu (Rob Tillotson) (12/13/89)
In article <19234@watdragon.waterloo.edu> bmacintyre@watdragon.waterloo.edu (Blair MacIntyre) writes: >New and exciting problems in the wonderfull world of DNET. > >So, I figured that something else must have changed, since the dnet >executable had been updated. So, I moved it to my bin directories, too. >So, now I had the entire newest version installed. > >And now nothing works ... > >- when I run the newest version, the Vax kicks me out! No core file, > no nothing. You know, this sounds very familiar. When the first 7-bit version, it worked fine for me, but of course the nfs-handler was not there. Then, I picked up the new version and installed the new dnet binary. Much to my surprise, as soon as it started up, it opened the fterm window, exchanged some data, then disconnected me. I put back the old dnet executable and tried nfs-handler... upon mounting NF0: and cd'ing to it, a bunch of data is exchanged (and a few things written to the NFS log file; I recompiled the server with the DEBUG option on) but the Amiga end just hangs forever until dnet is killed, at which time I get a typical "NF0: not found" message from cd. An examination of the output of 'ps' shows that there are three processes running on the Unix system, with no control terminals, that seem to be associated with the NFS server. I haven't had time to look into it further. By the way, while the nfs-handler is hung the rest of dnet works just fine so I can fterm, putfiles, and getfiles all day with no problem... By the way, I am running dnet on a Sequent Symmetry running Dynix (pretty much 4.3bsd), and am connected by a dialup connection through an AT&T Information Systems Network which gives a 7-bit even parity link with XON/XOFF flow control... G'day, eh? --TS -- Rob Tillotson Internet: akl@mace.cc.purdue.edu 320 Brown St. #406 BITNET: ROBT@PURCCVM West Lafayette, IN 47906 Fido: 1:201/40.302
jac@muslix.llnl.gov (James Crotinger) (12/14/89)
Did you install the new DNET executables on both ends? When I went to the newest version (w/nfs-handler included in the archive) I somehow didn't get the newest dnet onto my Amiga and it wouldn't work. Once I got all the newer versions installed, everything worked as I described earlier (i.e. dnet works, amiga clients work, and UNIX clients work from an fterm window, but not from the Sun). I've never been able to get nfs-handler to work. Anyone else? Jim
jayward@eecs.cs.pdx.edu (Jay Ward) (11/11/90)
Hello D-Netters!
While setting this program up was a breeze, the problem comes
when dialing the UNIX machine at school. The FTerm will accept my AT
commands and dial, followed by CONNECT 2400. After that the FTerm
doesn't want to hear any more keystrokes. The 'SD' light doesn't even
light when I hit a key. I've tried an aweful lot of parameter configurations
when running, but nothing seems to work. Anybody have an idea?
----------------------------------------------------------------------------
Jay Ward --> jayward@eecs.cs.pdx.edu | "A waist...
jayward@jove.cs.pdx.edu | is a terrible thing to mind"
----------------------------------------------------------------------------proff@phoenix.pub.uu.oz.au (Frederick Solidus) (11/16/90)
In <639@pdxgate.UUCP> jayward@eecs.cs.pdx.edu (Jay Ward) writes: >Hello D-Netters! > While setting this program up was a breeze, the problem comes >when dialing the UNIX machine at school. The FTerm will accept my AT >commands and dial, followed by CONNECT 2400. After that the FTerm >doesn't want to hear any more keystrokes. The 'SD' light doesn't even >light when I hit a key. I've tried an aweful lot of parameter configurations >when running, but nothing seems to work. Anybody have an idea? Though I have yet to get DNET working, I have fixed the above problem. Look at the S:dnet.config (I think) file, in it you will see something like this ATUA 19200 "connect" ATUA 19200 "connect 300" ATUA 19200 "connect 1200" ATUA 19200 "connect 2400" Now, when DNET sees "connect xxxxx" in the input streem, it looks up the above table, and sets the baud rate (i.e the 19200 after ATUA) accordingly all you need to do it to change ATUA 19200 "connect" to ATUA 2400 "connect" and ATUA 19200 "connect 2400" to ATUA 2400 "connect 2400" Please tell me if you get DNET working, because my amiga side DNET does not seem to lock-on to the unix side ACK charactors. Proff/The Force