similar to: Possible bug in SAMBA connection close?

Hey all, I was wondering if a tool existed in samba to remotely shutdown NT/2K servers -- something like the shutdown.exe program included w/ the NT4 resource kit? I apologize if this has been answered someplace else -- I've looked through the message archive, and scanned the source. But, I didn't see anything like this. It could be useful, and seems like it wouldn't be too hard

Hi All I have a server which seems to be getting spam relayed through it. The story is this..... User reported loads of undeliverables being received so I had a trawl through the logs. So the attacker connects to our server using SMTP AUTH........ Oct 5 15:17:53 www sendmail[6972]: AUTH=server, relay=pppoe9.net109-120-27.se1.omkc.ru [109.120.27.9] (may be forged), authid=jon, mech=LOGIN,

We have a samba server behind a firewall with the IP address 192.168.200.2 and a Windows 2000 Domain controller with the IP address 192.168.255.1 . When we put the samba in the same subnet then it woks fine. We forwarded the fooling ports: TCP and UDP 192.168.200.2 to 192.168.255.1 port 137 192.168.200.2 to 192.168.255.1 port 138 192.168.200.2 to 192.168.255.1 port 139 192.168.200.2 to

On Mon, 6 Aug 2018 10:18:41 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > Thanks for anwser! > > Well, GlusterFS  just replicating(it is ok). > > Problem is access second server with specific name..... Yes, but what specific name ? is it the machines short hostname (netbios name) or what ? > > Popup appears requesting domain

Hi! I have two server samba member domain. Version 4.8.3(Compilated) Running in Ubuntu LTS 16.04 With GlusterFS(Replicated) and Heartbeat(for HA) IP A: 192.168.200.1 (DNS: Fileserver1) -> Master IP B: 192.168.200.2 (DNS: FIleserve2) -> Slave IP C:192.168.200.10 -> (DNS: Fileserve) -> Heartbeat -> IP that stays with master server , when UP, if down IP "junp" for

I'm trying to bridge a mix of 802.1q tagged and untagged Ethernet frames through the new Ethernet over GRE functionality in kernel 2.6.28 The hosts handling the tunnel (192.168.200.6, 192.168.200.2) are connected together through with a simple cross cable through their eth1 interface. The switches are connected to their respective eth0 interface, which is bridged with their respective gretap

Hi! Any Ideia ? Sorry to send again, as I sent on Sunday :-D Regards; On 05-08-2018 14:12, Carlos wrote: > > Hi! > > I have two server samba member domain. > > Version 4.8.3(Compilated) > > Running in Ubuntu LTS 16.04 > > With GlusterFS(Replicated) > > and > > Heartbeat(for HA) > > > IP A: 192.168.200.1 (DNS: Fileserver1) -> Master >

Hi! Thanks again. ========== *Yes, but what specific name ? is it the machines short hostname (netbios name) or what ?* IP A: 192.168.200.1 (DNS: Fileserver1.XXXXX.XXX.XXX) -> Master IP B: 192.168.200.2 (DNS: FIleserve2.XXX.XXX.XXX) -> Slave IP C:192.168.200.10 -> (DNS: Fileserve.XXX.XXX.XXXX) -> Heartbeat -> IP that stays with master server , when UP, if down IP

On Mon, 6 Aug 2018 11:28:04 -0300 Carlos via samba <samba at lists.samba.org> wrote: > Hi! > > Thanks again. > > ========== > > *Yes, but what specific name ? is it the machines short hostname > (netbios name) or what ?* > > > IP A: 192.168.200.1 (DNS: Fileserver1.XXXXX.XXX.XXX) -> Master > > IP B: 192.168.200.2 (DNS: FIleserve2.XXX.XXX.XXX)

I'm using samba 3.5.6 + PDC and connected to LDAP directory In log level 1 there is many entries like this : Feb 18 18:13:42 samba smbd[21646]: getpeername failed. Error was Transport endpoint is not connected Feb 18 18:13:42 samba smbd[21646]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer Is it a problem ? or just an informative event ? Feb 18

Hello, I am experiencing an issue on Mandriva 2007.1 (samba 3.0.24) where smbd crashes as soon as a guest connection attempt is made for a single file share: icho@hiker ~ $ smbclient //192.168.200.2/data Password: Domain=[FONET] OS=[Unix] Server=[Samba 3.0.24] Server not using user level security and no password supplied. tree connect failed: Call returned zero bytes (EOF) Syslog logs

Skipped content of type multipart/mixed

Hello Everyone, I am having trouble with booting a soekris 4826 board.after setting up my tftp,dhcp and web servers ,I log into the board using minicom and type boot f0,which doesn't quite work out. > boot f0 NSC DP83815/DP83816 Fast Ethernet UNDI, v1.03 Copyright (C) 2002, 2003 National Semiconductor Corporation All rights reserved. Pre-boot eXecution Environment PXE-2.0 (build 082)

Hi, I have the shown (end of this post) net work configuration. In a "few" words: My Debian Sarge server is connected to a D-Link ADSL Router (DSL-562T). DMZ is enabled for the Debian Sarge IP on the Router. My Linux server has two NIC''s. ethlan = internal Net ethdsl = external -> D-Link My Linux server is configured to make NAT via iptables. Current state -

I am looking to setup a domain server. I have tried and tried and this is the closest I have gotten so far. The main problem I have is in the user authentication. I am getting an error that the user or password is wrong. Currently it looks like Samba can not access the passwd file. What is this file? My log for the client give this error: [2003/06/05 15:35:35, 0]

Hello, can someone give me a hint, where to find an info, how to setup dovecote replication with sieve? On my active.active setup, it replicates the user mdboxes and sieve works also, on the active destination fileserver. Client changes the sieve, tests work fine. But the sieve file won't get replicated to the replica server. As i've researched, it was introduced in dovecot v2.2.rc3

Hello. I have got strange problem with tc utility (iproute2-ss001007) on linux 2.4.18. No matter what rules i am going to test, the resul of ''tc class ls/show'' is always the same : ATSLite ()# tc -s class ls dev eth1 do_page_fault() #2: sending SIGSEGV to tc for illegal read access from 00000000 (epc == 00000000, ra == 00408750) Segmentation fault tc -s qdisc ls , tc -s filter

Hi All, I am still having troubling with PXE. Thanks for replying Shao.I did follow ur suggestions and my results have improved a bit.From Ethereal and TCPdump, I can see that the client sucessfully dowloads the file pxelinux.0 from the server but stops at this point. here is the output of tcpdump tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:05:41.966864 IP

Please note that Windows 9x clients are not true members of a domain for reasons outlined in this article. Therefore the protocol for support Windows 9x style domain logons is completely different from NT4 domain logons and has been officially supported for some time. Did you read this document? Let me know what needs to be updated and i will take care of it. Cheers, jerry