Displaying 4 results from an estimated 4 matches for "73be".
Did you mean:
73bc
2016 Nov 18
2
DC server own hostname must be part of ad dc domain?
...n AD domain ?
And second part of question:
root at ad51:~# cat /etc/hosts
172.16.214.141 daeb1132-e379-4231-b114-5d03cc8925a9._msdcs.dc.samges.ru
127.0.0.1 localhost.localdomain localhost
# Auto-generated hostname. Please do not remove this comment.
172.16.214.151 ad51.samges.ru ad51
23a2a21d-73be-4824-8647-7ef06d463bca._msdcs.dc.samges.ru
::1 localhost ip6-localhost ip6-loopback
Are autogenerated string written bu provision script? Are it needed?
(provision was 4.1.9 version)
Can I remove records from "hosts" for *_msdcs.dc.samges.ru, if it
resolvable by samba dns s...
2016 Nov 18
0
DC server own hostname must be part of ad dc domain?
...ion:
>
> root at ad51:~# cat /etc/hosts
>
> 172.16.214.141 daeb1132-e379-4231-b114-5d03cc8925a9._msdcs.dc.samges.ru
> 127.0.0.1 localhost.localdomain localhost
> # Auto-generated hostname. Please do not remove this comment.
> 172.16.214.151 ad51.samges.ru ad51
> 23a2a21d-73be-4824-8647-7ef06d463bca._msdcs.dc.samges.ru
> ::1 localhost ip6-localhost ip6-loopback
>
> Are autogenerated string written bu provision script? Are it needed?
> (provision was 4.1.9 version)
No, is DHCP putting it there ?? if your machine is using dhcp to get its
ip etc,...
2007 May 06
1
Upgrade 3.0.24-3.fc5 to 3.0.24-4.fc5 Anomaly
..._fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 72cc : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 72d6 : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 731e : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 73be : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 75b9 : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 75d0 : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_reply: INVALID PIPE HANDLE: 760c : 1 Time(s)
smbd/ipc.c:api_fd_reply(290) api_fd_...
2012 Oct 24
2
every 2nd echo-request malformed when ping -s >4067
Hello,
while checking new mtu9k-setup, I discovered that ping has some odd
behaviour.
If I use payloadsize > 4067, every 2nd icmp-echo-request seems to be
malformed:
ping -s 4068 -D 10.5.49.65
1st: 12:21:09.048447 IP 10.5.49.126 > 10.5.49.65: ICMP echo request, id
46597, seq 0, length 4076
0x0000: 4500 1000 0f2d 4000 4001 a507 0a05 317e
2nd: 12:21:10.052891 IP 10.5.49.126 >