> I have not been able to dublicate these issues however I am running samba > 2.2.3a so I thought it may be samba related.
Darrell, I read through the thread that you referred to on the experienced users forum and the problem sounds more like basic network connectivity issues than Samba related. The user reported not being able to ping known internal IP addresses. Samba has nothing to do with pinging. The thread goes on to report that Samba related services (e.g., printing) wasn't working either. This makes sense given the fact that the user can't ping machines on the internal network. Again, this doesn't appear to be a Windows Network issue (i.e., Samba) but related to basic network connectivity. In any event, I can't seem to replicate a problem with VPN on my end either. > Samba 2.2.3a is the recommended stable current release and prior > releases are known to have problems with Windows Explorer and Network > Neighborhood. Actually, the problem (bug) was only with the 2.2.3 release. I think the bug was determined to be a typo or something in a change that was made between versions 2.2.2 and 2.2.3. -- Greg J. Zartman, P.E. Vice-President Logging Engineering International, Inc. 1243 West 7th Avenue Eugene, Oregon 97402 541-683-8383 541-683-8144 www.leiinc.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
