Yes, it is a well known old Swiki 1.1 problem (It is there since the release
of BigTime) 

Until now there is no cure: 
You can only install a prevous release of swiki (the 1.0 version), that
never had this problem under the same machine & network circumstances.
Jochen Rick did try to solve it over and over and then again, the man must
be tired now... 

Referring to other advicers on this swiki-list: you have in reality even
more choices: 
choice 1: buy a Mac 
choice 2: buy a *nix-machine
choice 3: keep your money, reinstall swiki 1.0, and hope that some day....


-----Original Message-----
From: Baveco, Hans [mailto:J.M.Baveco at Alterra.wag-ur.nl]
Sent: Thursday, November 15, 2001 12:09 PM
To: 'squeak-dev at lists.squeakfoundation.org'
Subject: [PWS] problems with uploading in comswiki1.1 (win network)


(As the pws list bounces, I post this question here ...)

Hi, finally upgrading my swikis on the intranet from swiki beta 11 to Swiki
1.1, I could not get the uploading facility working.
On beta11 I always got the error window "Cannot find server or DNS Error"
when uploading something, but the actual upload did succeed nonetheless and
the file showed up in the list of uploads after refreshing the view. 
However, on 1.1 I get the same error window, but uploading is NOT succesful.
This is on a microsoft NT network. The problems occur irrespective of
whether the server runs on a NT4 or Win2000 machine, and both with uploading
to the swiki server disk (with the default settings) or a remote disk. 
Uploading from the local host does work mostly, but not when the swiki is
run as a service.

---reaction Ger:---------------------
-
- local upload?: 
- You mean that you move files to the swiki directories and then restart the
machine?
- That works, but it kills the elegance of the swiki form the user's point
of view.
- (Watch out: If you give people ftp-access to all your swiki-directories,
- they also see the uncrypted administrator's password in
swiki\refs\security.xml!
-  
- end of reaction---------------------

Anyone else encountered these problems? I suspect they occur on any windows
network, except of course if it is the result of me using the wrong
settings.

Hans