I already tried with the username. I also tried with the ip or with the domain.
I always get the same error.

in the 4.3 packages we have added a testing smb kioslave you can either use smb:// or \\ to access a share

Thanks. Now, I'm able to browse those shares using dolphin and konqueror. However, the kioslave frequently pops up an application error ("The exception unknown software exception (0xc0000005) occurred in the application at location 0x0034f515."). It isn't fatal - I can continue browsing the share, it just keeps popping up the error message.

I just installed KDE 4.3.1 (MSVC x86), and it looks like the smb:// kioslave was removed. Any word as to when what the status is and when we can expect its return? (of course I can live without it).

Also another question: (with appropriate permissions), we can access the local drive of another machine on the network using \\machine\c$\local\path\on\other\machine. Will this be possible (eventually) using the smb kio?

we just forgot to add it since I didn't backport it in svn, we added it as a patch in 4.3.0
of course it's possible to access c$, like explorer you won't see it in the list of shares because $ as suffix is used to make a share folder hidden

Looks like it didn't make it into 4.3.2, either. Oh well.

Reverting to 4.3.0 and retrying the c$, looks like that does work (I'm not remembering where I'd tried it before that it didn't let me; oh well).
I guess I'll just stick with 4.3.0 for a while.

I just installed KDE 4.3.4 on Windows XP. What I need the most is to use Kate over fish KIO to do some programming on my server remotely. When I enter "fish://..." into Kate's file browser and press enter, nothing happens. KIO "sftp://" gives the already mentioned "unexpected error: 0".

Using "username@" at the beginning of URL doesn't affect anything. Plink.exe didn't help in this matter either.

Any hints? Or it just doesn't work? Any plans? Progress?

atrox wrote:When I enter "fish://..." into Kate's file browser and press enter, nothing happens.

Aha, trying "fish://" in Dolphin revealed that it's an "invalid protocol".