search for: 44r

...g it back I do a smb stp smb start and off it goes. Now this is fine as far as it goes but any PCs updating at that time can get a little upset. There are 500 odd smbd running at any one time. For example these are the entries when it is registered: "VOYAGER#00" 983543441 172.16.12.100 44R "VOYAGER#03" 983543441 172.16.12.100 44R "VOYAGER#20" 983543441 172.16.12.100 44R I understand the #0x corresponds to the entry type but what is the 9 digit number to the right of that ? Can I get away with creating my own entries in the wins.dat file ? Will nmbd use a host f...

...samba>cat wins.dat "SPRUCE#20" 914324043 127.0.0.1 46R "SPRUCE#03" 914324043 127.0.0.1 46R "SPRUCE#00" 914324043 127.0.0.1 46R "GIGI#00" 914324043 255.255.255.255 c4R "GIGI#1e" 914324043 255.255.255.255 c4R "GIGI#1b" 914096552 127.0.0.1 44R The correct address should be 192.168.1.1. I have "interface 192.168.1.1/24" in my smb.conf. The system otherwise works fine, but when a windows machine does a "Find Computer" it gets the bogus 127.0.0.1 from the WINS server. Other Samba servers can find it by its correct IP...

Hello, These two following lines are from the wins.dat file. I was wondering about the meaning of the last records (44R and c4R). Does anybody know what they mean? "PCLAB#1b" 982581535 10.33.6.140 44R "PCLAB#1c" 982581535 10.33.6.140 c4R Kind regards, Werner Maes LUDIT-KULeuven

...39;winsserver_init' is picking up the old IP from /var/lib/samba/wins.dat --- [2003/12/05 14:46:24, 4] nmbd/nmbd_winsserver.c:initialise_wins(362) initialise_wins: add name: F-LAPTOP-SJG#20 ttl = 161432 first IP 192.168.213.12 flags = 44 --- "F-LAPTOP-SJG#00" 1070797025 192.168.213.12 44R "F-LAPTOP-SJG#20" 1070797016 192.168.213.12 44R --- 2). When the machine is plugged onto the network it introduces itself --- [2003/12/05 14:47:30, 4] nmbd/nmbd_packets.c:process_dgram(1227) process_dgram: datagram from F-LAPTOP-SJG<00> to FUSION<1d> IP 192.168.213.29 for \MA...

Debian Sarge, Samba 2.2.12 (legacy install), openLDAP 2.2.17, connecting to a PDC running Samba 2.2.8a. The machine in question failed DIAGNOSIS.txt step 3. I've got a really odd issue -- a Samba server that can "smbclient -L" everyone but itself. Samba still serves shares and PDC authentication works fine, but this failure is annoying, and as such, must be fixed. :) -- issued

...3" 1110703485 10.0.0.120 24R "RUPERT-LAPTOP#00" 1110702143 10.0.0.120 24R "RUPERT-LAPTOP#03" 1110703485 10.0.0.120 24R "RUPERT-LAPTOP#20" 1110702143 10.0.0.120 24R "SAMBAGRP#00" 1110783500 255.255.255.255 c4R "SAMBAGRP#1b" 1110742524 10.0.0.110 44R "SAMBAGRP#1c" 1110742524 10.0.0.110 c4R "SAMBAGRP#1e" 1110783500 255.255.255.255 c4R -- Rupert Heesom <rupert@heesom.org.uk>

...0#00" 1009148707 172.16.10.102 172.16.12.102 46R "LUCAS-100#03" 1009148707 172.16.10.102 172.16.12.102 46R "LUCAS-100#20" 1009148707 172.16.10.102 172.16.12.102 46R "TEST#00" 1009190254 255.255.255.255 c4R "TEST#1b" 1009148707 172.16.10.102 172.16.12.102 44R "TEST#1c" 1009148707 172.16.10.102 172.16.12.102 c4R "TEST#1e" 1009148707 255.255.255.255 c4R "TFIC#00" 1009190360 255.255.255.255 e4R "TFIC#1e" 1009186400 255.255.255.255 e4R "TRH#03" 1009086508 172.16.11.58 64R "YPG_PC36#00" 1009086508 1...

Is it possible to manually add entries to the WINS database on a Samba nmbd running as a WINS server? Alternativily could I get the WINS nmbd to use DNS for hostsnames it can't resolve using it's own database. I have several NT servers that seem to just vanish from the db after a while. One of my 2.2.3a boxes also did this for a pastime. Whilst I can do nbtstat -RR on NT or restart

...PIPE 0xcd659c64 16384 dovecot 5161 root 40r PIPE 0xcc08b5a0 16384 dovecot 5161 root 41r PIPE 0xcc08b870 16384 dovecot 5161 root 42r PIPE 0xcc08b360 16384 dovecot 5161 root 43r PIPE 0xcc08bc60 16384 dovecot 5161 root 44r PIPE 0xcc08bab0 16384 dovecot 5161 root 45r PIPE 0xcc08b000 16384 dovecot 5161 root 46r PIPE 0xcc08b120 16384 dovecot 5161 root 47r PIPE 0xcc08b6c0 16384 dovecot 5161 root 48r PIPE 0xcc08b990 16384 dovecot 5161 root...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

...at coqqBe2`NrZ%b z4E>JN%K`fA*T?{23RI`HZ)R+{40g;FDRO{spL^En#&Xg$`p)4O-DIFx%1G$4MvlgE zNv9 at Pw<}TC!*Ot(83D<o=7)>HmXPm^Yh)<}i`u$qc;~mf4ohc;?(`fKyt6z;z6gV4 z<y8IX1yr;dG%z(LV#-Yde0Un${`}Ohn9Okdjf}Hw9Zo2lTwQoF;3}ebql`A-1irUM zn$G9kzalTwoH5-TYKw<BEmh;g*d;x?NY0;u&7P>|8*O5F44RFA=G at s9H*hV=$PQ4$ zj)<Z!j~)!l3Nbp?D{8{w8Ti`mp2iI}$XUZCjHd2UKc#SNn2a=p<-poVM(5b;AL*Fn zEZ&5qBiybmgG+Ot`^dxux~iVrwc(s*rs2gB==P4#n2cCro0&{6N8a<gKm#Qs%1L3v zP{jcXwD(j4{%qb##ziESGY!;@3zREztcWNEx|ORGcy3<bt=bPfN%rQjmUpdC?e7Q& z*Tg at doe8DJr%-Q<G6{3e%XfF<PZdVOM()6OInw$)Wf_5...