search for: 746c

Displaying 4 results from an estimated 4 matches for "746c".

Did you mean: 746
2002 Feb 26
1
printing problems and permissions
...02/02/26 18:04:21, 3] smbd/ipc.c:reply_trans(480) trans <\PIPE\> data=176 params=0 setup=2 [2002/02/26 18:04:21, 3] smbd/ipc.c:named_pipe(334) named pipe command on <> name [2002/02/26 18:04:21, 3] smbd/ipc.c:api_fd_reply(296) Got API command 0x26 on pipe "spoolss" (pnum 746c)free_pipe_context: destroying talloc pool of size 0 [2002/02/26 18:04:21, 3] rpc_server/srv_pipe.c:api_pipe_request(1148) Doing \PIPE\spoolss [2002/02/26 18:04:21, 3] rpc_server/srv_pipe.c:api_rpcTNP(1180) api_rpcTNP: pipe 29804 rpc command: SPOOLSS_OPENPRINTEREX checking name: \\SUGAR\hplj6...
2018 May 29
2
Samba 4.8 RODC not working
.../29 10:54:01.565288, 4] ../source4/dsdb/repl/drepl_partitions.c:578(dreplsrv_refresh_partition) dreplsrv_refresh_partition(DC=ads,DC=MYDOMAIN,DC=be) [2018/05/29 10:54:01.568733, 4] ../source4/dsdb/repl/drepl_partitions.c:353(dreplsrv_out_connection_attach) dreplsrv_out_connection_attach(c5675dd9-746c-4940-be0c-aa39f4e7da23._msdcs.ads.MYDOMAIN.be): create [2018/05/29 10:54:01.568723, 4] ../source4/lib/socket/interface.c:116(add_interface) [2018/05/29 10:54:01.568766, 4] ../source4/dsdb/repl/drepl_partitions.c:578(dreplsrv_refresh_partition) dreplsrv_refresh_partition(CN=Configuration,DC=ads,D...
2018 May 24
5
Samba 4.8 RODC not working
Hi, It's my first try to setup RODC using Samba 4.8. We have latest Samba 4.7 environnement with 2 DC and some file servers. Joining the DC to the domain is OK using samba-tool domain join command. The domain controller appears in the DC list (MMC) However, users cannot be authenticated. Samba is running but these ports are closed : netbios-ssn 139/tcp # NETBIOS session service
2008 Jul 14
5
EOL in stderr of ssh - Linux
Hello everyone, recently I've found something I consider a bug. Correct me if I'm wrong, but I always thought that Linux' EOL is 0x0A. Imagine my surprise when I saw that all messages that are being output on to the stderr (on any Linux I've tested - Fedora and Ubuntu) are terminated with 0x0D, 0x0A. Maybe that's standard behaviour of all stderr messages in all Linux