Hi esp. Jan,

> Ok, I've pretty much got it figured out, the setup scripts 
> use grep and such to find your hosts. However the grep for 
> sf2 will also return sf21, and this messes up things a lot.
> 
> Try the following:
> 
> in /etc/hosts on the servers, create `aliases' for your machines:
> 
> x.x.x.x sf2.ss.visual.bt.co.uk serverA
> x.x.x.x sf21.ss.visual.bt.co.uk serverB

I tried it. I still have the same problem, so I don't think
the grep is the problem. This is my output now:

==================================================================
[root_at_sf2 /vice]# createvol_rep coda:root E0000100 /vicepa
Servers are (serverA serverB )
HexGroupId is 7F000000
creating volume coda:root.0 on serverA
V_BindToServer: binding to host sf2.ss.visual.bt.co.uk
Volume 2a000001 (coda:root.0) created 
creating volume coda:root.1 on serverB
V_BindToServer: binding to host sf21.ss.visual.bt.co.uk
Volume 2a000001 (coda:root.1) created 
Fetching /vice/vol/Volumelist from serverB serverA 
V_BindToServer: binding to host sf2
VLDB completed.
<echo coda:root 7F000000       2 2a000001 2a000001 0 0 0 0 0 0 E0000100 >>
/vice/vol/VRList>
V_BindToServer: binding to host sf2
VRDB completed.
Do you wish this volume to be Backed Up (y/n)? [n] n
[root_at_sf2 /vice]#
==================================================================

Still, both volumes are created with the same number. Here
are the contents of the /vice/vol/remote files:

[root_at_sf2 remote]# more serverA.list 
P/vicepa Hsf2 T57f471 F57e430
Wcoda:root.0 I2a000001 H2a P/vicepa m0 M0 U2 W2a000001 C38e351a6 D38e351a6
B0 A0
[root_at_sf2 remote]# more serverB.list 
P/vicepa Hsf21 T74cc1 F73c7b
Wcoda:root.1 I2a000001 H2a P/vicepa m0 M0 U2 W2a000001 C38e36176 D38e36176
B0 A0
[root_at_sf2 remote]# 

The other files in /vice/vol however show all volumes being stored
on sf21.ss.visual.bt.co.uk. Somehow Coda takes the complete name
here although changed every occurance in of sf21 and sf2 in /vice
to serverA and serverB.

I don't really think the grep is the problem, because I had
the same failures when I used two servers called sf2 and sf3.

I've had this error since I moved my two clients and two
servers to a closed subnet (IP 10.x.x.x). I tried installing
a DNS, changing the server names, even using another machine 
for a server.

I think the only solution I see at the moment is formatting
the hard disk and reinstalling everything from the beginning.
Then I can be sure that there isn't an error in the Linux 
configuration.

Frank