Troubleshooting Exceed and Ssh problems

(from http://inst.eecs.berkeley.edu/connecting.html)

Troubleshooting Exceed and Ssh problems:

Problem: Possible Causes: Solutions:

You type the UNIX command (such as "xterm") and you get an error similar to
X connection to 128.32.138.27:11.0 broken (explicit kill or server shutdown).
An XWindows server (Exceed, XDarwin, etc) is not running on your local computer.
The .Xauthority file in the user's UNIX directory is old.
The UNIX account is over its disk quota; this prevents the .Xauthority file from being written.
Your firewall is blocking it. Start an XWindows server on your desktop computer.
Delete .Xauthority file in your UNIX acocunt; login again to UNIX account.
Reduce UNIX disk usage and login to the UNIX account again.
Turn off the firewall and try again. If that fixes it, then turn the firewall back on and enable the Hummingbird Exceed program. (For the Symantec filewall, turn off "auto protect" and tell it to alert you when it blocks something, so you'll get a chance to "allow" the XWindows connections.)

You type the UNIX command (such as "xterm") and you get an error similar to
Error: Can't open display:
OR
Error: Can't open display: cory.eecs.berkeley.edu:0.0
"X11 Forwarding" is not enabled in the Ssh window.
You have an old 'setenv DISPLAY' command in your .cshrc or .login file. Logout from UNIX, enable "X11 Forwarding", login again.
Remove all hard-coded 'setenv DISPLAY' commands, logout, login again.

You type "emacs &" and it just hangs for 30 seconds to a minute, then you are disconnected from the server you are logged onto. "X11 Forwarding" is enabled in the Ssh window but you are not running an XWindows server.
You have an old 'setenv DISPLAY' command in your .cshrc or .login file. Run the command "emacs -nw &" (-nw = 'no windows').
or
Run the command "emacs" (without the &) so you can see any error messages.
Remove all hard-coded 'setenv DISPLAY' commands, logout, login again.

Problem:	Possible Causes:	Solutions:
You type the UNIX command (such as "xterm") and you get an error similar to X connection to 128.32.138.27:11.0 broken (explicit kill or server shutdown).	An XWindows server (Exceed, XDarwin, etc) is not running on your local computer. The .Xauthority file in the user's UNIX directory is old. The UNIX account is over its disk quota; this prevents the .Xauthority file from being written. Your firewall is blocking it.	Start an XWindows server on your desktop computer. Delete .Xauthority file in your UNIX acocunt; login again to UNIX account. Reduce UNIX disk usage and login to the UNIX account again. Turn off the firewall and try again. If that fixes it, then turn the firewall back on and enable the Hummingbird Exceed program. (For the Symantec filewall, turn off "auto protect" and tell it to alert you when it blocks something, so you'll get a chance to "allow" the XWindows connections.)
You type the UNIX command (such as "xterm") and you get an error similar to Error: Can't open display: OR Error: Can't open display: cory.eecs.berkeley.edu:0.0	"X11 Forwarding" is not enabled in the Ssh window. You have an old 'setenv DISPLAY' command in your .cshrc or .login file.	Logout from UNIX, enable "X11 Forwarding", login again. Remove all hard-coded 'setenv DISPLAY' commands, logout, login again.
You type "emacs &" and it just hangs for 30 seconds to a minute, then you are disconnected from the server you are logged onto.	"X11 Forwarding" is enabled in the Ssh window but you are not running an XWindows server. You have an old 'setenv DISPLAY' command in your .cshrc or .login file.	Run the command "emacs -nw &" (-nw = 'no windows'). or Run the command "emacs" (without the &) so you can see any error messages. Remove all hard-coded 'setenv DISPLAY' commands, logout, login again.

X connection to 128.32.138.27:11.0 broken (explicit kill or server shutdown).

Error: Can't open display: OR Error: Can't open display: cory.eecs.berkeley.edu:0.0

Error: Can't open display:
OR
Error: Can't open display: cory.eecs.berkeley.edu:0.0