[OpenAFS] File server allegedly unavailable

[Mike Lee]

Is it MS ISA?
as I know it working with a proxy server, and it will be fine working
with tcp connection.
however, for udp, it will be terrible, for example, in Linux box can not
traceroute outside, however every MS client(win98/2k/nt) can.
I do not know the detail, (using the MS products, you are always junior
worker), answer from another junior, ISA just forward all request (above
1024 port) to a build-in proxy


Derek Atkins wrote:

>Are there any server logs?
>Perhaps the NAT gateway in w2k is doing something strange?
>
>-derek
>
>Charles Clancy <security@xauth.net> writes:
>
>>>Charles Clancy <security@xauth.net> writes:
>>>
>>>>Would this possibly fix the problem of multiple AFS clients behind a NAT
>>>>gateway?
>>>>
>>>No.  You can already have multiple AFS clients behind a NAT -- you
>>>just need to set the NAT UDP timeouts to be fairly large.
>>>
>>I tried upping the UDP timeouts on the Win2K NAT routing from 60 seconds
>>to an hour.  I can get 1 client working fine.  However, when a second
>>client on a second machine tries to connect, things stop working.
>>
>>For example:
>>
>>host1$ find /afs -follow
>>(things start going...)
>>
>>minute or so later:
>>host2$ find /afs -follow
>>(things go on both hosts for a couple seconds, and then both hosts stop)
>>(and give 'connection timed out')
>>
>>I've been unsuccessful with attempts to use both IPF on Solaris and
>>Win2K server's built in routing.
>>
>>--
>>t. charles clancy <> tclancy@uiuc.edu <> www.uiuc.edu/~tclancy
>>
>>_______________________________________________
>>OpenAFS-info mailing list
>>OpenAFS-info@openafs.org
>>https://lists.openafs.org/mailman/listinfo/openafs-info
>>
>