Getting the Samba PDC into the domain

[Len Harold]

>From the production Samba server:

 root> /opt/samba/bin/nmblookup SMBTEST
 Sending queries to 129.101.74.255
 129.101.74.140 SMBTEST<00>
 129.101.74.140 SMBTEST<00>

Of course nmblookup fails miserably on SMBTEST.

Len

>okie, well does the machine at ip 129.101.74.140 actually _have_ a NetBIOS
>name SMBTEST registered?  use nmblookup (or nbtstat.exe) to find out.
>
>
>On Thu, 13 Jan 2000, Len Harold wrote:
>
>> Ok Luke,
>> 
>> >if it's not broken, smbclient and rpcclient take a -n NETBIOSNAME option.
>> >check this out, first, though.
>> 
>> I tried this:
>> 
>>   rpcclient -n SMBTEST -S SMBTEST -W MRCTEST -U smbroot
>> 
>> It is taking the the netbios name so now I'm guessing that my problem is
>> in the configuration somewhere, not the code.
>> 
>> Guys,
>> 
>> If someone wants to take a stab at this, the end of lsaquery error message
>> says:
>> 
>>  cli_establish_connection: SMBTEST<00> connecting to SMBTEST<20> (129.101.74.140) - smbguest [MRCTEST] with NTLMv1, nopw: No
>>  socket open succeeded.  file name: /tmp/.smb.0/agent
>>  socket connect to /tmp/.smb.0/agent failed
>>  redirect FAILED, make direct connection
>>  Connecting to 129.101.74.140 at port 445
>>  error connecting to 129.101.74.140:445 (Invalid argument)
>>  Connecting to 129.101.74.140 at port 139
>>  error connecting to 129.101.74.140:139 (Invalid argument)
>>  cli_establish_connection: failed to connect to SMBTEST<00> (129.101.74.140)
>>  cli_net_use_add: connection failed
>>  cli_net_use_del: \\SMBTEST. force close: No
>>  cmd_lsa_query_info: query failed
>> 
>> Len