[Samba] Re: About Microsoft/Novell accord
Stéphane Purnelle <[EMAIL PROTECTED]> > Dear samba team, > > I created a folder on my website (french linux website) about this huge > movement of Novell. > And for make my articles, I want to have the official position of samba > team about this accord. For anyone unfamiliar with this: http://news.com.com/Red+Hat+couches+Microsoft-Novell+pact+as+a+Linux+win/2100-7344_3-6132323.html -- Gerard -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: How to copy a file from linux to window pc
"Indunil Jayasooriya" <[EMAIL PROTECTED]> > Hi, > > I have file at /opt/mailbackup/mailbackup.tar.gz (this is a Linux Machine) > > I want to put this file to a windows pc. > > What is the command to do it. > > can I use something like the following. > > mount -t smbfs > > Then How to use this ? I use this method on my FreeBSD 6.1 system. 1) Create a directory: '/c' 2) Create an alias: alias c:='mount /c' 3) Place this in my /etc/fstab file: //[EMAIL PROTECTED]/directory/c smbfs rw,noauto 00 Obviously you will need to make sure that the drive or directory you want to access are configured correctly on the Windows machine. Now all I have to do is type: c: at the command line and the Win share is mounted. I can then do a simple cp . Ciao! -- Gerard Terrorist memo: Bush is listening. Use big words. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Length of share name
I am new at setting up Samba3. I had heard that the name share name is supposed to be limited to 8 characters or less; i.e., [home] or [configs], etc. Is this correct, or can the name be longer? Also, are there any specific characters that are not allowed? I am not planning on using any, but I was just wondering. Ciao! -- Gerard Seibert [EMAIL PROTECTED] A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines. With consistency a great soul has simply nothing to do. Ralph Waldo Emerson -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Changing the server string server string
Andres Tarallo <[EMAIL PROTECTED]> > Holy Windows !, I never thought that this value was cached into the > registry. > > I solved it with your advice. Thanks god it's only as small pilot > installation of 20 clients, things are worst in deployment (more than > 400 clients) > > John H Terpstra wrote: > > On Tuesday 04 July 2006 13:54, Andres Tarallo wrote: > > > >> I'm using Samba 3.0.22, My samba server announces as "SAMBA > >> 3.0.22xx", so I added in the samba conf a line that says server > >> string = File Server. > >> > >> tesparm reports that everything is Ok, but I when I browae the shares > >> the old name still appears. Coukd it be hardwired? > >> > > > > No, it is NOT hard-wired - but your MS Windows clients have stored the > > original value in their registry. If you want to change what the client now > > thinks it is - go edit those registries! This is a great way to have fun > > with Windows. :-) (not!). > > > > - John T. > > Actually, you could have used a simple utility program like 'jv16' to accomplish the same feat. I remember seeing something in the MSKB about how to accomplish this also, but I do not remember exactly how it was proposed. -- Gerard Seibert [EMAIL PROTECTED] "I was relaxing in my favorite chair on Sunday, reading the newspaper, watching a football game on TV while listening to another game on the radio, drinking a beer, eating a high cholesterol snack, and scratching our dog with my foot and my wife had the nerve to accuse me of just sitting there doing nothing!" -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Accessing ZIP drive
I have Samba 3.0.22 installed on a FreeBSD 6.1 OS. I am fairly new to Samba, so please bear with me. I set up shares for /var /usr and $HOME without any problems. They can all be accessed from one of my WinXP Pro machines without incident. I then created a share for the ZIP drive on the FreeBSD system. Unfortunately, I am unable to access the the ZIP drive installed on the FreeBSD machine. I continually receive this error message: ** \\seibercom\zip is not accessible. You might not have permission to use this network resource. Network access is denied! ** I have no idea how to correct this problem. The ZIP drive is mounted automatically at boot time from /etc/fstab. -- Gerard Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error Message With One PC
I am running Samba on a FreeBSD 5.4 OS. When one PC, a Window's XP Pro, starts up on the network, this error message is displayed on the FreeBSD computer: $ Apr 5 05:35:41 seibercom smbd[92214]: [2006/04/05 05:35:41, 0] lib/util_sock.c:write_data(557) Apr 5 05:35:41 seibercom smbd[92214]: write_data: write failure in writing to client 192.168.0.4. Error Broken pipe Apr 5 05:35:41 seibercom smbd[92214]: [2006/04/05 05:35:41, 0] lib/util_sock.c:send_smb(765)Apr 5 05:35:41 seibercom smbd[92214]: Error writing 4 bytes to client. -1. (Broken pipe) This message only appears when this one particular PC starts on the network. I cannot find out what is causing it. Perhaps someone might be able to assist me. Thanks! -- Gerard [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error Message
I am running FreeBSD 5.4 with Samba-3.0.21b,1 which is the latest version available for FreeBSD. I continually receive this error message: [EMAIL PROTECTED] ~ $ Mar 10 18:44:28 seibercom smbd[41038]: [2006/03/10 18:44:28, 0 ] lib/util_sock.c:read_data(529) Mar 10 18:44:28 seibercom smbd[41038]: read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer Mar 10 19:16:28 seibercom smbd[41139]: [2006/03/10 19:16:28, 0] lib/util_sock.c: read_data(529) Mar 10 19:16:28 seibercom smbd[41139]: read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer Mar 10 20:20:30 seibercom smbd[41287]: [2006/03/10 20:20:30, 0] lib/util_sock.c: read_data(529) Mar 10 20:20:30 seibercom smbd[41287]: read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer The message will inclement ad infinitum when the system is idle. The client referenced is a WinXP Pro machine. This message only references one machine although there are other ones on this net. There does not appear to be any problem with the other machines that I am aware of. This behavior did not occur in the previous version of Samba. What can I do to correct it? Thanks! -- Gerard [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba using wrong IP address
I recently posted about a problem that I was experiencing after updating Samba. This is the output that I was getting: smbclient -L boss -U username%password timeout connecting to 192.158.0.4:445 timeout connecting to 192.158.0.4:139 Error connecting to 192.158.0.4 (Operation already in progress) Connection to boss failed It has just occured to me that the IP address is wrong. It should be 192.168.0.4 not 192.158.0.4 (notice the 158 instead of the 168 notation), I have no idea why it suddenly started using this IP address. My hosts file looks correct. Where else could I look for the solution for this problem? -- Gerard Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Problems with Samba after update
I am using Samba on a FreeBSD 5.4 machine. I just updated to the newest version of Samba (3.0.21b,1) available in the ports system. The old version was working fine, but since there were a number of ports that I had that were out dated, I simply updated them all. The problem is that Samba does not appear to be working correctly now. I can access the FreeBSED machine from any of the WinXP machines without incident. However, the reverse is not true. I have tried running the following command which produces this output: smbclient -L boss -U username%password timeout connecting to 192.158.0.4:445 timeout connecting to 192.158.0.4:139 Error connecting to 192.158.0.4 (Operation already in progress) Connection to boss failed Absolutely nothing has changed other than the updating of Samba and a few other ports -- mostly KDE. The WinXP machines are untouched. There is no new firewall involved, etc. -- Gerard Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error after updating Samba
to client. -1. (Broken pipe) [2006/02/24 11:05:37, 0] lib/util_sock.c:write_data(557) write_data: write failure in writing to client 192.168.0.4. Error Broken pipe [2006/02/24 11:05:37, 0] lib/util_sock.c:send_smb(765) Error writing 4 bytes to client. -1. (Broken pipe) [2006/02/24 12:41:43, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 13:13:44, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 13:45:44, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 14:17:46, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 14:29:56, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 15:07:57, 0] lib/util_sock.c:read_data(529) read_data: read failure for 4 bytes to client 192.168.0.4. Error = Connection reset by peer [2006/02/24 15:10:25, 1] smbd/service.c:make_connection_snum(693) I have no idea why this upgrade is causing this problem. However, if I cannot correct it, I will be forced to downgrade to the older version of Samba. Thanks! -- Gerard Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Usernames & Passwords
Jean-Jacques Moulis <[EMAIL PROTECTED]> > On Sat, 04 Feb 2006 07:50:10 -0500 Gerard Seibert <[EMAIL PROTECTED]> wrote: > > GS> Using the following command, I can access a share on one of the > WinXPmachines: > GS> smbclient //SERVER/SHARE -u NAME%PASSWORD > GS> I now find that I can also access the share using an incorrect 'NAME' or > GS> 'PASSWORD' or both. In fact, I can just use an incorrect 'PASSWORD' with > GS> no name, and I can still access the share. > GS> Obviously, something is configured wrong on the WinXP machine, but I am > GS> not sure what. Perhaps someone might have a suggestion. > > Your XP machine is using "Simple file sharing"! > nothing else is available in XP Home Edition! > > On XP pro revert to classic sharing by turning off "simple file sharing" in > Folder options > Thanks, that corrected the problem. In fact, it also corrected the problem I was having trying to run the command: smbclient -L SERVER That use to always produce an error. Now it works correctly. d:-) -- Gerard Seibert [EMAIL PROTECTED] "Be creative, invent a perversion." Anonymous -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Usernames & Passwords
I thought I had posted this previously, but I cannot seem to find any record of it. I am using Samba in a mixed network (WinXP and FreeBSD 5.4). There is no domain involved. Using the following command, I can access a share on one of the WinXP machines: smbclient //SERVER/SHARE -u NAME%PASSWORD I now find that I can also access the share using an incorrect 'NAME' or 'PASSWORD' or both. In fact, I can just use an incorrect 'PASSWORD' with no name, and I can still access the share. Obviously, something is configured wrong on the WinXP machine, but I am not sure what. Perhaps someone might have a suggestion. Thanks! -- Gerard Seibert [EMAIL PROTECTED] The boor is of no use in conversation. He contributes nothing worth hearing, and takes offense at everything. Aristotle, c. 340 b. c. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbclient failure
= 0 (0x0)
gettimeofday({1138105768 991816},0x0)= 0 (0x0)
socket(0x2,0x1,0x0) = 5 (0x5)
fcntl(5,F_GETFL,0x0) = 2 (0x2)
fcntl(5,F_SETFL,0x6) = 0 (0x0)
connect(0x5,{ AF_INET 0.176.5.8:0 },16) ERR#36 'Operation now in
progress'
nanosleep({0 1000}) = 0 (0x0)
connect(0x5,{ AF_INET 0.176.5.8:0 },16) ERR#56 'Socket is already
connected'
fcntl(5,F_GETFL,0x0) = 6 (0x6)
fcntl(5,F_SETFL,0x2) = 0 (0x0)
setsockopt(0x5,0x6,0x1,0xbfbfd414,0x4) = 0 (0x0)
write(5,0x8148000,72)= 72 (0x48)
gettimeofday({1138105769 6629},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
write(5,0x8148000,183) = 183 (0xb7)
gettimeofday({1138105769 8057},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 9076},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x55) = 85 (0x55)
break(0x817e000) = 0 (0x0)
break(0x819e000) = 0 (0x0)
write(5,0x8148000,170) = 170 (0xaa)
gettimeofday({1138105769 11181},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 12214},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x10e)= 270 (0x10e)
read(0x6,0x8144630,0x8) = 8 (0x8)
read(0x6,0xbfbfd090,0x10)= 16 (0x10)
write(5,0x8148000,274) = 274 (0x112)
gettimeofday({1138105769 15963},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 17535},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x7e) = 126 (0x7e)
write(2,0x8144500,65)= 65 (0x41)
write(5,0x8148000,78)= 78 (0x4e)
gettimeofday({1138105769 19249},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 20273},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x30) = 48 (0x30)
write(1,0x8168000,1) = 1 (0x1)
write(1,0x8168000,30)= 30 (0x1e)
write(1,0x8168000,30)= 30 (0x1e)
write(5,0x8148000,125) = 125 (0x7d)
gettimeofday({1138105769 22487},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 23506},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x40) = 64 (0x40)
write(1,0x8168000,1) = 1 (0x1)
write(1,0x8168000,29)= 29 (0x1d)
write(1,0x8168000,30)= 30 (0x1e)
write(5,0x8148000,125) = 125 (0x7d)
gettimeofday({1138105769 25813},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 26855},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x40) = 64 (0x40)
write(5,0x8148000,39)= 39 (0x27)
gettimeofday({1138105769 28227},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e000,0x4) = 4 (0x4)
gettimeofday({1138105769 29164},0x0) = 0 (0x0)
select(6,{5},0x0,0x0,{20 0}) = 1 (0x1)
read(0x5,0x817e004,0x23) = 35 (0x23)
break(0x817e000) = 0 (0x0)
close(5) = 0 (0x0)
exit(0x0)
process exit, rval = 0
Perhaps someone might notice something obvious here.
--
Gerard Seibert
[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error returning browse list: NT_STATUS_OK
Adam Nielsen <[EMAIL PROTECTED]>
> > Using incorrect names and or passwords produces the exact same output.
> > That does seem strange.
>
> I suspect in that case that for whatever reason you're connecting to XP
> with the wrong username. If your machine is on a domain, try using
> "-U DOMAIN\\username" instead.
>
> > What do you mean " run \\Gerard" from within XP"?. How do I do that.
>
> Go to the Start menu, choose Run, and type in "\\Gerard". If that
> works, open a Command Prompt and type in "net config workstation" -
> this should tell you what your username is, which should be the same
> one you use with smbclient.
>
> Cheers,
> Adam.
This is the output from that command:
Computer name \\BUDMAN
Full Computer name BudMan.SEIBERCOM.NET
User nameGerard Seibert
Workstation active on
NetbiosSmb ()
NetBT_Tcpip_{DA74D62E-27F2-4C87-95C3-C94C4FDD1173} (0007E9EAF552)
Software version Windows 2002
Workstation domain WORKGROUP
Workstation Domain DNS Name (null)
Logon domain BUDMAN
COM Open Timeout (sec) 0
COM Send Count (byte)16
COM Send Timeout (msec) 250
The command completed successfully.
Does this give you any clues?
--
Gerard Seibert
[EMAIL PROTECTED]
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error returning browse list: NT_STATUS_OK
Adam Nielsen <[EMAIL PROTECTED]> > > smbclient -L GERARD -U gerard > > Error returning browse list: NT_STATUS_OK > > > What am I doing wrong and how do I correct it? > > It looks like a possible permissions problem on the XP box. What > happens if you run "\\Gerard" from within XP? Also if you put in a > wrong username and/or password with smbclient, what errors do you get? > > Cheers, > Adam. Using incorrect names and or passwords produces the exact same output. That does seem strange. What do you mean " run \\Gerard" from within XP"?. How do I do that. Thanks! -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbclient not displaying shares
Eric Hines <[EMAIL PROTECTED]> > At 01/03/06 05:48, Gerard Seibert wrote: > >I have just recently installed Samba. I have two WinXP Pro machines > >networked to a FreeBSD 5.4 computer. The Printer is connected to one > >of the WinXP machines currently. > > > >This is the output of the 'smbclient' command. > > > >smbclient -U user-name -L winxp > >Password: > >Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] > > > > Sharename Type Comment > > - --- > >Error returning browse list: NT_STATUS_OK > >Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] > > > > Server Comment > > ---- > > > > WorkgroupMaster > > ---- > > > >As you can see, nothing is listed. > > > > Does testparm give you any hints? > > Eric Hines Nothing at all. I created the file with SWAT; therefore, I would assume the syntax was correct. I have no idea what is wrong. I have Googled and found others with this problem, but no concrete solution to it. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbclient not displaying shares
I have just recently installed Samba. I have two WinXP Pro machines networked to a FreeBSD 5.4 computer. The Printer is connected to one of the WinXP machines currently. This is the output of the 'smbclient' command. smbclient -U user-name -L winxp Password: Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment - --- Error returning browse list: NT_STATUS_OK Domain=[winxp] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment ---- WorkgroupMaster ---- As you can see, nothing is listed. This is my smb.conf file. It is rather simple. # Samba config file created using SWAT # from 216.45.217.148 (216.45.217.148) # Date: 2006/01/02 14:44:49 [global] log file = /var/log/samba/log.%m load printers = No show add printer wizard = No domain master = No ldap ssl = no valid users = @wheel admin users = @wheel write list = @wheel hide dot files = No [BS-Web] comment = BeerStud 'htdocs' dir path = /usr/local/www/beerstud/htdocs valid users = force user = XXX force group = XXX read only = No [SC-Web] comment = Seibercom 'htdoc' dir path = /usr/local/www/seibercom/htdocs force user = XXX force group = XXX read only = No [orivate] comment = Private Directory path = /usr/home/private force user = XXX force group = XXX read only = No [cgi-bin] comment = CGI-BIN Directory path = /usr/local/www/cgi-bin force user = XXX force group = XXX read only = No [Send] comment = DADA Scheduled Mail Directory path = /usr/home/ges/.dada_files/.send force user = ges force group = ges read only = No create mask = 00 force create mode = 0666 [dada-log] comment = DADA Logs path = /usr/home/ges/.dada_files/.logs read only = No [config-l] comment = config files usr-local-etc path = /usr/local/etc username = @wheel, @user, root valid users = @wheel, @user, root admin users = @wheel, @user, root write list = @wheel, @user, root read only = No All of the share do show up in the Windows Network. What am I doing wrong here. Ciao -- Gerard [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Connection with WinXP Error
I have Samba 3 (latest version) installed on a FreeBSD 5.4 system. I seem to be getting error messages in my log file, etc. that I am unable to decypher. I tried running this command: smbclient -U% -L localhost and this was the output: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.20b] tree connect failed: NT_STATUS_LOGON_FAILURE This is the log file output: log.127.0.0.1 [2006/01/01 12:09:36, 0] smbd/service.c:make_connection_snum(575) Can't become connected user! The following is the [Global] section of my smb.conf file: # Samba config file created using SWAT # from 216.45.217.148 (216.45.217.148) # Date: 2005/08/21 11:05:15 # Global parameters [global] lanman auth = no log file = /var/log/samba/log.%m max log size = 50 load printers = no preferred master = no local master = no domain master = no dns proxy = no wins server = 192.168.0.2 ldap ssl = No valid users = [snip] admin users = [snip] netbios name = budman restrict anonymous = no max protocol = NT server signing = Auto security = user What should I do to correct this problem. I believe that this failure is one of the reasons I cannot get KDE to properly access my WinXP machine. -- Gerard [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] permission denied from winxp box to samba share.
On Friday, July 08, 2005 11:58:42 AM Jason <[EMAIL PROTECTED]> wrote: >trying to set up a totaly anonymous share for users on a linux box with samba >3.0.10 point to a dir on my hard drive that looks like >drwxr-xr-x 2 root root 4096 Jul 7 22:39 sambashare > >in my smb.conf, for this dir, I have > >[globalshare] > path = /usr/local/share/sambashare > read only = No > guest ok = Yes > guest only = Yes > guest account = nobody > writeable = yes > >windows users can see the share, but cant write to it.. they get "permission >denied" in the log, I see > >[2005/07/08 11:52:42, 1] smbd/service.c:make_connection_snum(648) > xp-01 (192.168.4.49) connect to service globalshare initially as user nobody >(uid=65534, gid=65534) (pid 17680) > >but thats it. > >Jason > ** Reply Separator ** Saturday, July 09, 2005 6:41:42 AM Check the file permissions on that directory. I had a similar problem. I changed the permissions to 0777 and everything worked fine. -- Gerard E. Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Files missing when using windows XP and samba
On Tuesday, July 05, 2005 12:50:04 PM Stuart Bailey <[EMAIL PROTECTED]> wrote: >Hi, >I am using Fedora Core 3 as a server for both Unix (Solaris and HPUX) and >Windows Xp clients. The Unix clients view the files through an NFS v3 share, >and windows client use samba (3.0.8-0.pre1.3). >When looking at a directory from the server, or from a Unix client, I can see >132 files. However, from the Windows client, I can only see 65 files. There >appear to be nothing special about the files names (we have already removed >spaces etc from the filenames incase they caused a problem). >If I mount the samba shares via smbfs on the server (to a new mount point), I >can see all 132 files, so I suspect the problem is not samba. >I have checked the file permissions, and although they have various owners, >all permissions are 666. There seems to be no consistency between files that >are missing. >I have tried a number of different Xp machines and they all exhibit the same >symptoms. > >Any ideas or suggestions would be appreciated. > >Many thanks > >Stuart. > >-- >--- >Stuart Bailey BSc (hons) CEng CITP MBCS > LinuSoft (Proprietor) > Linux Specialist > (01953) 601294 > (07778) 383739 > http://www.linusoft.co.uk > ** Reply Separator ** Tuesday, July 05, 2005 4:38:58 PM I have no idea if this would make any difference or not. On your WinXP machines, when you open a network folder, try clicking on the entry on the tool bar. Then open the tab. Make sure that the show hidden and system files option is checked. It is worth a try anyway. -- Gerard E. Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Unable to write to Samba Share from WinXP
Samba 3.014a I have three computers networked together. Two are WinXP Pro and one is a FreeBSD 5.4 running Samba. I cam use 'smbclient' to exchange files between the computers. However, when I attempt to use the WinXP machines to send a file to the Samba machine I receive an error message. This is the usual message: *** Access Denied Make sure the disk is not full or write protected and that the file is not currently in use. *** This is the smb.conf file. # Samba config file created using SWAT # from 127.0.0.1 (127.0.0.1) # Date: 2005/07/02 19:36:46 # Global parameters [global] server string = Samba lanman auth = No log file = /var/log/samba/log.%m max log size = 50 preferred master = No local master = No domain master = No dns proxy = No wins server = 192.168.0.3 [homes] comment = %u's Home Directory path = /usr/home/%u admin users = gerard, ges encrypt passwords = Yes guest ok = No map archive = Yes map hidden = Yes [htdocs] comment = BeerStud 'htdocs' dir path = /usr/local/www/data/beerstud/htdocs guest ok = No map archive = Yes map hidden = Yes [ges] comment = GES Directory path = /usr/home/ges read only = No guest ok = No map archive = Yes map hidden = Yes [canon] comment = Canon S630 on Gerard path = //gerard/CanonS63 printable = Yes printing = lprng print command = lpr -r -P'%p' %s lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j lppause command = lpc hold '%p' %j lpresume command = lpc release '%p' %j queuepause command = lpc stop '%p' queueresume command = lpc start '%p' printer name = canon I cannot understand what the problem is. I would appreciate any assistance someone could afford me. -- Ciao Gerard E. Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error Msg in log file
I have Samba 3.0.14a installed. In the log file I have this entry: [2005/06/28 19:12:03, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Broken pipe [2005/06/28 19:12:03, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 4 bytes to socket 24: ERRNO = Broken pipe [2005/06/28 19:12:03, 0] lib/util_sock.c:send_smb(647) Error writing 4 bytes to client. -1. (Broken pipe) [2005/06/28 19:18:26, 1] smbd/service.c:make_connection_snum(642) gerard (192.168.0.3) connect to service gerard initially as user gerard (uid=1002, gid=1002) (pid 19989) [2005/06/28 19:18:37, 1] smbd/service.c:close_cnum(830) gerard (192.168.0.3) closed connection to service gerard I am experiencing a problem with WinXP crashing when I attempt to reach a share on my FreeBSD 5.4 computer that is running Samba. Could someone tell me what the problem is here, or what I should be lookng. -- Gerard E. Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] WinXP Crashes
I have Samba 3.0.14a installed on a computer running FreeBSD version 5.4. I also have two other computers that are running WinXP with all updates, service packs, etc. This is a very simple configuration with no domains, etc. Now, when I open "My Network Places" and hover the mouse over an icon for the Samba network or one of its shares, within a few moments Internet Explorer will crash. This is the message: Windows Explorer has encountered a problem and needs to close. I then get the option of sending a report to Microsoft about the problem. The Dr. Watson program does record the incident, but I lack the skill to be able to decipher the error file. Has anyone else experienced this sort of behavior or have a suggestion as to how I might correct it? -- Thanks Gerard Seibert [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
