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

Re: can't connect to portmapper from remote host

On Mon, May 07, 2001 at 08:17:38AM -0700, Nate Amsden wrote: > sounds like a generic routing problems rather then a portmap problem. > run 'traceroute -n 130.241.119.140' from 194.236.111.14. traceroute > is in the traceroute package. > > if you can't reach the host, then there is either a routing

Re: can't connect to portmapper from remote host

[EMAIL PROTECTED] wrote: > > 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

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".