Loading Profile...
conflict with windows file sharing
Hello,
I have WinXP, with file sharing enabled.
I am currently sharing the folder "c:\photos" under the name of "photos".
From another workstation, I can correctly access this resource.
However, when I start Wuala (in the first machine), after sometime running, I cannot access the resource "photos" anymore from the second machine.
It is as if Wuala is conflicting with windows file sharing.
I then stop Wuala,
and I can access again the "photos" resource from the second machine.
What can be the problem?
Regards,
DAvid
I have WinXP, with file sharing enabled.
I am currently sharing the folder "c:\photos" under the name of "photos".
From another workstation, I can correctly access this resource.
However, when I start Wuala (in the first machine), after sometime running, I cannot access the resource "photos" anymore from the second machine.
It is as if Wuala is conflicting with windows file sharing.
I then stop Wuala,
and I can access again the "photos" resource from the second machine.
What can be the problem?
Regards,
DAvid
1 person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?wuala is also running a so called samba (smb) deamon, which is the same thing (technical level) as windows file/foldersharing.
wuala normally creates a share called \\wua\la or similar names \\wua1\la or \\wua2\la and so on...
sometimes this conflicts in the local network with other smb names especially when it comes to browsing (workgroups) and unique smb names..
its hard to tell what the exact problem is, you should maybe also look into your syslogs (event viewer, system and application logs), maybe you see additional information there if windows couldnt use its windows filesharing services any more or if it has some ip conflict, or netbios problems and so on....
smb is pretty sucky in general, so thats the main aspect here... :(
eeeeeek. -
Inappropriate?Sometimes, it is possible to still access a shared folder by entering its IP address even though it doesn't work by entering the computers name. So instead of trying to access \\COMPUTERNAME\photos you could try accessing \\192.168.0.100\photos. You can find out the correct IP address by entering ipconfig on the commandline (Start -> Run -> Cmd, then ipconfig).
-
Inappropriate?I am already using the IP rather than the computer name.
My only option for the moment is to disable the file system integration, which is not working anyway.
(In my MacOSX is working. That's pretty cool!! :) )
EMPLOYEE
