Hello Samba List,
I'm running a Samba 3.0.22 PDC on Solaris 9. Things got a bit peculiar
when I added a 2nd network interface.
The two subnets are a primary network that carries all the client
traffic and a tape-backup/admin network that is not accessible to any
clients, ie.
aaa.bbb.ccc.241 - bge0 - primary network (address suppressed)
192.168.254.254 - bge1 - admin/backup network
I've configured Samba (I think) to ignore the admin network...
socket address = aaa.bbb.ccc.241
interfaces = bge0 lo0
bind interfaces only = true
hosts allow = aaa.bbb.ccc. , 127.
However, some devices are getting the notion that there is a PDC at
192.168.254.254 and are trying to contact it (which of course they
cannot). For instance (this is a NetApp that is a domain member):
grunthos> cifs testdc
...
Testing all Primary Domain Controllers
found 2 unique addresses
Fri May 12 09:56:55 EDT [auth.dc.trace.DCConnection.statusMsg:info]:
AUTH: TraceDC- Found 2 BDC addresses through WINS.
Fri May 12 09:56:55 EDT [auth.dc.trace.DCConnection.statusMsg:info]:
AUTH: TraceDC- Found 2 PDC addresses through WINS.
found PDC TRILLIAN at aaa.bbb.ccc.241
Not able to communicate with PDC 192.168.254.254
trying 192.168.254.254...Fri May 12 09:57:07 EDT
[auth.dc.GetDCName.failed:error]: AUTH: Error 0x0 while trying to get
Domain Controller name for 192.168.254.254: Timed out waiting for reply.
...
I'd expect it to find only aaa.bbb.ccc.241 - Any idea what am I missing
here?
The PDC is also the WINS server, in case that matters.
Thanks,
--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran@mdibl.org
Roy McMorran skrev:> Hello Samba List, > > I'm running a Samba 3.0.22 PDC on Solaris 9. Things got a bit > peculiar when I added a 2nd network interface. > > The two subnets are a primary network that carries all the client > traffic and a tape-backup/admin network that is not accessible to any > clients, ie. > aaa.bbb.ccc.241 - bge0 - primary network (address suppressed) > 192.168.254.254 - bge1 - admin/backup network > > I've configured Samba (I think) to ignore the admin network... > > socket address = aaa.bbb.ccc.241 > interfaces = bge0 lo0 > bind interfaces only = true > hosts allow = aaa.bbb.ccc. , 127. > > However, some devices are getting the notion that there is a PDC at > 192.168.254.254 and are trying to contact it (which of course they > cannot). For instance (this is a NetApp that is a domain member): > > grunthos> cifs testdc > ... > Testing all Primary Domain Controllers > found 2 unique addresses > > Fri May 12 09:56:55 EDT [auth.dc.trace.DCConnection.statusMsg:info]: > AUTH: TraceDC- Found 2 BDC addresses through WINS. > Fri May 12 09:56:55 EDT [auth.dc.trace.DCConnection.statusMsg:info]: > AUTH: TraceDC- Found 2 PDC addresses through WINS. > found PDC TRILLIAN at aaa.bbb.ccc.241 > Not able to communicate with PDC 192.168.254.254 > trying 192.168.254.254...Fri May 12 09:57:07 EDT > [auth.dc.GetDCName.failed:error]: AUTH: Error 0x0 while trying to get > Domain Controller name for 192.168.254.254: Timed out waiting for reply. > ... > > I'd expect it to find only aaa.bbb.ccc.241 - Any idea what am I > missing here? > > The PDC is also the WINS server, in case that matters. > > Thanks, >Hi Roy My best guess is that this is subnet browsing issue. Since enhanced browsing is enabled by default try to disable it in [Global] section enhanced browsing = no -- Venlig Hilsen (Best Regards) Rune T?nnesen