I think you can/should have them remove the PDC from their WINS entry on their end and then you can rejoin the network with the new IP Address.
Outside of that, I can only suggest looking into how to send an update to a record on a WINS server from a Samba PDC. I'm unsure if that is possible as I have only run a fully Windows or a Linux/Samba with Windows Clients as a network. -- Regards, Robert Adkins > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Paul Raines > Sent: Tuesday, September 04, 2012 2:24 PM > To: [email protected] > Subject: Re: [Samba] Changed PDC IP, all hell broke lose > > > It is definitely an issue with the WINS server which returns > the old IP address > > # nmblookup -U 172.27.88.81 -R 'MRIRESEARCH#1b' > querying MRIRESEARCH on 172.27.88.81 > 132.183.202.95 MRIRESEARCH<1b> > > SO it is not automatically picking up the IP change which > happened 4 days ago and I have restarted samba on my PDC > several times. The old IP is definitely not in /etc/hosts > anymore or anywhere in smb.conf. It only shows up in > gencache.tdb in the files /var/lib/samba even though I keep > deleting that file when I restart. > > WINS is a total mystery to me. How is this supposed to work? > > -- Paul Raines (http://help.nmr.mgh.harvard.edu) > > > > On Tue, 4 Sep 2012 12:00pm, Paul Raines wrote: > > > I have no idea what the WINS server is except that I am sure it > > running on Windows since they are totally Windows-based > organization. > > So the WINS server is definitely the problem? When I talk > to them and > > mention I am using Samba on Linux they may totally just say > "we don't support it" and hang up. > > > > It seems a strange design that a WINS server can take > precedence over > > my explicit "password server" setting in my smb.conf file. > > > > -- Paul Raines (http://help.nmr.mgh.harvard.edu) > > > > > > > > On Tue, 4 Sep 2012 11:21am, Robert Adkins II wrote: > > > >> More information is required. > >> > >> What is the WINS server running OS wise? Can you work with the IT > >> Staff in charge of that WINS Server? > >> > >> -- > >> > >> Regards, > >> Robert Adkins > >> > >> > >> > >>> -----Original Message----- > >>> From: Paul Raines [mailto:[email protected]] > >>> Sent: Tuesday, September 04, 2012 11:16 AM > >>> To: Robert Adkins II > >>> Cc: [email protected] > >>> Subject: RE: [Samba] Changed PDC IP, all hell broke lose > >>> > >>> > >>> I am not running winbindd on the server. I am using the > WINS server > >>> of my hospital which I have no control over. > >>> > >>> I have already tried deleting browse.dat (I do not see > the other two > >>> files anywhere) to no avail. > >>> > >>> So my fear is that this is all happening because the WINS > server is > >>> refusing to recognize the change since I cannot do anything about > >>> it. Is that the issue? Is there anyway to force a WINS server to > >>> change the IP it has a for domain master browser? > >>> > >>> -- Paul Raines (http://help.nmr.mgh.harvard.edu) > >>> > >>> > >>> > >>> On Tue, 4 Sep 2012 10:59am, Robert Adkins II wrote: > >>> > >>>> It's most likely that your server has the old IP Address > >>> Cached in the > >>>> wins.dat, browse.dat, browse.tdb. > >>>> > >>>> I recommend the following: > >>>> > >>>> Shutdown the windbind, nmbd and smbd services. > >>>> > >>>> Back up each of the above mentioned files. > >>>> > >>>> Delete the original above named files. > >>>> > >>>> Restart your services and then see if you can connect. > >>>> > >>>> You may also need to edit your samba configuration file > to point to > >>>> the new server IP Address as the PDC Master Browser. > (Assuming you > >>>> didn't already do > >>>> that.) > >>>> > >>>> The problem is that your server is telling clients to > >>> attempt to find > >>>> it on a network that no longer exists. > >>>> > >>>> -- > >>>> > >>>> Regards, > >>>> Robert Adkins II > >>>> > >>>> > >>>> > >>>>> -----Original Message----- > >>>>> From: [email protected] > >>>>> [mailto:[email protected]] On Behalf Of Paul Raines > >>>>> Sent: Tuesday, September 04, 2012 10:41 AM > >>>>> To: [email protected] > >>>>> Subject: [Samba] Changed PDC IP, all hell broke lose > >>>>> > >>>>> > >>>>> I had to move my RedHat 5 box acting as a PDC to a new IP > >>> address. It > >>>>> is running samba 3.5.10. After the move, none of my > >>> windows or linux > >>>>> samba clients worked anymore. I tried rejoining some to > >>> the domain, > >>>>> but would get error > >>>>> > >>>>> Unable to find a suitable server > >>>>> Join to domain 'MRIRESEARCH' is not valid > >>>>> > >>>>> > >>>>> The old PDC IP address is 132.183.202.95 and nothing is > at that IP > >>>>> anymore (for 4 days now). The new IP is 172.21.21.35 > >>>>> > >>>>> I ran 'net -d 10 join' and would see it was still trying > >>> to connect > >>>>> to the old IP address. I tried 'net cache flush' to no > avail. I > >>>>> shut down samba, removed every file in /var/cache/samba > >>> and still no > >>>>> change. > >>>>> It tries to go to the old IP address. > >>>>> > >>>>> On the PDC box, I increase 'os level' from 60 to 70, > >>> stopped the nmbd > >>>>> and smbd processes, did a 'net flush cache' and > restarted nmbd and > >>>>> smbd. Still it fails and the nmbd log as the following. > >>>>> > >>>>> ========== > >>>>> [2012/09/04 10:09:25, 0] nmbd/nmbd.c:857(main) > >>>>> nmbd version 3.5.10-0.110.el5_8 started. > >>>>> Copyright Andrew Tridgell and the Samba Team 1992-2010 > >>>>> [2012/09/04 10:09:25.716397, 0] > >>>>> nmbd/nmbd_logonnames.c:160(add_logon_names) > >>>>> add_domain_logon_names: > >>>>> Attempting to become logon server for workgroup > MRIRESEARCH on > >>>>> subnet 172.21.21.35 > >>>>> [2012/09/04 10:09:25.716599, 0] > >>>>> nmbd/nmbd_logonnames.c:160(add_logon_names) > >>>>> add_domain_logon_names: > >>>>> Attempting to become logon server for workgroup > MRIRESEARCH on > >>>>> subnet 192.168.0.150 > >>>>> [2012/09/04 10:09:25.716671, 0] > >>>>> nmbd/nmbd_logonnames.c:160(add_logon_names) > >>>>> add_domain_logon_names: > >>>>> Attempting to become logon server for workgroup > MRIRESEARCH on > >>>>> subnet UNICAST_SUBNET > >>>>> [2012/09/04 10:09:25.716768, 0] > >>>>> nmbd/nmbd_become_dmb.c:337(become_domain_master_browser_wins) > >>>>> become_domain_master_browser_wins: > >>>>> Attempting to become domain master browser on workgroup > >>>>> MRIRESEARCH, subnet UNICAST_SUBNET. > >>>>> [2012/09/04 10:09:25.716828, 0] > >>>>> nmbd/nmbd_become_dmb.c:351(become_domain_master_browser_wins) > >>>>> become_domain_master_browser_wins: querying WINS > server from IP > >>>>> 0.0.0.0 for domain master browser name MRIRESEARCH<1b> on > >>> workgroup > >>>>> MRIRESEARCH > >>>>> [2012/09/04 10:09:25.722744, 0] > >>>>> nmbd/nmbd_logonnames.c:121(become_logon_server_success) > >>>>> become_logon_server_success: Samba is now a logon server for > >>>>> workgroup MRIRESEARCH on subnet UNICAST_SUBNET > >>>>> [2012/09/04 10:09:25.722928, 0] > >>>>> nmbd/nmbd_become_dmb.c:235(become_domain_master_query_success) > >>>>> become_domain_master_query_success: > >>>>> There is already a domain master browser at IP > >>>>> 132.183.202.95 for workgroup MRIRESEARCH registered on subnet > >>>>> UNICAST_SUBNET. > >>>>> [2012/09/04 10:09:29.096239, 0] > >>>>> nmbd/nmbd_logonnames.c:121(become_logon_server_success) > >>>>> become_logon_server_success: Samba is now a logon server for > >>>>> workgroup MRIRESEARCH on subnet 172.21.21.35 > >>>>> [2012/09/04 10:09:29.096382, 0] > >>>>> nmbd/nmbd_logonnames.c:121(become_logon_server_success) > >>>>> become_logon_server_success: Samba is now a logon server for > >>>>> workgroup MRIRESEARCH on subnet 192.168.0.150 > >>>>> [2012/09/04 10:09:49.731244, 0] > >>>>> nmbd/nmbd_become_lmb.c:395(become_local_master_stage2) > >>>>> ***** > >>>>> > >>>>> Samba name server PDC-NMR is now a local master browser for > >>>>> workgroup MRIRESEARCH on subnet 172.21.21.35 > >>>>> > >>>>> ***** > >>>>> [2012/09/04 10:09:49.731468, 0] > >>>>> nmbd/nmbd_become_lmb.c:395(become_local_master_stage2) > >>>>> ***** > >>>>> > >>>>> Samba name server PDC-NMR is now a local master browser for > >>>>> workgroup MRIRESEARCH on subnet 192.168.0.150 > >>>>> > >>>>> ***** > >>>>> [2012/09/04 10:10:10.732440, 0] > >>>>> nmbd/nmbd_browsesync.c:247(domain_master_node_status_fail) > >>>>> domain_master_node_status_fail: > >>>>> Doing a node status request to the domain master browser > >>>>> for workgroup MRIRESEARCH at IP 132.183.202.95 failed. > >>>>> Cannot sync browser lists. > >>>>> [2012/09/04 10:10:10.732636, 0] > >>>>> nmbd/nmbd_browsesync.c:247(domain_master_node_status_fail) > >>>>> domain_master_node_status_fail: > >>>>> Doing a node status request to the domain master browser > >>>>> for workgroup MRIRESEARCH at IP 132.183.202.95 failed. > >>>>> Cannot sync browser lists. > >>>>> > >>>>> ============================================= > >>>>> > >>>>> Where is it still getting the old IP address? > >>>>> > >>>>> The the clients are all set with > >>>>> > >>>>> remote announce = 172.27.88.81 > >>>>> wins server = 172.27.88.81 > >>>>> security = domain > >>>>> password server = pdc.nmr.mgh.harvard.edu > >>>>> workgroup = MRIRESEARCH > >>>>> > >>>>> The WINS server is run by central IT group of the hospital > >>> and I have > >>>>> no control over it. > >>>>> > >>>>> DNS is properly changed: > >>>>> > >>>>> # host pdc.nmr.mgh.harvard.edu > >>>>> pdc.nmr.mgh.harvard.edu is an alias for > >>> raidsrv01.nmr.mgh.harvard.edu. > >>>>> raidsrv01.nmr.mgh.harvard.edu has address 172.21.21.35 > >>>>> > >>>>> --------------------------------------------------------------- > >>>>> Paul Raines http://help.nmr.mgh.harvard.edu > >>>>> MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging > >>>>> 149 (2301) 13th Street Charlestown, MA 02129 USA > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> The information in this e-mail is intended only for the > person to > >>>>> whom it is addressed. If you believe this e-mail was sent > >>> to you in > >>>>> error and the e-mail contains patient information, please > >>> contact the > >>>>> Partners Compliance HelpLine at > >>>>> http://www.partners.org/complianceline . If the e-mail > was sent to > >>>>> you in error but does not contain patient information, > >>> please contact > >>>>> the sender and properly dispose of the e-mail. > >>>>> > >>>>> -- > >>>>> To unsubscribe from this list go to the following URL > and read the > >>>>> instructions: https://lists.samba.org/mailman/options/samba > >>>>> > >>>> > >>>> > >>>> > >>> > >> > >> > >> > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
