rsuberg at satx.rr.com
Sun May 17 00:36:28 CDT 2009
Interesting, though it has been a while, what I had to do to get samba to
recognize win pcs was that the linux box user needed to have an account on
the win box, and the other way was that the win box had to have an account
in samba daemon and/or linux system with the appropriate permissions that
Although I did say that it has been quite a while since I had to set samba
and that setup had been torn down some time ago due to needing the hardware
for another task.
From: satlug-bounces at satlug.org [mailto:satlug-bounces at satlug.org] On Behalf
Of Ian L. Target
Sent: Saturday, May 16, 2009 6:50 PM
To: The San Antonio Linux User's Group Mailing List
Subject: Re: [SATLUG] SAMBA
>> I've had the same problem in SAMBA whenever I used the /name/ of a
>> share (e.g.: smb://cadillac/filesharename), but, I find that if I use the
>> /network share's internal IP address/, (e.g.:
>> smb://192.168.X.1XX/filesharename) and set it as a bookmark for later
>> retrieval, my problem goes away. This has worked for me in all-SAMBA
>> environments, and in mixed SAMBA-Windows environments. If you contact me
>> off-list, I can send you a screenshot of my settings.
The smb://192.168.1.11/ did it! Thanks!
SATLUG mailing list
SATLUG at satlug.org
http://alamo.satlug.org/mailman/listinfo/satlug to unsubscribe
Powered by Rackspace (www.rackspace.com)
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.238 / Virus Database: 270.12.25/2109 - Release Date: 05/11/09
More information about the SATLUG