similar to: Authentication problems after upgrading to 3.0.23c

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

Hi all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server

Hi all hope you can help, I have a mixed XP / 2K client deployment, and the samba server is running as a PDC. On most machines I have no problems, but on 2 2K machines and 1 XP machine I'm getting the same behaviour every time I either try to write the file or execute a file, no matter whether I log on to the domain or which userid I log on as. I'm also running debian woody 2.4.19, and

I've been fighting with a samba install on top of a amd64 Ubuntu 10.4 system for a couple months now. I have a small flotilla of Windows systems running anything from Win 2000 up through Windows Server 2008. All save for the 2008 systems are setup with nightly NTBackup jobs with my samba server as the destination. The 2008 systems are running MS SQL and use the samba server as the

I've recently set up an Openfiler 2.2 system, with a few disks under md (RAID6), LVM on top of that, and formatted ext3. When snapshots are in use, large file transfers (transfers of large files, or transfers of many smaller ones) are disconnected - Leaving a Windows 2000 client with an error like 'The network resource is no longer available'. Re-trying works, but cuts out again

Hello list! Are there any known issues regarding samba3 - linux 2.6 kernels? I'm getting disconnects every 20 seconds or so, both via cifs and smbfs mounts. This occurs regardless of whether the connection is in use and sometimes leads to I/O errors (even doing 'ls' on a mounted dir). It is not consistent though, and seems to be triggered by high network traffic. When it is

Windows 98 client cannot print via samba to PrintPro printer "exported" via Cups/PrintPro on PrintPro/Samba server. "Exporting" with Cups on server node allows print drivers to be downloaded to Windows clients from the server. Any help or suggestions are greatly appreciated. Win98 node gim98.rsmas.miami.edu [129.171.97.21] connects to Samba 3.0.0-15 server "prima"

I appologize if this has been answered previously or if the answer is obvious. I have done the best I could searching through the mailing list archives and through google to see if I can find an answer to my problem. With that said, the problem is that whenever I use my connection to samba (3.0.23c on FBSD 5.4) from my Windows XP (Professional, SP2) machine I receive these errors: Sep 11

Good Day I having problems with the samba, when I go to add to a machine windows xp to the dominio some errors appear in messages log of the system, the machine windows xp enters in the dominio but they anypeople can make logons and is shown me an error saying that the dominio was not found on windows xp machine. The errors --- Nov 23 11:06:31 instituto smbd[17752]: getpeername failed. Error

Hello, I'm still testing Samba with security=ads. Everything runs fine atm., but when I logon I'm getting this in pc's log: [2009/05/07 13:17:58, 2] lib/access.c:check_access(406) Allowed connection from (10.255.255.7) [2009/05/07 13:17:58, 2] lib/access.c:check_access(406) Allowed connection from (10.255.255.7) [2009/05/07 13:17:58, 1]

Hi list, Since I've upgraded from Version 5.0 to 5.1 i have strange problems with samba. Since 5.1 the connection from a XP client to the samba server disconnect often, especially then i write a file to the share after some idle time. Some informations of my config. The Box is a Samba PDC for a little Windows Domain with a ldap backed. I used this config on Centos 4.x and 5.0 without

I've installed a samba PDC with ldap database, but I can't join the domain with my windows XP machines. I populated the Database with smbldap-tools. When I try to log in as Root in the log file is written: log.0.0.0.0 1 [2006/12/29 11:49:24, 0] lib/util_sock.c:get_peer_addr(1229) 2 getpeername failed. Error was Der Socket ist nicht verbunden 3 [2006/12/29 11:49:24, 0]

Debian Latest stable. Linux newton 2.6.18-4-686 Samba 3.0.24 PDC 3Com 3812 Gigabit switch (connection between WinXP client & server) Others connect through 3Com 3225 100 Mbit -> 3Com 3812 -> Server Windows XP SP2 fully updated. F-Secure client security (look down for firewall settings) In advance, thanks for reading this. Any suggestions are welcome! I'm having a hard time here.

Hi I have a samba server with tdbsam passwords, and a share, PROJECTS, which is accessed by various XP home clients, the usenames and passwords being manually synced to the samba ones (less than 10 users, and only 4 workstations). There is one win2K machine, which is a domain member. Subdirectories on PROJECTS have g+s set, so only users, who are members of specific Linux groups, have access to

Hi, anybody knows, what the last entry in this log mean?: [2004/11/07 16:51:50, 3] smbd/reply.c:rename_internals(3777) rename_internals: case_sensitive = 0, case_preserve = 1, short case preserve = 1, directory = ./Neu Textdatei.txt, newname = ./???.txt, last_component_dest = ???.txt, is_8_3 = 0 [2004/11/07 16:51:50, 3] smbd/dosmode.c:unix_mode(111) unix_mode(./Neu Textdatei.txt) returning

Heloo My server hangs up :((machine not only samba) I've upgrated my system. Now it is Gentoo 2005.1 - K 2.6.14 - Samba 3.0.20b Everything works exelent and much more faster now but sometimes it hangs up. The last hang up was when I have loged one user on w98 :( to domain. Only strange thing that I've found in logs are : : [2006/01/05 07:59:13, 0]

Hello mailing-list, this is my first post and i hope that you enjoy my very bad but sometimes funny english. My Problem is the following: First of all, my server-config: Samba Version 3.0.20b-3.4-SUSE on a SUSE Linux Enterprise Server 9 with Kernel 2.6.5-7.252-smp Now the problem is, that samba generally works fine, but it doesn't work to work with a special application directly on a

I'm hoping to get some guidance diagnosing intermittent smbd errors that have been cropping up in the last 2 months. They are sporadic, difficult to reproduce, and don't reveal much of a pattern so far except that the majority are generated by a couple of clients, although several clients appear to be affected. Typical symptom on the client is a hang when attempting to look at the share

Good day, this is new error for me can you help me please ? from log: [2004/12/01 12:45:44, 2] smbd/close.c:close_normal_file(270) podskalsky closed file Podskalsky/HALINatd/pribehy/vaic/dosly k vrcholu uz pod vrcholem 40 r.doc (numopen=0) [2004/12/01 12:45:44, 2] lib/access.c:check_access(324) Allowed connection from (192.168.1.54) [2004/12/01 12:45:59, 0] lib/util_sec.c:assert_gid(113)

Trying to upgrade from 3.0.14a to 3.0.23c. So far, things seem to be working, but the following entries appear in the smbd error log. The test machine is a domain client (server is still 3.0.14). The sids listed are exactly as they appear in the ldap tables. What makes them invalid? Anyone know. [2006/10/19 11:34:10, 1] passdb/pdb_interface.c:pdb_default_uid_to_rid(1227) Could not peek rid