My setup (if you mean samba) is working like a dream.
Connecting with the server with 'normal' Windows devices is working fine. (XP, 2K and 98)
Connecting with the server with a Linux system is working fine too.
Only connecting the pda is a problem. It begins with the fact that the server is not displayed in the "network neighborhood". I know the path but when I enter it I receive an error.
Quote:
|
Cannot map network path. Network resource cannot be found or you do not have permission to access the network. Contact you network administrator.
|
The pda does not prompt me for user and password. I just gives the error. It is not possible to enter the name and password
before I try to connect to the server
On the web there are some suggestions given to make samba3 working with WM2003se but they do not work for me:
1. Change the "security" from ‘user’ to ‘share’ in smb.conf. ------- no change
2. Change the value "use spnego" to ‘no’ in smb.conf. --------------- no change
Further more:
The pda connects to my old samba2 server without problems
The pda connects to Windows shares without any problems
In both working cases the shares are displayed in the "network "neighborhood". It is possible to browse to the right map and
after I hit enter the name and password are asked and the connection is established.
For connecting the pda to shares I use resco explorer 2005 v5.21
I believe it is some sort of bug in samba but I can not verify that, because I do not know anybody who can try to test this too.
Both (samba 2 and 3) smb.conf are almost the same.
If it is possible I roll back to samba 2, but on suse10.0 this results in dependency hell...
