similar to: authentication against win2k3 server

Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 - previously running Samba 2.2.8. It starts up and SWAT confirms that it is running and I am using the same smb.conf but I am unable to connect to a share via PC. Message "\\s080 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access

Christoph Scheeder asked > > Hi, > 1.) is this a new installation No, it was Mandrake 8.2 box, but was recently upgraded to Mandrake 10. > 2.) if not what was changed when the failure first occured? Thing were running fine, at least that's what it appeared like. Then sporadically people started getting authentication error when logging into their IMAP mailboxes. Next the

I've been having some odd problems with samba and it's libsmb/nmblib parts. It seems to be trying to transmit data to the .63 of my netblock, i.e. the IP of the machine would be 24.240.60.20, it'd be trying to transmit to 24.240.60.63. I've changed IPs about 15 times since, and it does it to each different block I change to. If the IP of the local machine got changed to

I'm receiving the following errors in my system logs... <Log> Jan 24 11:25:06 localhost nmbd[1276]: [2011/01/24 11:25:06.840799, 0] libsmb/nmblib.c:839(send_udp) Jan 24 11:25:06 localhost nmbd[1276]: Packet send failed to 10.40.0.124(138) ERRNO=Operation not permitted Jan 24 14:01:59 localhost nmbd[1276]: [2011/01/24 14:01:58.622688, 0] libsmb/nmblib.c:839(send_udp) Jan 24

I'm not really sure if this is a samba problem or a linux network problem, I have checked the newsgroups and ive seen this question pop up a few times, w/o answer. Here is the issure I am having, whenever the i do a smbclient -L hostname for this particular server I get the following message in the logs: open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot

Im having some trouble getting, or even finding out if this works. I have read through the samba by example and all the docs i can get my hands on and i cant get this to work. Maybe it isn't supposed too.... I have setup samba under RHEL4 QU1 to authenticate to AD. I am just using samba to authenticate users for login purposes. It works fine and dandy until my primary AD box goes down. I

Before I lay out the problems I am currently suffering from let me describe my environment: Dell OptiPlex GX270 2.6Ghz 512MB Ram RedHat Linux Fedora Core 3 with all current updates. Samba compile is version 3.0.20 stable. Uname -a: Linux theo.hq.navis.net 2.6.12-1.1378_FC3 #1 Wed Sep 14 04:24:31 EDT 2005 i686 i686 i386 GNU/Linux Everything was running fine until my last YUM update.

I am having trouble with one of my samba PDC's. It does not recognize itself as the domain master browser even though it is set to be so. I can not add machines to this domain and I suspect this is why. Has anybody seen this or know what causes it? Notice this: DOMAIN_ALBANY(3) current master browser = ALBANY_PDC DOMAIN_NYC(2) current master browser = NYC_PDC

Hello again folks, I give up trying RPC. I'm trying to avoid update samba package of my Ubuntu 9.04 server (amd64) so I decided to try ADS again. This way I'm using the following versions: krb5-user 1.6.dfsg.4~beta1-5ubuntu2 samba* 2:3.3.2-1ubuntu3.1 I'm having problem joining a AD domain. I suspect there is something related to how my company's directory was setup and I

Hello, I'm having a problem logging in to the Samba domain from an XP machine. The machine is added to the domain but after reboot I can't login. I've done the signorseal registry hack but I'm still not able to login. The error I get when logging in is this: "Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or

Hello list, i want to auth. squid against a win2000 AD group to get internetaccess using winbind. First i had installed samba.2.2.5 I configured smb.conf: [global] workgroup = CAMPUS server string = Samba Server hosts allow = 149.250. 212.68. 192.168. 127. security = domain password server = ATHENA encrypt passwords = yes socket options = TCP_NODELAY SO_RCVBUF=8192

I have been trying in vain to get ADS domain authentication working. I can't figure out what is wrong and have read the docs and looked through the mailing lists. I'm not sure why better documentation hasn't been written on the web site for the ADS feature since it's pretty spectacular to be able join a Samba server natively to an AD domain. I have successfully joined the samba

I'm hoping someone can give me a hand in figuring out this problem, I have seen several other similar problems in searching, but nothing that exactly matches what I am seeing here. I have recently migrated a client from a Samba server running 2.2.7 (Redhat 9) to 3.0.2 (Fedora 1). The samba installation is running as a PDC for 5 Win XP workstations and was working perfectly prior to the

The only thing related to 'addresses' in my /etc/samba/smb.conf file is a "hosts allow": hosts allow = 192.168.3.0/24 127.1 I'm going to ignore the 'local hosts case, as if I solve the other, the localhost case may get solved by inference. I thought the 'hosts allow' would allow any host on the local 192.168.3.0/24 subnet. The hosts have no problems

Hi All, On my first internal NIC, Samba is working perfectly. On my new, second internal NIC, I am getting the following in my messages log: libsmb/nmblib.c:send_udp(793) Packet send failed to 192.168.254.255(138) ERRNO=Operation not permitted nmbd/nmbd_packets.c:send_netbios_packet(163) send_netbios_packet: send_packet() to IP 192.168.254.255 port 137 failed I though .255 was a reserved

Hi, It's a basic firewall question I guess. Perhaps someone of you has seen it. I've got I firewall setup meant for my samba server protection. The problem is it seems to block all broadcasts. The error message: [2004/09/22 17:43:47.572148, 0, pid=1505, effective(0, 0), real(0, 0)] libsmb/nmblib.c:send_udp(756) Packet send failed to 192.168.2.25(138) ERRNO=Operation not permitted

Hi ! I've set up a samba server (2.0.3-8) on a machine running RH 6.1. Everything works fine. Printing, smbclient and so on.. But when i try to login from a win95 client, it says "there's no domain server to confirm the password".. And when i look in the logs. ( .log ), it says: [1999/10/28 10:00:59, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69) process_login_packet:

I had a problem similar to my current one a week or so ago, and I was encouraged to upgrade from Samba 2.2.9 to 3.0.7, which I did. Now that I've completed that nightmare, the problem I initially set out to fix is still there, just different. Namely: I am trying to set up Samba 3.0.7 on a SuSE 9.1 box as an LDAP PDC whose only job will be authentication. Our LDAP server is on a separate

Hi everybody on the sambalist my server is running pretty ok now, but after examening my logs im trying to get rid of the last messages. 1) Tons of messages like this, ( i have 20 printers overhere ) log.smbd [2005/11/23 10:24:09, 0] printing/print_cups.c:cups_queue_get(790) Unable to get jobs for ipp://localhost/printers//usr/bin/lpq -P'pdfprinter' - printing is setup RAW,

Looking for a solution to this problem. I have Googled all over the place but haven't found a definitive answer. I have a Samba Server that ONCE was on a network where there was SECOND Samba Server with IP Address 192.168.20.3. Today, the FIRST server is on a network with an address range 10.0.0.0/255.255.255.0 and it has no way of finding that SECOND Server 192.168.20.3. However,