similar to: 3.0.22-solaris10 - Please help !

Displaying 20 results from an estimated 9000 matches similar to: "3.0.22-solaris10 - Please help !"

2006 Jun 12
1
3.0.22 on solaris10 socket error.
Hi all, I've built samba 3.0.22 on solaris10 sparc with ldap support using thes config parameters : ./configure --prefix=/opt/samba \ --localstatedir=/var/lib/samba \ --enable-socket-wrapper \ --disable-cups \ --with-privatedir=/etc/samba/private \ --with-piddir=/var/run \ --with-configdir=/etc/samba \ --with-logfilebase=/var/log/samba \ --with-ldap \ --with-ads=no \ --with-automount \
2006 Mar 06
3
Problem Accessing Samba Server from Windows
Hi, I'm having a problem accessing my samba server from Windows. The problem occurs every time I try to browse to it on either XP or 2003 Server. The error message I get is: "\\Zeus 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 permissions. The account is not authorized to log in
2006 Mar 07
3
[Samba Version 3.0.20b-3.4-SUSE]: WinXP-Error writing to share
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
2009 Oct 15
2
can not access samba drive on Redhat ES 4
Hi, Our samba server is running Red Hat Enterprise Linux ES release 4 (Nahant Update 4) with samba version: samba-3.0.33-0.17.el4. We like to authenticate all the users with our Primary Domain Controller wnidows 2008. Some users keep getting asked to enter username and password. Even with the correct password, still can't access the drive. The strange thing is that some users are
2009 Jun 25
1
Windows 7 RC1 Build 7100 Cannot Connect to Samba Shares w/Winbind
I'm doing some testing with Win7 RC1 and I'm having an identical problem with two CentOS servers (5.2 and 5.3) both running Samba 3.0.33 where I cannot authenticate. Both servers are authenticating with Winbind to an AD DC. I have a third CentOS 5.2 server with Samba 3.0.33 shares that does not use Winbind which has no problems. This pops up in smbd.log: (.200 is wireless and .184 is my
2004 Sep 08
1
Samba performance issue
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)
2006 Jan 05
3
my serwer hngs :(
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]
2005 Apr 23
1
Urgent: problem with SAMBA+LDAP
Greetings Experts! Sorry for my poor english, but I?m inside of a terrible nightmare!!! I?m using Samba+LDAP has about 2 months ago without problems, but in the last 4 hours, the system is absolutelly unstable. I couldn?t upgrade or patched anything. The problem simply has appeared. Principally system characteristics: - Sun Fire V880 running Solaris 9 - openldap-2.2.23 - nss_ldap-232 -
2008 May 22
2
Strange samba error
Hello, We use samba to backup some (rather large) sql databases. Lately we ocasionally are getting fail reports, as in the file could not be written, and windows generating an error 64: "The specified network name is no longer available" While going trough the logs, i can see the following error (sorry for the long output): ----- [2008/05/19 01:14:46, 0]
2006 Oct 20
1
user can't logon to specific computer: creds_server_check failed
A few computers -- two or three -- are very spotty about letting people log on. It seems -- and this could be off-base -- that they'll let anyone log on once, but will require a reboot before you can log on again. Sometimes, logging on works fine, though. There really appears to be little rhyme or reason to what happens. In the Samba logs, I'm getting: [2006/10/20 08:08:14, 0]
2008 Apr 14
2
corrupt files... oplocks?
Suddenly in the past week we have been having users who share excel files via our Samba complain that the file has become corrupt, and also some database files (Orcad .tdb database files). Fortunately there has in each instance been a good copy in the .recycler... so far. I came across some docs and threads in the net about oplocks. I did find an error in the samba log: [2008/04/14 10:19:05,
2007 Apr 05
2
Samba kills network.
When i try to swap files between disks on my server using samba i get errors: then windows reports "The specified network name is no longer available". Sometimes the copies are fine other times files just wont copy. Hardware checks out fine. Ive even replaced the network cable between server and switch thinking that might be causing the problem. Ive included a ethereal cap of the
2008 Apr 30
1
samba in NATed network
We have about 300 users distributed on different vlans using private ip network spaces, and sharing one single public IP when going out to the Internet. Our samba (3.0.24) server has a pulbic IP and is running as a primary domain controller. All clients receive Sambas's public IP as their WINS server. I am able to join the domain but samba stops responding sporadically. Looking at the
2008 Jan 31
3
Connection problems, laptop to server
I'm having problems connecting from my laptop, and the logs show lib/util_sock.c:send_smb(769) Error writing 116 bytes to client. -1. (Broken pipe) : 1 Time(s) lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.91. Error Broken pipe : 1 Time(s) libsmb/smb_signing.c:srv_check_incoming_message(737) srv_check_incoming_message: BAD SIG: seq 2 wanted
2008 Feb 01
1
PDC: random problems, especially NETLOGON script not always loading
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.
2009 Nov 06
2
Vista clients having Issues Copying files from Samba Server
Hello, I'm running samba-3.0.33 (samba-3.0.33-3.15.el5_4) On Centos 5.4 and some files have issues being copied from the Samba server to the Vista (Service Pack 1) clients local disk via Windows Explorer, copying too the Samba server also has no issues and copying via the CMD prompt has no problem, I'm getting the following errors 1. Invalid MS-DOS Function
2001 Dec 13
4
Severe problem with Samba
Dear All, we are experiencing severe problems with Samba 2.2.0 (with quota support) running on a dual processor (400MHz) Sun E450 running Solaris 2.7. This is used as a central file server for student diskspace, accessed by approx 1200 PCs running NT 4. Up until recently we experienced some, what we assume to be, loading issues with connections during the middle of the day being slow.
2005 Nov 20
1
Lots of "write_data: write failure in writing to client" and "Error writing 4 bytes to client. -1"
Last week we installed Samba 3.0.20b on one of our servers, worked fine and does it's job well. But today the load was rising due two smbd processes taking up all cputime. While looking for hints on what was going on the logfiles show two types of errors (I don't know at this time if it has anything to do with the load spike): lib/util_sock.c:write_data(554) write_data: write failure in
2002 Mar 08
2
Re: 'Network Busy' - indeed (Gustav Tresselt)
> 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
2006 Jun 14
0
Samba write errors, broken pipes and client lockups
Over the last few weeks I've had problems using Samba on a FreeBSD. Windows XP clients (that's all I have) would experience intermittent long delays (lockups, freezing) when accessing the samba shares using Windows Explorer or any other applications. This occurred both directly when browsing the network neighborhood, and when accessing the share through a letter drive mapping.