Fedora Users — Re: Network resources evaporate on FC3 within 30 minutes of a reboot

Craig White wrote:

On Fri, 2004-12-10 at 21:48 -0500, A. Rick Anderson wrote:

	wins proxy = Yes

---
? set this to no
---

	wins support = Yes

---
Good - do the Windows computers also point to this wins server?
---

	idmap uid = 16777216-33554431
	idmap gid = 16777216-33554431

---
are you using winbind? I don't understand here. If you are using winbind
(have another PDC then this shouldn't be a domain master/preferred
master) - another thing - though I think that you should make sure that
winbind isn't running and thus, these idmaps don't make sense to me is
that if you do use winbind, you shouldn't use nscd daemon, which might
explain things. In a setup that I think you are using - 1 Linux box as
PDC for Windows domain. winbind should be off, idmaps should be off,
wins support should be on, all windows systems should point to this
system by ip address as it's wins server and nscd is helpful.
---

	guest ok = Yes

---
not sure about this but
security = user
would be a very good thing
---

	printing = lprng
	print command = lpr -r -P'%p' %s
	lpq command = lpq -P'%p'
	lprm command = lprm -P'%p' %j
	lppause command = lpc hold '%p' %j
	lpresume command = lpc release '%p' %j
	queuepause command = lpc stop '%p'
	queueresume command = lpc start '%p'

----
not sure why you aren't using cups - it's so much easier

Craig

I believe that the idmap entrys came from SWAT or one of the GUI tools originally, as did all of the printing stuff. I haven't dug into getting printers to work yet. That is my next project, after getting the current network issues resolved. [the point being, the idmap and printer entries were not entered in the smb.conf file by design or deliberate intent.]

This box is, as you say, a linux box as the PDC, DHCP and DNS for a Win2k environment. The DHCP settings are attached, but when I was setting them up (a while back), it was my intent to point to the linux box as the wins server. I have a DirecWay 6000 modem, which includes a built-in DHCP server that can't be disabled. The modem also commandeers the 192.168.0.1 address, so my Linux box is 192.168.0.2. When I check my win2k machines via ipconfig /all, they are getting configured by the dhcpd.conf file on the linux server, so I don't think the modem and my linux box are conflicting.

A check on process that were running showed that there were 2 winbindd processes running, one whose parent was 1. There was/is no ncsd process running. I turned off winbind, made the switch on "wins proxy = no", and commented out all the printer stuff and the idmaps. However, it is worth noting that winbind was running on FC2 without a noticeable problem. I've got winbindd.log files dating from before I upgraded to FC3. The only complaint, which is consistent in all versions of the winbindd.log files are that the user "root", "cyrus" and "mailman" don't exist.

A check on nsswitch.conf shows that it expects to use winbind as the secondary on most of the services.

Those changes to the smb.conf file seem to have done the fix. I've been running a test on the net view of my printer server and it has been running for at least ten or fifteen minutes longer then any time since I upgraded. Craig, your advice seems to have been right on the money. Thanks folks for the insights.

I wonder why FC3 would be pickier about winbind running then FC2 was?

-- 
A. Rick Anderson

default-lease-time 28800;
max-lease-time 86400;
option subnet-mask 255.255.255.0;
option routers 192.168.0.1;
option domain-name-servers 192.168.0.2, 198.77.116.8;
option netbios-name-servers 192.168.0.2, 192.168.0.1; 
option broadcast-address 192.168.0.255;
option domain-name "galarik.org";

ddns-update-style interim;

subnet 192.168.0.0 netmask 255.255.0.0 {
	range 192.168.0.1 192.168.0.250;
	host Illuvatar {
		hardware ethernet 00:0C:76:B2:A3:32;
		fixed-address 192.168.0.100;
	}
	host Sauron {
		hardware ethernet 00:01:02:85:EC:D0;
		fixed-address 192.168.0.101;
	}
	host Bilbo {
		hardware ethernet 00:07:95:D5:FC:08;
		fixed-address 192.168.0.102;
	}
	host Frodo {
		hardware ethernet 00:0A:E6:7C:CE:85;
		fixed-address 192.168.0.103;
	}
	host Thorin {
		hardware ethernet 00:60:67:2C:9E:17;
		fixed-address 192.168.0.104;
	}
	host Eru {
		hardware ethernet 00:0F:1F:22:A4:91;
		fixed-address 192.168.0.15;
	}
	host Balin {
		hardware ethernet 00:20:35:DE:55:E4;
		fixed-address 192.168.0.16;
	}
	host Gimli {
		hardware ethernet 00:20:35:DE:55:D4;
		fixed-address 192.168.0.17;
	}
	host Samwise {
		hardware ethernet 00:50:04:FC:ED:0F;
		fixed-address 192.168.0.18;
	}
	host Ori {
		hardware ethernet 00:08:AD:B4:9C:57;
		fixed-address 192.168.0.20;
	}
	host Ainu {
		hardware ethernet 00:09:6B:86:FF:2B;
		fixed-address 192.168.0.21;
	}
	host Aman {
		hardware ethernet 44:45:53:54:42:00;
		fixed-address 192.168.0.23;
	}
}