samba - Jun 2004 - Re: Questions about Samba and a WINS server...update

Ok...trying to follow up here and see if someone can help me out, and let 
me know what is exactly hapening here. I have a few ideas, but I wanted to 
post here.

As I said in my previous post, I am having problems browsing the corporate 
network from a Branch Office.

Doing some testing, here is some output from my log.nmbd on my WINS server:


[2004/06/25 12:20:45, 0] nmbd/nmbd.c:terminate(54)
   Got SIGTERM: going down...

[2004/06/25 12:20:45, 0] nmbd/nmbd.c:main(664)
   Netbios nameserver version 3.0.4 started.
   Copyright Andrew Tridgell and the Samba Team 1994-2004

[2004/06/25 12:20:45, 0] 
nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(327)
   become_domain_master_browser_wins:
   Attempting to become domain master browser on workgroup COURTESY, subnet 
UNICAST_SUBNET.

[2004/06/25 12:20:45, 0] 
nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341)
   become_domain_master_browser_wins: querying WINS server from IP 
192.168.1.50 for domain master browser name COURTESY<1b> on workgroup
COURTESY

[2004/06/25 12:20:45, 0] 
nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113)
   *****

   Samba server OXYGEN is now a domain master browser for workgroup 
COURTESY on subnet UNICAST_SUBNET

   *****
[2004/06/25 12:20:45, 0] 
nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282)
   become_domain_master_browser_bcast:
   Attempting to become domain master browser on workgroup COURTESY on 
subnet 192.168.1.50

[2004/06/25 12:20:45, 0] 
nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295)
   become_domain_master_browser_bcast: querying subnet 192.168.1.50 for 
domain master browser on workgroup COURTESY

[2004/06/25 12:20:45, 0] 
nmbd/nmbd_become_dmb.c:become_domain_master_query_success(225)
   become_domain_master_query_success:
   There is already a domain master browser at IP 192.168.1.20 for 
workgroup COURTESY registered on subnet 192.168.1.50.

[2004/06/25 12:21:08, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
   *****

   Samba name server OXYGEN is now a local master browser for workgroup 
COURTESY on subnet 192.168.1.50

   *****

I'm posting this again, because I think I may know what is going on, but 
trying to gete verification. This line:

There is already a domain master browser at IP 192.168.1.20 for workgroup 
COURTESY registered on subnet 192.168.1.50.

...I am pretty sure is what is causing the problem. The WINS Server, 
OXYGEN, has the IP of 192.168.1.50:
The NT 4.0 server has the IP address of 192.168.1.20.

What is stumping me is that for some reason, it appears that the NT box is 
still  becoming the Domain Master Browser, which could be the reason why i 
can't browse properly, right?

So how can I make sure that OXYGEN becomes the DMB? It is already the LMB, 
but seems to be losing to the NT 4.0 server for the DMB?

I just thought of something: The NT 4.0 box has the domain setup as 
COURTESY. In looking at my smb.conf file, I setup the WORKGROUP as 
COURTESY. I think I read in the Samba book that this could cause a problem. 
If my thinking is correct, if I were to shut off the NT box, I bet I could 
browse the network from a Branch office, correct? If that is the case, what 
are my options to resolve that? Keep in mind, I have to keep the NT 4.0 box 
for now. :/

Any recommendations?

Jason

>I just thought of something: The NT 4.0 box has the domain setup as 
>COURTESY. In looking at my smb.conf file, I setup the WORKGROUP as 
>COURTESY. I think I read in the Samba book that this could cause a 
>problem. If my thinking is correct, if I were to shut off the NT box, I 
>bet I could browse the network from a Branch office, correct? If that is 
>the case, what are my options to resolve that? Keep in mind, I have to 
>keep the NT 4.0 box for now. :/
>
>Any recommendations?
>
>Jason
Hey guys, I think I found my problem. Now I just need to figure out how to 
fix it.

I checked the NT 4.0 box, and for network identification, it has the DOMAIN 
set to COURTESY.
In smb.conf, the workgroup = COURTESY.

Went through the book, and it stated that if it is set like that, you will 
experience problems. :-/

Ok...now I need to figure out how to fix this.

The tricky part is, all our users have a mapped drive to the NT 4.0 server. 
I have to take that into consideration before I make some changes.

Anyone have some suggestions on what I can do to fix this?

I appreciate it.

Jas