similar to: Account not authorized to login from this station

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

I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23

Iam running Samba 2.0.10 on a FreeBSD 4.2 platform within a Windows 98/2k peer to peer network. Most of the time this system appears to be working very well with the file system nicely browsable by the client machines. Unfortunately, from time to time the following error appears within the log.smb: [2002/02/14 10:54:28, 3] lib/util.c:interpret_addr(1833) Get_Hostbyname: Unknown host. ed0

> I have a network that sporadically give 'network busy' errors. One morning > the workstations will all connect up fine and stay up throughout the days > work, yet the next day there is not one machine that can log on to the > network. It may run fine for two weeks, then bam, three days of no logins. > Yet the internet works fine. Could I copy my smb.conf file and rpm -e

It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,

Hi I'm looking for help in netbios-ssn problem we ecountered. Our server is HP UNIX 10.20, and samba is 2.0.7. recently, we can saw error message in syslog.log file: "netbios-ssn/tcp: accept: Resource temporarily unavailable" and, from log.smb, we can see beblow message: Failed to set socket option TCP_NODELAY (Error Invalid argument) [2003/11/08 03:56:54, 0]

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

Hello, I've been searching through the Samba archives attempting to find a resolution to intermittent Win2k -> Samba 2.2.2 for IRIX share failures. It seems that there have been numerous failures similar to mine reported with various versions of Samba and various OS's, but I've been unable to find a workable resolution. Intermittently when connecting to a Samba share from Win2k

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:

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

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

I've samba running an embedded linux system (2.6.x kernel with uClibc). I'= m trying to transfer some medium to large files (65-225 MB). I'm using simp= le windows explorer drag/drop to write the files to the embedded system. T= he file transfer dialog will show some progress then lock up for a few minu= tes. After this it reports with "The specified network name is no longer

Hi, I'm running samba 2.2.7 on redhat advanced server with approximately 40 win2k clients and having a serious problem with the clients. Intermittently the clients will lose their connection to the server for approximately 30 seconds. It's like the socket connection is being reset or something. Here's a sample output from a client log file: [2003/04/12 15:13:08, 0]

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) >

This is probably a hot topic, and if this has been beaten to the ground, forgive me. I'm not a regular part of the Samba community. Although I have been using Samba for years, I now have to use it in a corporate environment utilizing some of it's more modern features. Let me just say, that it's been several hours of testing/troubleshooting to get where I am now. (And I don't

Hi, Please, what does this message mean: "getpeername failed. Error was Transport endpoint is not connected"? I get the following in my log.smbd file each time I try to log to my samba domain from a Windows XP client: [2005/08/24 09:49:09, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/08/24 09:49:09, 0]

Good Afternoon, I have Samba 2.2.1a running on a SPARC Solaris 2.7. All of a sudden I'm having a problem with one PC mapping Samba drives. In the log file for this PC I get the following error messages: [2001/12/11 12:47:22, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2001/12/11 12:47:22, 0] lib/util_sock.c:send_smb(729)

Hello, I run a samba (v3.0.10) PDC and openLdap server on the same machine. They work fine, except sometimes the smb server cannot contact the ldap server. From a windows client, it looks like the server gets stuck, and it takes a few minutes before the shares are available again. In the /var/log/messages file, i get these error messages :

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