Users not able to see remote users on the node network

Question

Users that belong to one node are not able to see users in another calendar
server node. Both calendar servers are pointing to the same directory server.
Some errors that occur in the log files:
DEXOTEK ERRCODE Ox13608 -> SchedBaseOpen: Section name too long
DEXOTEK ERRCODE Ox13608 -> OpenConnection: SchedBaseOpenOnHost
And when uninode -cws nodeID is run, it does not report being able to see all
the users and resources on the remote nodes.
uninode: connected to hostname.net.xxx.com, node 10000
directory of items: 10 (USERS = 10/RESOURCES = 0)
CONNECTION EX AV Q-SIZE IN-PROCESS IMPORT-DIR
(10000)->xxxxxx.xxx.com(10001) 2 2 0 0 370 (U=370/R=0)
Here is the nodes.ini file:
+ H=xxxxxxx.xxx.com/N=10000
+ H=xxxx.xxx.com/N=10001
all=2
There is a reported bug, that 16 chars is max on domain names for the nodes.ini
file, which means that you need to change that file and use:
     a) an alias that can be resolved on the network with either DNS or local
     host files
     b) use the IP address.
As documented in the release notes, here is the procedure on how to modify the
hostname when it is too long. Or how to modify the hostname for any reason.
Fix for long host names problem
If the fully qualified domain name for your network exceeds 16 characters, it
will be necessary to shorten the host name of all the servers in the Calendar
Server network . These instructions must be carefully followed to avoid causing
problems with the network. Ensure that the procedure is applied to ALL nodes in
the Calendar network.
1) The following procedure should be carried out on each server in the
Calendar network:
a) Bring the Calendar services down.
% unistop -y
b) Run the unidbfix command in export mode.
% unidbfix -export -n node-id
This will create a remotenode.ini file for each node on the server. The file is
located in the node's perm directory.
Example:
If you have two nodes on the server ROCK, node 1(in N1) and node (in N2), the
files are:
/users/unison/db/nodes/N1/perm/remotenode.ini
/users/unison/db/nodes/N2/perm/remotenode.ini
The remotenode.ini file will look something like this:
[1]
RN_NUMCONNECT = 2
RN_SURNAME = "unison"
RN_GIVENNAME = "unison"
RN_ORGUNIT1 = "uni2"
RN_ORGUNIT2 = "openmail"
RN_ORGANIZATION = "ABC Corp"
RN_ACCESSMETHOD = 2
RN_SERVICENAME = "unieng"
RN_HOSTNAME = "rock"
[2]
RN_NUMCONNECT = 2
RN_SURNAME = "unison"
RN_GIVENNAME = "unison"
RN_ORGUNIT1 = "uni4"
RN_ORGUNIT2 = "openmail"
RN_ORGANIZATION = "ABC Corp"
RN_ACCESSMETHOD = 2
RN_SERVICENAME = "unieng"
RN_HOSTNAME = "rock"
2) Once you have run unidbfix in export mode on all the servers, proceed as
follows:
a) Compare the remotenode.ini files and verify that the entries are the
same. In each file, you will note that an entry for the local node is not
included.
b) Edit one of the files (on any of the servers). This file will be
referred to as the master file. Add the appropriate entries for the
local node (copy the section from one of the other files). Modify the
RN_HOSTNAME in each of the sections of the master file to shorten the
name.
c) Copy the master file in the perm directories of each node on all the
servers.
3) Once the master file is in the perm directory of all the nodes, proceed as
follows on each server:
a) Run the unidbfix command in the -import mode.
% unidbfix -import -n node-id
b) Edit the nodes.ini file on the hub server and make the same changes to
the host names. You do not need to apply the changes.
c) Edit the [UTL] section of the /users/unison/misc/unison.ini file and
change the host name.
d) Start up the services.
% unistart
4) After all the changes have been made, run the uninode -cws all and
uninode -snc all commands and verify that the results are accurate.

Answer 1

See this:
http://docs.info.apple.com/article.html?path=Mac/10.6/en/8203.html
You should then see your pcs listed in Finder's sidebar under the shared section.
Regards