Hello,

I just installed kde on windows and tried to use it at work.
Unfortunately I can't access the folders and files that are on the company network...

I tried to paste the "windows path" which is like this "\Company01AllUsers" in the path bar of dolphin but it says it can't find the file...

any idea ?

Thank you

you can't for now, as a workaround you can map the network drive to a letter

I do not know if KDE supports those paths. Have you tried using the smb: kioslave? smb:/machine ?

on linux \ is mapped to smb:/ we don't have the smb kioslave on windows, since smb is native to windows, but it's not working yet :P

Brandon wrote:you can't for now, as a workaround you can map the network drive to a letter

Thanks, that works for the folder mapped and subfolders.
But now i would like to follow links but 'windows link files' does seem to be recognised
Maybe i'll have to rename all my links with the mapped disk ?

if the links points to unc paths they won't work of course

I've got a similar situation, only the UNC paths use double-(back)slashes (\\network_share\directories\on\share. Cygwin uses //network_share..., and access to the network share's drives is allowed under permissions using \\network_share\c$\directory...), and we have around 20 or so (mostly windows 2003 or 2008 servers, some winXP desktops) which we have access to (though we generally actively use a couple at a time); so mapping the network shares to local drives isn't very feasible.

What's the status of the SMB KIO slave on Windows? Could there be a work-around which uses another method for accessing these? It seems that Windows natively supports direct access using just the UNC path for all applications, though I suppose that might not work for KDE applications which use their own infrastructure and want to avoid relying on the OS in this area.

you are right that windows can open natively UNC paths and so does kde since in the end we use windows function, the problem is that right now it's broken since we use url like file:///c:/windows that are converted to c:/windows, so I'm thinking what would be the easiest way to fix this, like having file://///192.168.0.10/share converted to \\192.168.0.10\share or have a fake smb:/ kioslave that it's a clone of kio_file but adds \\ to the path

That makes sense. So, really it comes down to a convention for mapping a KDE path (file://... smb:/...) to a (windows) UNC path (and vice-versa) which currently isn't there.

I would be in favor of just using smb:/ since actually using samba seems a little redundant on a windows machine, and "file://///" is a lot of slashes and imo less than intuitive.

In doing this, I would like it if you could type either back or forward slashes and have it be recognized as a UNC path; since Windows recognizes and uses "\\unc\path" while cygwin recognizes and uses "//unc/path", and I use both all the time at work. If that isn't possible, than my vote would be to just use the Windows' "\\".

from a user point of view you will use \\ or smb:/ the problem is just how to handle it internally

apparently it's a bit more complicated to really support smb, with plain unc paths I can't use authentication, I have to use wnet functions, so I think the best is to make a smb kioslave

Hi,
I would like to know what's the current status of the sftp kio_slave on windows?

I saw a patch on a mailing list being posted a while ago. Is it working?

Thanks for everything.

sftp and fish don't work very well for now, you need to download and put plink.exe into the kde bin folder to make them work

Thanks, it's good to know that it should be working. I copied plink but I'm having some problems getting it to work.

It always gives "sftp: unknown error: 0". Do I need to use a specific version of KDE? I tried with ver 4.2.95.

Thanks again.

try to specify the username in the url like sftp://username@192.168.0.100