Hi Jeff,
I'm fairly sure I remember the unix client officially supporting this sometime before the spinning off of OpenAFS. Is there any place today where one can consult release notes for old IBM/Transarc releases to verify?
I'm not currently in a position to test this but am interested in the results since we are considering adding a multi-homed server at some point. I wonder if anyone else is in a position to perform a test to verify Fabio's results?
-Mitch
On Sat, 20 Nov 2004, Jeffrey Altman wrote:
I have no idea if the Windows client contains multi-homed support or not. If there was a patch applied to the Unix client in order to
support multi-homed servers, please point me at it so that I can
apply a similar patch to the Windows client.
Jeffrey Altman
Fabio Bucciarelli wrote:
Hi!
I've tested AFS within a test environment consisting of 3 linux multihomed AFS servers (vlserver and fileserver) both connected to two LANs. I didn't define any NetInfo or NetRestrict file.
In addition, I have both windows and linux clients each connected to one LAN or another.
Linux clients work in both networks, while windows clients work only in
one of them (the one corresponding to eth0 interface for servers).
Windows client can ask the vldbserver, but when I try to access to the afs filesystem, it use the wrong IP address of fileserver (that of the first network).
I suppose that Windows client has not the multihomed support. Is that right?
Thanks in advance.
Take care, Fabio
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
