search for: nmbs

Hi, I have a question about the format of Theora bitstream header. It seems to me that there are differences between the specification[1] (version 2004 Oct 1) and its reference implementation in libtheora 1.0alpha3 released at 2004 Jun 1. I mean that... please refer to Section 6.2 'Identification Header Decode' in that specification[1] and the function

While trying to find a bug in my encoder, i came across an error in the spec where it defines the structure of the ident header... the spec defines 100 extra bits which aren't actually in the headers... NSBS, NMBS and NBS don't appear in a 3 2 0 header... the actual structure is as follows //0 - 7 header ident (8 bits) //8 - 55 theora ident (48 bits) //56 - 63 ver major (8 bits) //64 - 71 ver minor (8 bits) //72 - 79 ver revision (8 bits) //80 - 95 numMacroBlocksWide (16 bits) //96...

Clients are Windows 2000; server is running Samba version 3.0.2a. We've been a W2K shop for some time but have started to get in a few Windows XP systems (principally laptops). The issue we're experiencing with the Win XP machines is that they can't map the homes share, either through a VPN or when connected directly to the network the samba server is on. All other shares remain

...dr.arpa And a bit ahead thinking, if this is setup correctly, then your "NETBIOS" names.. Are resolvable through DNS. (See man smb.conf : Default: dns proxy = yes). For that i have 1 member running nmbd that is always online and provides the browserlist. Do note also, you dont need nmbs, if you set the "netbios resolving" through dns. Now this restricts you hostnames length, NETBIOS hostname's RFC is different then dns hostname RFCs. The golden rule is, stay below 15 char, and dont use . In netbios names. RFC allows it but it will conflict with the dns if setup wro...

Mandi! Rowland Penny via samba In chel di` si favelave... > This is probably where you are going wrong. AD lives and dies on DNS, > your DC MUST be authoritative for the AD domain. ...but *is* authoritative! Simply DHCP server assign the ''old'' DNS, where all resolution fr the AD (sub)domain are forwarded to AD DNS... > Your AD clients should be using the DC as

...words = yes local master = no [print$] path = /var/local/samba/printers guest ok = yes browseable = yes read only = yes write list = ntadmin [printers] comment = All Printers printable = yes path = /var/spool/samba browseable = yes guest ok = yes read only = yes nmbs logs the following related info as it starts: where www.ww.ww.ww is th IP for the W2K domain controler sss.ss.ss.ss is the IP for the SAMBA server FOO is the samba server (RH Linux 6.2, Samba 2.2.0) BAR is the W2K domain controler/WINS server FOOBAR_DOM is the domwain [2001/05/23 15:10:27, 2]...