similar to: Going insane (can't logon from Windows)

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

Mates, I'm trying to solve some log errors I getting. I have samba 3.0.7 installed on Suse 9.0. It has been happening intermittently for several months. I don't know if this is XP client related or what. Any thoughts: The errors are: Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] lib/util_sock.c:get_peer_addr(1000) Feb 9 20:00:33 skyline smbd[14408]: getpeername

Hi. Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have added will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont

Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have add will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont understand:

I have a laptop that I need to be able to connect to my samba shares with its wired connection and its wireless connection. It works fine when connecting from the wired ethernet connection but it stops working once I disable the wired connection and connect to the wireless network (both networks are on the same subnet). The IP address for the wired connection is 192.168.1.112

Hello, I tried to google this, but haven't found anything really helpful so far. I get stuff like this at one Samba-3.0.9-Domain-Member-Server: > [2005/03/06 13:30:47, 1] smbd/service.c:make_connection_snum(647) > fre2003 (192.168.86.11) connect to service users initially as user fre (uid=1006, gid=1000) (pid 31447) > [2005/03/06 13:31:57, 1] smbd/service.c:close_cnum(835) >

I'm finally getting somewhere in setting up my FreeBSD PDC. I try and login via my XP client and now it gives me this odd message. "Cannot login because a duplicate user already exists on the network. Please goto control panel and system and change your computer name." Sorta paraphrased there, perhaps off by a word or two but that's pretty much what it tells me. I'm just

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

Hello all, I haven't been able to solve an issue I am having when copying over data from a Windows box to a Samba share. I have found others with the same issue and I have made some configuration changes to try and solve the issue but the issue is still lingering. I want to migrate off my old Windows box but until I solve this issue I am I cannot move forward. Please let me know if

Hi, This is more of a FYI than a request for help. thanks. 8) I upgraded our 3.0.x servers to 3.0.9 due to bugs which we were running across. This happened at about 7AM, a few hours before anyone starts arriving at work. The mornings are one of the most taxing times on our servers as everyone is loading profiles, and they review what lastnights image / video rendering farm

Hi, In the last a couple of weeks, Eric helped me fixed a couple of my new samba 3.0.5 running on HP-UX 11i hang issues. Right now, people still experience slowness when they run some applications on the samba shares OR recursive list directories on the samba shares. There was not a lot of errors in the individual log files. However,there are some errors in log.smbd and log.0.0.0.0 file. 1)

Dear all, I have a SuSE9.1 box running as a file server with mp3's on it. The /var/log/messages log file is recording the following errors which I don't understand and perhaps you could assist me: Nov 17 11:25:05 mp3-nrg smbd[7903]: [2004/11/17 11:25:05, 0] lib/util_sock.c:get_peer_addr(975) Nov 17 11:25:05 mp3-nrg smbd[7903]: getpeername failed. Error was Transport endpoint is not

Hi folks, I am having a weird problem that I just recently noticed on this particular server runnng Samba 3.0.10 on Fedora Core 3 and am hoping someone could shed some light on this. We're using tdb for our backend database. The user "nsu" is a member of unix group admin. The unix group admin is mapped to "Domain Adminstrators". This works OK, in that when logging in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1. Is there a reference that will help in the identification of Samba errors? 2. Can anyone identify these errors? I' @ log level = 6 and I get: Mar 15 10:58:01 enigma smbd3[4271]: [2004/03/15 10:58:01, 0] lib/util_sock.c:get_peer_addr(952) Mar 15 10:58:01 enigma smbd3[4271]: getpeername failed. Error was Transport endpoint is not connected

I have a similar error, I can us XP workstation ad domain members, and they even use the shares, but two or threes times per day the connection resets, and I have to kill the smbd and start it again (only restart does not work). Take look at my LOG. Any idea? [2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/10/04

Hello List, I have a bit of a strange problem with an OS 10.3.3 XServe (Samba 3.0.2) that I've inherited from a previous sysadmin ;). It's a bit hard to describe but I'll do my best and include applicable log files and the smb.conf. Ok, first of all this machine is bound to our Active Directory domain and authenticates users there (security = ads). It uses the Windows 2000 DC

Hello experts After a total panic last weekend, now my LDAP+Samba is working fine, apparently. However, in my syslog, each one minute, still occurring errors like this: Apr 25 08:47:21 myserver smbd[10245]: [ID 702911 daemon.error] [2005/04/25 08:47:21, 0] lib/util_sock.c:set_socket_options(202) Apr 25 08:47:21 myserver smbd[10245]: [ID 702911 daemon.error] Failed to set socket option

hi folks, i?m using samba 3.0.2a. in my system messages.log are some entrys like this Mar 16 11:59:29 lraprintbak smbd[1857]: =============================================================== Mar 16 11:59:29 lraprintbak smbd[1857]: [2006/03/16 11:59:29, 0] lib/fault.c:fault_report(37) Mar 16 11:59:29 lraprintbak smbd[1857]: INTERNAL ERROR: Signal 11 in pid 1857 (3.0.2a-SUSE) Mar 16 11:59:29

Hello, I am new to Samba and to this mailing list so please excuse my ignorance. I have a situation where when a user syncs his Desktop PALM V PDA to his Windows 2000 PRo PC - user account being a Samba mapped drive, the Server crashes...any clues??? endpoint is not connected Jan 4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0] lib/util_sock.c: get_peer_addr(1000) Jan 4 16:42:06

Howdy, My samba works pretty well I should say. I access my linux box's shares from 3 different XP machines quiet nicely. But I just noticed today that Im getting quite a bit of errors dumping in, and wondered A) if it may be affecting the performance of Samba, or B) if I could maybe fix them through some simple configuring, etc. They're pretty unchanging, and the interval is... not