Greeting Henry,
I say that is normal (because it's the same thing with a Windows server)
. If the notebook (with offline files enabled) is turn on without any
nic connected, Windows will work offline (no surprise here). A this
point, you can't map or acces the server share (you can try to access
share with UNC path, it will not work). But if you try to access share
on another server, not in the share mapping of your client, then all
work perfectly.
The "problem" is the client. You must enable online work to reaccess the
server share. Look at the taskbar on the windows client for a small
computer, double-click on it an try to synchronise, or just select the
option to work online without synchronize (look at the buttom of this
page
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/prdc_mcc_gmba.mspx?mfr=true).
Best regards,
Robert
--
Cybionet - Solution reseautique
http://www.cybionet.com
Hello,
since the update to Samba 3.0.25b Clients which have offline files enabled
- typically notebooks - are sporadical loosing their network drives.
In the samba logs I see:
"read_data: read failure for 4 bytes to client 192.168.1.58. Error = Connection timed out"
After a new login the client can connect again to the shares again, but
after some minutes of work the same thing happens again.
Clients with no enabled offline files have no problems.
We are using XP Prof. Clients and Samba 3.0.25b (sernet-samba) on Debian
Etch. One of our five samba file server is acting as PDC with OpenLDAP as
auth. backend.
Regards,
Henry
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
