|
Grex > Helpers > #123: Grex System Problems - Fall 2003 |  |
|
| Author |
Message |
| 25 new of 291 responses total. |
remmers
|
|
response 223 of 291:
|
Dec 8 22:47 UTC 2003 |
(People are still writing OS's for the Amiga?)
|
scott
|
|
response 224 of 291:
|
Dec 8 23:01 UTC 2003 |
Re 222: In fact, there's a joke in there somewhere.
"I was at the computer store, and the sales guy was supposed to give me $7.12
in change. He was out of dimes, but instead of 2 nickels I grudgingly
accepted an NE2000 clone."
|
mcnally
|
|
response 225 of 291:
|
Dec 9 00:45 UTC 2003 |
Shouldn't you have gotten a dozen of them for your dime?
|
gull
|
|
response 226 of 291:
|
Dec 9 01:11 UTC 2003 |
<chuckle> True. I do think it's ironic that we're still using PCI
clones of one of the worst ethernet card designs ever. On the other
hand, CPUs are so fast now that hardware efficiency hardly matters for
such things. I use 'em and they work great. :>
|
rcurl
|
|
response 227 of 291:
|
Dec 9 05:24 UTC 2003 |
I found the MacTCPWatcher website and downloaded the utility. However the
Trace option was grayed out and the documentation declares " Note that
Traceroute is an OT only function. You cannot use it under MacTCP. (The
button greys out under MacTCP.)" I guess it should be called
MacOpenTransportWatcher.) Anyway, PING works, but returns no responses
from cyberspace.org.
|
gelinas
|
|
response 228 of 291:
|
Dec 9 05:34 UTC 2003 |
Shoot. We need traceroute, to find out where the packets are dropping.
|
other
|
|
response 229 of 291:
|
Dec 9 05:40 UTC 2003 |
Can we run it in the other direction? Trace from Grex to Rane's
machine, provided he can identify its IP?
|
gelinas
|
|
response 230 of 291:
|
Dec 9 05:45 UTC 2003 |
Last I heard, only staff could run traceroute. If we know when he is online,
and the IP address, we can give it a try.
|
twenex
|
|
response 231 of 291:
|
Dec 9 08:18 UTC 2003 |
Re: #226: We're still using clones and kludged upgrades of one of the
worst-designed CPUs ever, too. There are rumours that IBM was going to
go for the MC68000 for the original PC design, but rejected it on the
grounds that it was too expensive and there weren't many expansion
cards available for it... If only...!
|
cmcgee
|
|
response 232 of 291:
|
Dec 9 13:46 UTC 2003 |
Yellow Alert:
In the next few weeks, UM ITD and CAEN will stop allowing telnet and FTP to
and from there. Sometimes I try to telent over to grex from school. The few
times I've tried SSH, I get cut off because Grex is using some funny version.
Until now I didn't care; telnet and FTP worked. Soon they won't and I wont
be able to get to Grex during the day.
Can someone help me figure outhow to check email and move files when telent
and FTP are forbidden?
|
other
|
|
response 233 of 291:
|
Dec 9 13:58 UTC 2003 |
Hmm. My machine's version of SSH is too new to be compatible with
Grex, so I told it to use rlogin (whatever that is) and I've had no
difficulty establishing or maintaining a connection using the SSH
utility since.
I'm not sure if that translates, but perhaps someone with more
knowledge than I about these things can use it to help you.
|
gull
|
|
response 234 of 291:
|
Dec 9 14:16 UTC 2003 |
Re #232: Grex is running an old version of SSH. What client are you
trying to use to connect? If you have the option, make sure you tell it
to use SSH protocol version 1 instead of version 2.
rlogin is non-encrypted, so it's not as good as SSH but it's no worse
than telnet.
If you get SSH working you can use SCP to copy files to and from Grex,
assuming you can find a client. (Under UNIX-ish operating systems the
'scp' command should work.)
I don't know of a good SCP client for Windows that works on Grex.
Normally I use WinSCP, but it doesn't seem to work with Grex...I get
this error:
Error listing directory "/a/g/u/gull".
Unexpected directory listing line "drwxr-xr-x 5 gull 2560 Dec
8 18:00 .".
Operation aborted
Maybe Grex should upgrade to a newer version of SSH.
|
jp2
|
|
response 235 of 291:
|
Dec 9 14:30 UTC 2003 |
This response has been erased.
|
gull
|
|
response 236 of 291:
|
Dec 9 14:34 UTC 2003 |
I assume that will happen some time in the next decade, when NextGrex
comes online. ;>
|
gelinas
|
|
response 237 of 291:
|
Dec 9 15:43 UTC 2003 |
I've just logged in to grex from ITCS' login servers (login.itd.umich.edu),
using the version of ssh installed there. Because my login id on both
systems is the same (but the passwords aren't), I created a new id to
test with; that one also worked from login.itd
I did get the warning about the server lying about its key size, but it
still worked.
If you are not using login.itd, you may need to talk to the administrators
of the system you are using.
|
sholmes
|
|
response 238 of 291:
|
Dec 9 17:01 UTC 2003 |
I too get the warning about the server lying about its key but it's not
always . ..sometimes I get it and sometimes I don't.
|
mcnally
|
|
response 239 of 291:
|
Dec 9 17:20 UTC 2003 |
re #232: if "ssh grex.org" doesn't work because the host you're trying
from wants to talk a newer version of the ssh protocol, you might try
"ssh1 grex.org". Some machines support an "ssh1" command for backwards
compatibility.
|
jhudson
|
|
response 240 of 291:
|
Dec 9 19:17 UTC 2003 |
For windows, try putty and psftp to connect to grex.
To find them, try this
http://www.google.com/search?q=putty+download
|
aruba
|
|
response 241 of 291:
|
Dec 9 22:42 UTC 2003 |
Right, putty works great, and it has a pscp client (though you download that
separately).
Colleen - I happen to be in the UM library at the moment, and I couldn't ssh
directly to Grex either (using SSH Secure Shell, version 3.2.3). It says
it's downgrading to version 1 to connect to Grex, but then it craps out
anyway.
However, I am able to use Secure Shell to connect to login.itd.umich.edu,
and then from there type "ssh -l aruba cyberspace.org", which connects me to
Grex just fine. Kinda clunky, bt it does work.
|
gelinas
|
|
response 242 of 291:
|
Dec 9 22:59 UTC 2003 |
Hmm... which OS are the Library machines running?
|
jmsaul
|
|
response 243 of 291:
|
Dec 10 00:57 UTC 2003 |
I've never been able to get putty to work with Grex. Might be a configuration
issue.
|
rcurl
|
|
response 244 of 291:
|
Dec 10 03:47 UTC 2003 |
Re #s 227-230: I will probably be on too irregularly from Florida - and only
until tomorrow....so we'll probably not be able to trace this problem....
oh well, I have been able to get on these past few days.
|
scott
|
|
response 245 of 291:
|
Dec 10 04:42 UTC 2003 |
I used to use putty with Grex all the time. Worked fine, I used ssh from an
NT 4.0 box.
|
remmers
|
|
response 246 of 291:
|
Dec 10 13:31 UTC 2003 |
Re #243: I assume you can get other ssh clients to connect to Grex in
the same environment? I use PuTTY to connect to Grex also. Configuration
could be the problem. I had to fiddle with the "ssh" settings a bit.
|
twenex
|
|
response 247 of 291:
|
Dec 10 14:49 UTC 2003 |
I can confirm that PuTY does indeed work with Windows, (XP in my case)
|