[nfsd] Server can't contact local portmap, client can!

Question

I'm trying to setup nfsd on my i586 Arch. I've built a custom kernel with NFS v2 and v3 server & client support in it. I've also installed the nfs-utils (v1.0.6-2) package.
/etc/hosts.allow
sshd : all
telnet : 10.0.1., localhost
portmap: 10.0.1., localhost
lockd: 10.0.1., localhost
rquotad: 10.0.1., localhost
mountd: 10.0.1., localhost
statd: 10.0.1., localhost
/etc/hosts.deny
ALL: ALL: DENY
/etc/exports
/var/abs 10.0.1.2(rw,no_root_squash)
To get the NFSd running, I start portmapper with its rc.d-script and then the nfsd-script.
The nfsd-script won't work: it's complaining about portmapper:
portmap: server localhost not responding, timed out
RPC: failed to contact portmap (errno -5).
I made sure portmapper was running, BUT this is the strange part: if I try "rpcinfo -p <serverip>", I get an error (rpcinfo: can't contact portmapper: RPC: Remote system error - Invalid argument). When I run the same command on a client PC in the network, it works fine:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
I'm stuck.

Answer 1

Turns out my question was elementary. WebLogic was using my computer name (instead of IP) in the various configuration files. A search within the domain's folder for files containing "mycomputername" let me locate the areas that needed updating.