Filesystem integration doesn't work in latest Ubuntu 8.04.
Here are the details.
Debug log initialized
Starting server Mount ...
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:209)
at org.alfresco.jlan.oncrpc.TcpRpcClient.<init>(TcpRpcClient.java:57)
at org.alfresco.jlan.oncrpc.RpcNetworkServer.registerRPCServer(RpcNetworkServer.java:89)
at org.alfresco.jlan.oncrpc.mount.MountServer.startServer(MountServer.java:203)
at org.alfresco.jlan.app.JLANServer.doStart(JLANServer.java:307)
at org.alfresco.jlan.app.JLANServer.start(JLANServer.java:165)
at com.wuala.jlan.WualaJLanServer.start(Z:73)
at com.wuala.jlan.JLan$1.doRun(Z:65)
at aA.d.run(Z:35)
Starting server NFS ...
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.<init>(Socket.java:366)
at java.net.Socket.<init>(Socket.java:209)
at org.alfresco.jlan.oncrpc.TcpRpcClient.<init>(TcpRpcClient.java:57)
at org.alfresco.jlan.oncrpc.RpcNetworkServer.registerRPCServer(RpcNetworkServer.java:89)
at org.alfresco.jlan.oncrpc.nfs.NFSServer.startServer(NFSServer.java:365)
at org.alfresco.jlan.app.JLANServer.doStart(JLANServer.java:307)
at org.alfresco.jlan.app.JLANServer.start(JLANServer.java:165)
at com.wuala.jlan.WualaJLanServer.start(Z:73)
at com.wuala.jlan.JLan$1.doRun(Z:65)
at aA.d.run(Z:35)
</init></init></init></init></init></init>
i tried to use filesystem integration on linux (gentoo) but encountered a very strange error named "success".
#: mount /mnt/wua.la/wuala/direct
mount: mount to NFS server 'localhost' failed: RPC Error: Success.
on that computer a nfs-server is running, so i started wuala using the -noportmapregistration option. btw: can this option be entered somehow into wualarc?
my fstab entry looks like this:
localhost:/wuala /mnt/wua.la/wuala/direct nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183
the check reports portmap and service as ok and volume and integration as failed.
On win xp pro sp2 64 bit:
filesystem integration is not ready.
When I press "check" button I see grre marks on first 2 items, and red with "network drive connected" and "fs integration working".
My computer have 2 ethernet interface.
Now can I fix problem?
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
Trying to mount \\Wua20191\La
java.io.IOException: System error 53 has occurred.
The network path was not found.
, 2
at com.wuala.obfuscated.adf.k(Z:42)
at com.wuala.jlan.JLanActivator.tryConnect(Z:112)
at com.wuala.jlan.JLanActivator.run(Z:98)
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
Trying to mount \\Wua20191\La
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
java.io.IOException: System error 53 has occurred.
The network path was not found.
, 2
at com.wuala.obfuscated.adf.k(Z:42)
at com.wuala.jlan.JLanActivator.tryConnect(Z:112)
at com.wuala.jlan.JLanActivator.run(Z:98)
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
Trying to mount \\Wua20191\La
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
java.io.IOException: System error 53 has occurred.
The network path was not found.
, 2
at com.wuala.obfuscated.adf.k(Z:42)
at com.wuala.jlan.JLanActivator.tryConnect(Z:112)
at com.wuala.jlan.JLanActivator.run(Z:98)
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
Trying to mount \\Wua20191\La
java.io.IOException: System error 53 has occurred.
The network path was not found.
, 2
at com.wuala.obfuscated.adf.k(Z:42)
at com.wuala.jlan.JLanActivator.tryConnect(Z:112)
at com.wuala.jlan.JLanActivator.run(Z:98)
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
Trying to mount \\Wua20191\La
java.io.IOException: System error 53 has occurred.
The network path was not found.
, 2
at com.wuala.obfuscated.adf.k(Z:42)
at com.wuala.jlan.JLanActivator.tryConnect(Z:112)
at com.wuala.jlan.JLanActivator.run(Z:98)
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
[SMB] Win32 NetBIOS Failed To ReInitialize LANA
10044:CreateSocket - Socket type not supported
Todays update brings a few changes to the filesystem integration, see
http://wua.la/Luzius/Documents/Wuala/...
The main change is that Wuala now shows a listing in the mounted network share and gets mounted as W: under windows. This enables accessing your files with your systems file browser. You have no write access (yet), but it might still be useful. Generally, the W: approach gives much better system integration, but only allows for a very limited feature set. What do you think? Do you like it? Do you prefer the Wuala browser window? When? When not?
Todays update adds direct write access. This allows you to directly edit files stored in Wuala. The only requirements are that filesystem integration must be running and you have write access to the files you want to edit. Share your experiences about write access here.
Loading Profile...
jdfoote
last replied
on August 28, 2008 14:31
superwutze
last replied
on August 19, 2008 14:13
sunk818
last replied
on April 25, 2008 01:07
EMPLOYEE