Please don't laugh.
Some of my users have a need for a Windows FTP client that works with KfW.
Wait, it gets better.
The only two I'm familiar with are FileZilla and Kermit 95. The problem
is that the specialized server they need to connect to doesn't support the
ftp PROT command (ie,
Mike Dopheide wrote:
Please don't laugh.
NCSA had mods to the MIT ftp to run under Windows a few years ago, that worked
with We used to use them. Goole for: ncsa ftp kerberos
http://www.ncsa.uiuc.edu/UserInfo/Resources/Software/kerberos/ncsa_faq.html
Some of my users have a need for a
Yes, we do. :) But they were written in 1998 and I can't get them to
build in Windows against KfW.
-Mike
NCSA had mods to the MIT ftp to run under Windows a few years ago, that
worked
with We used to use them. Goole for: ncsa ftp kerberos
I've got a kerberized service that worked fine before I started
trying to use it through a load balancer. (I'm saying that for
background, not because I didn't think it should matter.)
So the current situation is that I've changed /etc/hosts and /etc/
nodename to contain the FQDN of the
[EMAIL PROTECTED] wrote:
I'm running into the proble of Kerberos using UDP over a VPN. I have
found lots of information on forcing the client to use TCP instead of
UDP. What I'm looking for instead is a way to do it on the server
instead. Is it possible to force a Windows2003 server to only
I'm running into the proble of Kerberos using UDP over a VPN. I have
found lots of information on forcing the client to use TCP instead of
UDP. What I'm looking for instead is a way to do it on the server
instead. Is it possible to force a Windows2003 server to only use TCP?
Hi all,
When do we get the error as Server not found in Kerberos Database?
I have a KDC on Win2003 and a client which is a Linux (redhat) is trying to
authenticate the users from this Active directory, which is on the win 2003
machine.
I observed that in case we specify the wrong user
I've got a kerberized service that worked fine before I started
trying to use it through a load balancer. (I'm saying that for
background, not because I didn't think it should matter.)
So the current situation is that I've changed /etc/hosts and /etc/
nodename to contain the FQDN of the
