similar to: Shared printing between Linux (client) and Windows (server): NT_STATUS_ACCESS_DENIED

I have a Windows 7 workstation with physically connected printer and Linux laptop (Linux Mint 19). They are connected to each other via router with internet cord plugged in. I managed to establish file exchange between them: create a shared resource on one computer, then access it from another. But the same trick with printer just do not work: as soon as I try to access it via network from

Try this. Check the enabled Guest account, go to Devices and Printers in Control Panel, right click on the network shared default printer and select Printer properties. Next select the Security tab on the Printer Properties page, and you should see Everyone in the list of users. Check the permissions for Everyone. At minimum, Print should be checked in the Allow check box. The print

On 9/27/19 1:32 PM, Rowland penny via samba wrote: ....snippity... > I repeat, smbclient never had anything to do with network browsing, so > it is unlikely to have anything to do with Network Discovery. Perhaps > you are thinking of libsmbclient ? this can be used by other packages to > provide network browsing. > > You could always code up what you require and propose it as

On 9/27/19 5:38 PM, Jeremy Allison wrote: > On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are

I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared printer that I cannot set up but I am not sure if this is a CentOS issue or a Samba issue. When I run the printer setup GUI, it is not able to find any shared printer. If I run smbclient I get this error: smbclient -L dap001 -N Unable to initialize messaging context Anonymous login successful ??????????????

Hello, I'm trying to use the "notify" API of libsmbclient, testing against a Samba AD DC. The function is returning with errno=22 (mapped from NT_STATUS_REVISION_MISMATCH), and I'm getting the following error message: smb1cli_req_writev_submit: called for dialect[SMB3_11] server[dc1.example.com] It looks like libsmbclient is, for some reason, using SMB1 but needs to be

Hi all, Sorry for this question which has certainely already been answered, but I could not find info in the list nor in the wiki. From my Debian laptop running testing (samba 4.9.5) and with an empty smb.conf (I wanted to be sure that only default values are used), I can not browse shares of a Windows 10 machine (sorry, Thunderbird splits some lines): smbclient -L 192.168.122.200 Unable to

On 9/27/19 1:39 PM, Jeremy Allison via samba wrote: > On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you

Shanks for the hint! Very strange that the default is only to use a deprecated protocol… Anyway, this option has no effect on this issue… Yvan Le 31/05/2019 à 18:53, Kris Lou via samba a écrit : > Most likely, your Windows 10 (file server) is disallowing SMB1 connections, > which is the default for smbclient. > > You can force smbclient to use a higher protocol with "smbclient

I am running several Solaris 11 file servers with samba 4.7.6. This is an AD domain but the domain controllers are Win 2008 R2 and Windows 2012 R2. All users and groups in AD have unix uidNumbers and gidNumbers assigned. On one file server, I am having problems where some users can not access files , via windows, to which they should have access as the group member. For example,

On 9/27/19 1:39 PM, Jeremy Allison wrote: > On Fri, Sep 27, 2019 at 01:36:42PM -0500, Christopher Cox via samba wrote: >> On 9/27/19 1:32 PM, Rowland penny via samba wrote: >> ....snippity... >>> I repeat, smbclient never had anything to do with network browsing, so >>> it is unlikely to have anything to do with Network Discovery. Perhaps >>> you are

Hai,   Just a questions, this might be a bug, might not, but for this one i need some help.   Setup, debian 9.   Member server samba 4.9.3 AD DC servers samba 4.8.7   Im setting up the member with a very tight firewall, so nothing in/our/routed unless its defined. Im using UFW firewall for it.   I notice the following in my member its firewall logs, and this only happend when i run : id or

I can consistently reproduce a crash in dovecot: Select 20 or more messages and copy them to a test folder. Go into that test folder and SHIFT-DEL the messages rapidly (holding down SHIFT-DEL works best) Just rapidly DELing them (even holding down DEL) doesn't do it (unless it's the Trash folder) I'm using the following namespace (in case that's relevant) namespace private {

I've run this test on every permutation of poll and notify: can NOT reproduce the crash: --with-ioloop=select --with-notify=none --with-ioloop=select --with-notify=dnotify --with-ioloop=select --with-notify=inotify --with-ioloop=poll --with-notify=none --with-ioloop=poll --with-notify=dnotify --with-ioloop=poll --with-notify=inotify CAN reproduce the crash: --with-ioloop=epoll

On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > Sounds like it's losing lots of packets. > > > > > > > The tcpdump[1] shows strang HTTP traffic at the end. > > It is TCP to port 80, but that

Hi I've just started to play around with AGI scripts and have run into problems. When I run Asterisk in console mode everything works just fine. If I run Asterisk in 'regular' mode (not console) it crashes if I hang up on the script. I have used Python scripts to test this and also the "agi-test.agi" script. (the Asterisk code was compiled from CVS code just a few days

On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 06:18 schreef upen: > > On Fri, Jun 7, 2013 at 2:57 AM, Geert Stappers wrote: > > > Op 2013-06-07 om 09:35 schreef Geert Stappers: > > > > Op 2013-06-06 om 14:42 schreef H. Peter Anvin: > > > > > > > > The tcpdump[1] shows strang HTTP

Hey all I have installed a new Debian 3.1, with samba 3.0.14a-3 from apt-get. I have configured samba to use the LDAP backend. I used the smbldap-populate to get my directory going. No problem until then. I currently only have 1 machine, which is also configured to be the PDC. But, I can't join that PDC to the domain, damn it. Here is what it says, debug level 2: pdc:~# net rpc join -U

On Sat, Jun 8, 2013 at 1:44 AM, Geert Stappers <stappers at stappers.nl> wrote: > Op 2013-06-07 om 12:20 schreef upen: > > On Fri, Jun 7, 2013 at 9:29 AM, Geert Stappers <stappers at stappers.nl> > wrote: > > > Op 2013-06-07 om 06:18 schreef upen: > > > > [ ... dhcp server configuration ... ] > > > > Everything has been always like this on

I have a problem with smbtree. When I try smbtree -N on my PC I receive: Got a positive name query response from 192.168.0.100 ( 192.168.0.100 ) read_socket_with_timeout: timeout read. read error = Connection reset by peer. failed tcon_X with NT_STATUS_INVALID_NETWORK_RESPONSE read_socket_with_timeout: timeout read. read error = Connection reset by peer. failed tcon_X with