similar to: Solaris and W2K

Hello! Problem: Outbound data goes through default interface instead of specified, causing congestion. Question: How can I instruct samba to tell Solaris to SEND data through specified network interface? Detailed: I have a solaris filesserver with two network interfaces, hme0 and hme1. I'd like NFS to use hme0 and smb hme1. I intsruct samba to only listen for connections on the

Hi all, I am having an issue where my hme0 interface is always turning up and down with dhclient requesting a lease. I am thinking this could be the same issue described by Jeremy Chadwick on June 9th: http://lists.freebsd.org/pipermail/freebsd-stable/2013-June/073711.html Everything was fine on 8.2-STABLE and older versions. It was then upgraded directly to 9.0-STABLE

I run samba 2.0.6 on Sun ultra enterprise 2 server. Lately the logs have been filled with [1999/11/29 20:11:19, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [1999/11/29 20:19:31, 0]

Hello, I am running a mail benchmark test using smtp-source[1] with VM running postfix on Xen hypervisor. My system configuration is: uname -a -> Linux cadlab 3.1.10-1.19-xen #1 SMP Mon Feb 25 10:32:50 UTC 2013 (f0b13a3) x86_64 x86_64 x86_64 GNU/Linux I am observing a very high disk write usage by xenstored (some 5 Mbps) without even anything running on the VM. Is it normal? During test, I

Hello, I am running a mail benchmark test using smtp-source[1] with VM running postfix on Xen hypervisor. My system configuration is: uname -a -> Linux cadlab 3.1.10-1.19-xen #1 SMP Mon Feb 25 10:32:50 UTC 2013 (f0b13a3) x86_64 x86_64 x86_64 GNU/Linux I am observing a very high disk write usage by xenstored (some 5 Mbps) without even anything running on the VM. Is it normal? During test, I

Every once in a while a user cannot connect to one of two samba servers. Most of the time (but not always), if he waits 15 minutes to an hour, he can connect successfully. Sometimes he can connect to one server, but not the other, which have the same configuration. We are using authentication from the NT server. Samba version 2.0.3 The messages in the log file are are shown below. In this

> > > > If it is that then either the solaris send window or the > client receive > > window is too small. > > > > Or, we could go for a vastly less complex explanation - shout > is known to not > send at the correct rate. Don't use it. > > Mike <p>Hi all, I understand, what for a livestreamer can I take ? any references ? A network

Hello, I'm new to this list. The NT folk here, are concerned about some timeout errors and stuff that appear in their event viewer. They are building a case to convince management that unless these "samba" errors are fixed, we should move to NT file shares. I think this is a bad idea. Can anyone help me out here. We are running samba 2.0.6 (1st msg) and 2.0.5a (2nd err msg)

I've been prowling through the FreeBSD and Snort list archives in search of information on setting up snort on a FreeBSD bridge(4) that logs to a remote postgres box via a third interface (hme0) Snort is being started with the following command: /usr/local/bin/snort -A full -D -e -d -s -i fxp0 -c /usr /local/etc/snort.conf Where fxp0 and fxp1 are in the bridge output from sysctl:

Samba 3.0.23a Solaris 9 I have reecently upgraded my Samba server to the above version and joined an Active Directory domain. Since having achieved this I have been encountering a strange problem. On some of my printers the printing of banner pages is enabled. In some instances when a user submits a print job it prints with root as the owner on the banner page and not the user's who

I am currently running Samba 2.2.8a in a production environment on a Unix box with Solaris 8. I am hoping to migrate and upgrade to Samba 3.0.10 on a Solaris 10 box. I am however having difficulties joining the NT domain with my new (still test server). Initially I provided the administrator with the ip address and the netbios name of the samba server so that a trust account could be created.

Hello, I've looked through multiple mailing list archives and cannot find an answer to this problem, but have found many others who are having the same problem. I hope this list can help. I have a Solaris 2.7 server running Samba 2.0.5 with multiple interfaces: hme0: 172.17.5.56 public qfe0: 172.18.30.36 backup network qfe1: 192.168.30.36 private qfe3: 172.18.10.36 private I have Samba

Hi all, I don't make it a point to answer my own posts, but I thought this information would be useful: In researching the problem our client was having below, I found that there were two NT servers on the same subnet as my Unix server running Samba. Both these NT servers were "arguing" over who was the master browser for that network segment. Once the NT SysAdmin corrected the

Hi All, Samba 3.0.2a is installed on Solaris and works fine with windows NT clients, but it doesn't work with windows XP client which complains that the share path can't find. Here is the basic coniguration: workgroup = GLOBAL netbios name = test netbios aliases = test server string = test Samba 3.0.2a interfaces = hme0 bind interfaces only

On Mon, 2003-01-20 at 08:34, Daniel Knoll wrote: > Hi all, > > I understand, what for a livestreamer can I take ? any references ? for vorbis uses icecast2 and either ices2/oddcast etc, as they are tested more. > A network question: > If I decrease the MTU (on hme0 interface is 1500) maybe it can be a solution > for my problem with broken streams? ok, so it's solaris.

Hello, I have set up an IPSec tunnel to create a VPN. It works well, I can ping and telnet back and forth with no problems. I am, however, struggling to get Samba to work. The setup: Samba 2.0.7 running on Sparc Solaris 2.6 The VPN tunnel is between a OpenBSD 2.7 server and a Netopia R9100 router. The tunnel is negotiated using IKE. The server running Samba receives NetBIOS packets, I can see

Ok.. I've tried tweaking several settings on Samba (1.9.18p4) in order to try to keep it from killing several machines that get backed up weekly via Amanda (using smbclient). What always appears to happen is that for one reason or another, Samba is booking along copying files and then all of a sudden NT stops communication and smbclient ends up hanging forever (regardless of the keepalive

Hello all. I've set up a Samba server on a Sun E280 box running Solaris 8. The server is part of a domain. I am having some problems printing. I can setup the printers on the Windows NT workstations using the Add Printer wizard. However, when I try to print I get inconsistent results. After installing the printer the workstation has to be restarted (sometimes more than once) before anything

Morning folks, Need some Help. I have a Solaris 2.5.1 system that runs Samba as simple shares but I want to attach it to an NT4 domain and use Winbind for NT authentication. But I get a broken pipe error when I run " smbpasswd -j thinktank -r testerpdc -U tester -D4". With the debug level set to 4 everything looks good until it connects to the pdc on port 445 then i get the broken

Hi, When I use the windows nt or Windows 2000 add printer Wizard (tool) and browse for the printers they are not listed as available. I have to select the Samba-host NETBIOS name before printers become browseable. What I want is to use The "Add printer Wizard", Browse, and find a list or printers available.. \\sambahost\printer1 \\sambahost\printer2 Please find my smb.conf