Section 3-3: No Connection to Remote Host

[ Previous chapter ][ This chapter ][ Next chapter ]


Subsection 3.3.1

Communication Problems on Various Configurations


Subsection 3.3.2

Communication Problems on DECnet

The host and/or network might be misconfigured. Check for node reachability of your own node and of the target node in NCP from other nodes with the command

$ mc ncp show node biox


Subsection 3.3.3

Communication Problems on TCP/IP

The host and/or network might be misconfigured. Check from another host whether you can reach your own node or the target node (e.g., basel.ch.embnet.org) with the appropriate command:

 

  
 % ping basel.ch.embnet.org
  

  
(You may need to be 'root' for this.)


Subsection 3.3.4

Connection Problems on X-Windows

As mentioned before , the connection of an X process requires that you permit access to your host. A frequent problem on personal computers is the limitation of the X-server programs (refer to the manual to optimise memory or other resources). Either you need to restart the X-server program or you reboot the personal computer.

If a special program fails, try to open a well-known program (such as a clock or terminal window). Some applications require specific performance features of local displays. Postscript viewers and molecular modelling programs are frequently affected if you work in heterogeneous environments.


[ previous chapter ],[ this chapter ][ next chapter ] , [next page/section] , or [overview] , or [table of contents]