I tried to upgrade our Solaris 7 Sun E450 PDC from Samba 2.2.8 to Samba 3.0.2a recently. We are running Windows 2000 desktops. Most of our users connect via our LAN , however a significant group of users are connecting over our WAN - by a variety of methods , including ISDN and BT-NetEquip ( 512k/2MB line ).
After the upgrade all of the users on the LAN were able to reach there network resources via Samba consistently without problems. Initially , all of the users connecting via the WAN were also able to get to all there network resources , but we consistently found that after approximately 2 to 3 hours they all lost there network resources. Attempts by WAN users to log back on again failed. When running the login script , the error code 53 was frequently seen. Restarting the Samba daemons on the PDC fixed the problem , but this is hardly a feasible solution on a production PDC. In the end , I had to fall back to running 2.2.8. Can anybody out there help me please ? Thanks in advance Dominic Clarke Friends of The Earth www.foe.co.uk -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
