OK. In that case, we should check that ARMGR has managed to bind to the correct ports.

If you run 'netstat -a', you should see it listening on the following ports:

12078/tcp (the HTTP daemon)
18678/udp (the state daemon)
21075/udp (the service discovery daemon)
21076/udp (the port mapper daemon)
21077/udp (the mount daemon?)
21078/udp (the nfs daemon?)

On top of that, could you run the attached program, which is a diagnostic tool that just uses the service discovery protocol to find the HTTP and portmapper daemons?