Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225112 - wins server wins.dat fails to get updated on IP address change
Summary: wins server wins.dat fails to get updated on IP address change
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: David Lawrence
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-29 01:01 UTC by das_deniz
Modified: 2008-05-06 19:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:07:03 UTC

Attachments (Terms of Use)

Description das_deniz 2007-01-29 01:01:28 UTC
Description of problem:

setup is linux only home network with one box having 'wins support = yes' and
several clients pointing to it's IP - all have 'hosts: files wins dns' in their

recently had to reset the flash for the router/DHCP server and one client got a
new IP address.  after which no other client could ping it by name EVEN AFTER

nmblookup was able to resolve the name to the new IP.

finally removing /var/cache/samba/wins.* and restarting smb on the wins server
and everything is fine. (this wasn't so easy to find - so i hope this has a nice
fix :)

Version-Release number of selected component (if applicable):


How reproducible:

well - do i have to go thru that again... i've reserved all the DHCP IPs

Steps to Reproduce:
1. small network with wins name resolution for them (w/o dns or any other for them)
2. change a client ip and restart it (reboot or restart networking)
3. try to have other clients ping it by name...
Actual results:

they won't be able to

Expected results:

they should be able to

Additional info:

my server is my mythbox... don't make me boot it to many times to test fixes :)

Comment 1 das_deniz 2007-01-29 14:13:00 UTC
Just a quick correction to the "AFTER REBOOTING ALL DEVICES" - I only rebooted
the clients - the wins server / mythbox did not get poked in the eye (but you
probably already knew that from the /var/cache bit...)

Comment 2 Bug Zapper 2008-04-04 05:46:40 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 3 Bug Zapper 2008-05-06 19:07:01 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.