RE: WebDAV with Authentication through Zebedee

Hello,

 

I just wanted to send a quick email as an update to this issue and to close
off the thread for anyone who happens to be searching through the archives
in the future.  

 

It turns out I was incorrect in my previous email and in fact I have not
been able to reproduce my original problem.  My mistake was that I had an
incorrect setting in the Default Web Site which led me to believe I had
reproduced the original issue.  I have since deleted WebDav folders, created
new ones, and rebooted both the client and the server without reproducing.
Unfortunately I'm not sure if I'll ever be able to figure out what was wrong
in the first place.  Probably something wrong with the infinite permutations
of settings in IIS vs. the standard windows file permissions etc.  

 

The end result is that I've been able to setup a WebDav folder with
Integrated Windows Authentication piped through Zebedee and with the port on
the client side is not the same as the port on the server side.  The ports
being different was important to me so that I could use some random
hard-to-guess port on the server side but still use port 80 on the client
side.  This allows me to setup a windows Mapped Drive by using
\\localhost\MyWebDAVFolder <file:///\\localhost\MyWebDAVFolder>  which is
great for any local scripts to be able to access the shared folder on the
remote server.  

 

I guess I would see this as a simplistic alternative to piping FTP through
Zebedee.  I assume FTP has additional advantages but is also a little more
tricky to configure so it really depends on the requirements of the specific
situation.  

 

Thanks for listening

 

  _____  

From: Brent Sterling [mailto:[email protected]] 
Sent: Monday, February 16, 2004 4:08 PM
To: [email protected]
Subject: RE: [Zebedee-talk] WebDAV with Authentication through Zebedee

 

Thanks very much for the response Yves.

 

The domain\user idea was unsuccessful but it appears that keeping port
numbers the same may have helped.  Here's what I did:

 

As a test, I modified my settings so that the "website" is now listening on
port 80 and of course modified the zebedee server and client to work on port
80.  (i.e. I now use: "zebedee -d -T 1234 80:www.mydomain.com:80" whereas
before I had my web server listening on some random hard-to-guess port)

 

Turns out your suggestion worked!  I was able to login with either basic or
integrated authentication.  

 

Here's the interesting thing. maybe a bug I'm not sure.  After getting the
login to work, out of sheer curiosity I put my all my settings back to how I
had them originally and then disconnected any mapped drives on the client
and rebooted both server and client.  When I tried to connect it prompted me
and I logged in just fine.  I also verified trying to login with bad
usernames to make sure it wasn't just allowing everyone.  I tried a few
things to reproduce my original problem but I couldn't.  

 

I'm continuing to experiment and my latest observation is that if I
completely delete that original webdav folder ("virtual
directory/application" in IIS under the default website) and start over
creating a brand new one I can reproduce my original problem (again using
the weird port numbers so the client uses "zebedee -d -T 1234
80:www.mydomain.com:54321").  I'll attempt changing everything to port 80,
logging in, and then changing everything back and see what happens.  

 

Thanks again for your help.

 

  _____  

From: zebedee-talk-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:zebedee-talk-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Yves Smolders
Sent: Friday, February 13, 2004 5:51 PM
To: [email protected]
Subject: Fw: [Zebedee-talk] WebDAV with Authentication through Zebedee

 

Brent,

 

When entering user name and password, try adding the domain name with the
user name:  domain/user or domain\user, can't remember - this might help.
Also map the http server and client on the same port, don't redirect 8080 to
http (80) on the server, webdav does crazy things then (like showing
subfolders that don't exist...) - if you can't listen to port 80 on the
client, try binding the zebedee client to 127.0.0.2 instead of localhost!

 

I've got it running with clear text authentication, no problemo!

 

Yves

----- Original Message ----- 

From: Brent <mailto:[email protected]>  Sterling 

To: [email protected] 

Sent: Friday, February 13, 2004 10:13 PM

Subject: [Zebedee-talk] WebDAV with Authentication through Zebedee

 

Hello, 

 

I apologize if this question has been answered before.  I browsed through
the archives but I'm pretty sure the search isn't working so it's quite
possible I missed something while browsing. 

 

I've been a long-time user of Zebedee for tunneling XP's Remote Desktop
feature.  Recently I've been experimenting with using Zebedee for tunneling
a WebDAV connection.  My high level understanding is that WebDAV is
essentially an extension to HTTP.  On the server side Microsoft's IIS
supports WebDAV and it's built into XP on the client side.  

 

I have been able to setup a WebDAV folder in IIS and connect to it through
Zebedee from an XP client using the "Anonymous Login" setting in IIS.
However, when I change the folder security to require Basic Authentication I
cannot connect.  It continually prompts me for a userid and password even
though I'm entering valid credentials.  When I attempted this same scenario
with Zebedee out of the picture and a big hole in my firewall, I was able to
enter valid credentials and login just fine.  

 

In summary:

1)       Zebedee Tunnel - WebDAV Anonymous Login - Works

2)       No Zebedee - WebDAV Basic Authentication - Works

3)       Zebedee Tunnel - WebDAV Basic Authentication - Doesn't Work

 

Because of number 1) I'm fairly sure my basic tunnel setup is fine.  Because
of number 2) I'm fairly sure my WebDAV server and client setup is fine.  I'm
hoping that maybe I just have something configured wrong in Zebedee when
this additional authentication is needed.  

 

My Zebedee configuration is fairly straight-forward:

 

Server:

verbosity 1

server true                     # Yes, it's a server!

detached true                # Convert to daemon if possible

serverport 1234

target myserver

redirect 54321                # WebDav

compression zlib:9         # Allow maximum Zlib compression

keylength 256                # Allow key length up to 256 bits

 

Client Command Line:

zebedee -d -T 1234 80:www.mydomain.com:54321

 

Of course I point the webdav client to http://localhost/sharedfoldername and
the web server is setup to listen to port 54321.  Again it works for
Anonymous but not for Basic Authentication.

 

Any help that could be provided would be greatly appreciated!  Thanks!