It was the nat, the external IP is the one in the vldb, and the nat
wasn't tracking the connections right or something. Rebooting the NAT
machine fixed it.
Thanks for your help.
Jeffrey Altman wrote:
David Broudy wrote:
Jeffrey Altman wrote:
The most likely reason that you are not seeing updates on the second
machine is that the file server is unable to issue callback breaks
to that machine because of a network issue such as a NAT or Firewall.
There is a nat, but two client machines and the fileserver where the
volume I was testing on are all inside of it. The client that works has
exactly the same network config, is on the same ethernet switch, and it
getting it's address from the same dhcp server as the one that doesn't
work.
I'll try tcpdump tomorrow, is there another tool (rxdebug?) that I might
be able to find useful info in?
Thanks,
Dave
The most useful tool is to bump the file server logging state to 125
and look for messages describing showing the StoreData from the client
that is writing and the callback break attempts to the client that is
not reporting the changes.
--
Dave Broudy
[EMAIL PROTECTED]
Phone: 303.278.0908 Mobile: 703.401.5955 Fax: 303.674.6840
http://www.broudy.net/
AIM/YIM: dbroudy
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
