search for: protocols

In preparation for installing this header as a common public header for use by other projects, rename it. --- common/protocol/Makefile.am | 10 +++++----- common/protocol/{protocol.h => nbd-protocol.h} | 6 +++--- common/protocol/protostrings.sed | 6 +++--- plugins/nbd/nbd-standalone.c | 2 +- server/protocol-handshake-newstyle.c

Hi, I'm trying to replace a windows fileserver server with a Fedora Core 2 samba server in our Windows 2000 ADS domain. A performance problem occurs when accessing certain samba shares from Windows Explorer on either an Windows XP or a W2K client machine. It can take up to a minute for explorer to list files in a share folder containing only a few files! It eventually does, but but reports

I'm trying to set up nut-2.6 with a SMX1000 ups unit from APC on a CentOS 4.8 server. It's connected via USB, and Linux has detected it as a HID device. Nut was built from source code. T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 21 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=051d ProdID=0003 Rev= 1.06 S: Manufacturer=American Power

We should have only one NBD protocol file. Let's make nbdkit's version the canonical one, and use it in libnbd. Rich.

I'm trying to get Samba up and running and having a terrible time. It says that I should be able to run nmap and see that 137 and 139 are open - which they are not. I have not added any restrictions in smb.conf, do not have a firewall running and I have increased the log level to 5 to see all of the messages. It says that it is talking on 137 but it kind of looks like it's not talking

Hi all, I have begun the release of my MFC/R2 protocol software. At http://www.opencall.org/installing-mfcr2.html there are instructions for installing what I have released so far. This is the MFC/R2 protocol software, and a test program. The software to interface Asterisk to the MFC/R2 code will be released shortly. It used to work, but it hasn't been touched for a while, and Asterisk

Hai, If you use that or the AD, then its incomplete, imo. Your missing ldaps (636) and the GC (ssl) 3268/3269) ports and maybe NTP (123/tcp) if installed. Maybe you dont need them, just an observation. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Jeff > Sadowski via samba > Verzonden: dinsdag 13 februari 2018

the glusterfs 3.0.X crashed on Fedora 12, it got buffer overflow, seems fine on Fedora 11 Name : fuse Arch : x86_64 Version : 2.8.1 Release : 4.fc12 Name : glibc Arch : x86_64 Version : 2.11.1 Release : 1 complete log: ====================================================================================================== [root at test_machine06 ~]# glusterfsd

The DF flag is only available to clients that negotiated structured replies, and even then, the spec does not require that it be implemented. However, since our current implementation can't fragment NBD_CMD_READ replies, we trivially implement the flag (by ignoring it); we don't even have to pass it on to the plugins. Enhance some documentation about sparse reads while at it (when we

Hello, Thank you ! I add server min protocol = SMB2_02 to smb.cnf All clients are now using SMB2_10 as minimum protocol version May you indicate me the difference between "client min protocol" and "server min protocol" ? "server min protocol" is to use on a domain member "client min protocol" is to use in which case ? Should I also set client min

More nbd-protocol.h improvements Eric Blake (2): common/protocol: Switch nbdmagic to uint64_t common/protocol: Declare additional constants common/protocol/nbd-protocol.h | 16 ++++++++++------ server/protocol-handshake-newstyle.c | 2 +- server/protocol-handshake-oldstyle.c | 2 +- plugins/nbd/nbd-standalone.c | 2 +- tests/test-layers.c | 2 +- 5 files

Use a simple bash script to generate the protostrings.c functions. Remove the extern decls from the nbd-protocol.h file which were used previously in the generation of this file. They have been moved to a new internal header called "protostrings.h". --- common/protocol/Makefile.am | 8 ++- ...tostrings.sed => generate-protostrings.sh} | 56 +++++++++++--------

Hello, My DC smb.conf currently has the following set server max protocol = NT1 server min protocol = CORE client max protocol = NT1 client min protocol = CORE Is it safe to change both the client and server max to = SMB3? What about on member servers? Should I be concerned with anything breaking? I'm using Windows 7 clients to authenticate against Ubuntu

I did not set max protocol to SMB2 in smb.cnf, I don't want to force SMB2 selection if SMB3 can be used by a client. The machine is a Windows 7, so is SMB2 compliant. Le 22/07/2019 ? 11:44, Gaiseric Vandal via samba a ?crit?: > I would guess that changing the min protocol does not affect existing > connections unless you were to restart samba. > > Is the max protocol set to at

Debian Lenny Samba 3.2.3 LOOX N560 with Windows Mobile 5 Hello, ?my PDA LOOX N560 could connect via WLAN to SAMBA under Etch. Meanwhile I upgraded to Debian Lenny and now may PDA cannot connect anymore to the server. Error 1223 or 1222. Connecting to XP-Clients via WLAN is okay. Connecting to Samba Wireshark tells me: malformed packet: No. ? ? Time ? ? ? ?Source ? ? ? ? ? ? ?

Hello, I''m trying to shape traffic by IP addresses and by 802.1q vlans. But when I add 802.1q filter filters output looks strange. Maybe I''m missing some options to TC? Thanks, Mindaugas # ./bin/tc -s -d filter show dev eth0 filter parent 1: protocol ip pref 1 u32 filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1 filter parent 1: protocol ip pref 1 u32 fh

Sorry if this is a stupid question but I tried reading, studying and finding solution but am not making it alone :) On my home lan I have a Linux (Debian sid) box (192.168.174.244) running 3.0.10 samba and cups 1.1.23. My objective is to print from this box to the other home PC which is running XP (192.168.174.242) and sharing an Epson R200 printer. Follows the troubleshooting I could do

Hello, I currently run samba with server min protocol = NT1 but I need to move towards server min protocol = SMB2 is there any way I can detect which clients still use the older protocol versions? I would like to estimate the impact of the change before i do close NT1/SMB1. Thank and kind regards, Heiner Billich

On Fri, Mar 29, 2019 at 12:43:33PM +0000, Richard W.M. Jones wrote: >On Thu, Mar 28, 2019 at 10:44:42PM -0500, Eric Blake wrote: >> The DF flag is only available to clients that negotiated structured >> replies, and even then, the spec does not require that it be >> implemented. However, since our current implementation can't fragment >> NBD_CMD_READ replies, we

On Thu, Mar 28, 2019 at 10:44:42PM -0500, Eric Blake wrote: > The DF flag is only available to clients that negotiated structured > replies, and even then, the spec does not require that it be > implemented. However, since our current implementation can't fragment > NBD_CMD_READ replies, we trivially implement the flag (by ignoring > it); we don't even have to pass it on to