From: jcburt@gatsibm.larc.nasa.gov ()
Newsgroups: comp.os.linux
Subject: Network probs with X, NFS, etc...
Date: 27 Jan 1993 15:40:19 GMT
Organization: NASA Langley Research Center
Distribution: world
NNTP-Posting-Host: gatsibm.larc.nasa.gov

Hi there!
  Hopefully *someone* will have an answer and say "you forgot to
do x,y,z, stupid..." but I'm not sure where to go from here...

basically, I have a Gateway 2000 486DX-33 w/ ATI Ultra (8514) graphics
board, WD EtherCard PLUS16 ethernet board, 8MB RAM, 200 MB harddrive.

I'm running under whatever version of SLS that was on tsx-11.mit.edu
on friday 1/22, and Linux.99.4 kernel. now for the problems...

ftp & telnet work fine both into and out of the 486. rlogin works
fine into the 486, but gives an error message "rlogin: connection closed."
when going from the 486 to another machine. rsh *seems* to work fine
for executing other commands, but when no command is specified, it
defaults to rlogin and gives the same error message.

I can do an NFS mount of a remote filesystem with only one problem.
The mount operation goes fine, no error messages and the filesystem
appears just as it should...unfortunately it appears to be read-only,
even though I specified read-write both on the 486 and the remote machine.
Any command that requires writing to the directory returns the message
"permission denied". I've tried giving write permission on the remote
file system to everybody (chmod ugo+w), but I still can write to it
from the 486. Reading files is fine and FAST!!! I don't know if it
makes a difference, but the remote machine is a IBM RS/6000 running 
AIX 3.2.

I'm using startx to start the X8514 server, and it *seems* to be working fine for
local clients, i.e. any X client on the 486 runs fine and displays properly.
The problem occurs when I try to run an X client on a remote machine
and have it display on the 486. I've tried using the xon script, but 
nothing happened, no errors, no response, nothing. I tried to do things
manually by telneting into the remote machine (rlogin wouldn't work),
setting the DISPLAY environmental variable to point to the 486 (or
alternately using the -display commandline switch) and tried to run
xterm. nothing happens, no errors, and then xterm eventually times
out and says it couldn't connect to the server...it seems like its
finding the display okay, and its authorized to use the display, but it
just can't connect to the display...

going the other way around -- running the X server on the RS/6000 and
trying to run an X client on the 486 works fine, and the window comes
up like it should on the RS/6000.

It seems like things are set up correctly at the TCP/IP level (and below)
since I can connect fine (except rlogin) and have *excellent* terminal
response (even creating an xterm window locally and telneting from it) and
file transfers using ftp run like a bat out of hell...

A final problem I have is with xdm, which I don't think involves any
networking...I tried starting xdm up using "xdm -nodaemon  < /dev/console"
but the system seemed to lock up. Basically the screen would blank (going
to graphics mode) and the disk light would come on briefly, but then 
nothing happened. The screen stayed blank (no hatched background, no x cursor)
and any keypress resulted in a beep but nothing else...the only way I
could recover was to do a hard reset, or a cold boot.

Basically I think Linux is an EXCELLENT UNIX implementation (THANK YOU
Linus!!!!!), and installation was fairly easy...but I have a couple
of problems (mentioned above) that limit what I am able to do...

Suggestions anyone???????? 

John Burton
G & A Technical Software
jcburt@gatsibm.larc.nasa.gov





Newsgroups: comp.os.linux