RPC 390109 is nsrstat (the only UDP thingy NW uses) and it looks like it could not connect to that RPC port on 192.168.40.168. Not sure why IP is used instead on name, but name resolution in place is likely required for this to work. You can do test from gst server and do rpcinfo -t 192.168.40.168 390113 2.
EDIT: On second thought, that might not be good example as -r does TCP connect, but I just tried it and it works:
ble1
4 Operator
•
14.3K Posts
0
September 21st, 2012 16:00
RPC 390109 is nsrstat (the only UDP thingy NW uses) and it looks like it could not connect to that RPC port on 192.168.40.168. Not sure why IP is used instead on name, but name resolution in place is likely required for this to work. You can do test from gst server and do rpcinfo -t 192.168.40.168 390113 2.
EDIT: On second thought, that might not be good example as -r does TCP connect, but I just tried it and it works:
[root@foo ~]# rpcinfo -t bar 390109 2
program 390109 version 2 ready and waiting