Re: serial terminals

1. Edit /etc/inittab There is probably some commented lines not unlike this one: # Example how to put a getty on a serial line (for a terminal) # T0:3:respawn:/sbin/getty -L ttyS0 38400 vt320 3 is the initlevel (it will only be activated in initlevel 3) -L is for local (no carrier detect) serial

Re: can't connect to portmapper from remote host

> > if you can't reach the host, then there is either a routing problem or > > a firewall blocking you from connecting to that host. > > traceroute -n 130.241.119.140 from 194.236.111.14 appears to be successful: > > -snip-- > traceroute to jobbet (130.241.119.140), 30 hops ma

how to open port 111?

Hello again debian-user! I have a problem with the portmapper not responding to remote calls: (jobbet=agda=130.241.119.140, amin=194.236.111.14) "[EMAIL PROTECTED]:~$ rpcinfo -p jobbet rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host" It works alright from localhost

can't connect to portmapper from remote host

Hello again debian-user! As I was trying to set up NFS on a debian-potato-box at work ("agda" at 130.241.119.140) I found out that the remote host, that was to be the NFS client 194.236.111.14, could not connect to the portmapper on the server. The error message recieved was "No route to host".