[OpenAFS] Win2K complaining about time-skew

[Thomas Cherryhomes]

Unlike a lot of people on here, I was able to get 1.0.4a installed and
working on Win2K Pro (Service Pack 1 though...)

I have a client in the same building I am in, I have set up his network
and he is connecting to our internet connection... I have set up a
NAT-wall to handle his network. The AFS server and the NAT frontend are
the same machine. (Configured with 64.64.113.126 (zeus.apogeemm.com) for
the outside world, and 192.168.1.1 for the internal network)

I have set up the machines INSIDE the NAT wall to connect to
64.64.113.126 address because the Win2K client bitches to me about not
having a name to match the network address for 192.168.1.1 ...

I am able to connect to the openafs.org and my local cell
unauthenticated without problems (and able to copy files in and out of
the test directory I gave full perms to system:anyuser).... 

However,

I am unable to authenticate using the Win2K client because it gives me
the following error popup:

"Unable to Authenticate, Error 2: Client and server clocks badly
skewed."

I checked the time on both the server and the client, and they both read
the same (within less than five seconds apart!!!)...

I AM able to authenticate with a linux client in my office outside the
NAT-wall...

and I AM able to authenticate with a win98 client in my office outside
the NAT-wall....

I DO not have a copy of Win2K for my office so I was unable to test from
outside the NAT-wall with that OS.

Any ideas??

-Thom