Re: can't connect to portmapper from remote host

[haek@hem.passagen.se]

> > 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 max, 38 byte packets
>  1  194.236.111.1  35.586 ms  17.352 ms  22.604 ms
>  2  194.236.189.225  16.918 ms  16.289 ms  16.584 ms
>  3  213.64.49.142  17.099 ms  17.857 ms  16.629 ms
> [..]
> 12  130.241.15.6  43.565 ms  44.705 ms  42.999 ms
> 13  130.241.119.140  41.958 ms  51.164 ms  43.479 ms
> ------------snip-----------
> 
> But still no success with rpcinfo:
> 
> hans@amin:~$ rpcinfo -p 130.241.119.140
> rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host
> 
> 
> Any other hints?
> 
> Hans
> 


In my attempts to get NFS working, I tried to run the portmapper in a more verbose manner and it reported the following in syslog:

"May 10 03:09:16 Pc140 portmap[10473]: cannot bind udp: Address already in use"

Does that give anyone any hints?


Hans