You know, the strangest thing happened here.....
One thing I neglected to mention and I bet it was vital information, is that w have 2 samba machines on the network.
we have one as a spare in case the main server dies.
It is sync'd with the main server every 5 minutes with rsync.

I had to turn that backup machine off to do some hardware maintenance, ad it stayed off over the weekend.
This issue disappeared while that machine was turned off.
As soon as I turned this machine on again, the issues started all over again.
It was the same 'cannot contact the domain controller' hiccup.

I shut down the samba daemons and the problem went away.
It would seem to me that something, someplace is misconfigured.

This is what is on the main:

domain logons = Yes
os level = 65
lm announce = Yes
preferred master = Yes
domain master = Yes
wins support = Yes

And, this is what is on the backup:

domain logons = Yes
os level = 35
lm announce = Yes
preferred master = Yes
local master = No
domain master = Yes
wins server = 192.168.0.201


Wins server on the backup is pointing at the main server, not sure that this is completely right either.
My gut tells me it is one of these settings on one of the servers.

So, does anyone have any idea on how I can get the two machines to coexist?
I have no idea why the clients cannot log in randomly and intermittently when both are running.


Louis van Belle wrote:
It's still from the NT4, when these problems occurred.
let me know if it works. you could set the os level to 65 ( that's what im having atm. )

Louis
-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Mark Rutherford
Verzonden: woensdag 29 maart 2006 18:31
Aan: [email protected]
Onderwerp: Re: [Samba] domain controller cannot be contacted

Hi again Louis,

I have in my smb.conf:

domain logons = Yes
os level = 34
lm announce = Yes
preferred master = Yes
domain master = Yes
wins support = Yes

It is the only server. The clients get the ip of this server via dhcp.
I never heard of needing 2 wins server ip addresses, so I'm interested and I just added that to the dhcpd.conf and rehashed it. I am going to try that (is my desperation showing yet? :-D)





Louis van Belle wrote:
If it always happens after a reboot you could try to set the connection timeout lower, somebody correct me if I'm wrong.

I had this problem also, what you also can so let you samba
server act
as wins server, and put the wins ip in you XP configuration.

Als ALWAYS put 2 WINS IP in even if they are the same, this
is because
of strange windows behavor.

Also check if your server is the master browser of the network.
if not, make sure only 1 server and preffered the samba server, the master browser.

Louis

-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Namens Mark Rutherford
Verzonden: woensdag 29 maart 2006 17:44
Aan: [email protected]
Onderwerp: Re: [Samba] domain controller cannot be contacted

Hi Louis,

The reason I would say this is not it, is because it
always happens
on a reboot.
You have not logged in yet... so nothing is running.

However, I will have to read up on this issue a bit. Did
not know it
existed.


Louis van Belle wrote:
You know "User Hive Cleanup Service for XP, if not install it.

http://www.microsoft.com/downloads/details.aspx?familyid=1B286
E6D-8912-4E18-
B570-42470E2F3582&displaylang=en


I experienced problemen with loggin's because some programs badly closes the registry, of a old connection with samba stays open.

Louis
-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Namens Mark Rutherford
Verzonden: woensdag 29 maart 2006 16:45
Aan: [email protected]
Onderwerp: [Samba] domain controller cannot be contacted

Hi everyone,

I have struggled with this problem for awhile now. randomly and intermittently a workstation or bunch of workstations
will not be
able to log in.

This is pretty much reproduceable at will, and here is what you need to do to get this little issue to show up: 1. Log out and try to log in as a different user 2. Attempt to login immediately after the machine is booted.

To ensure you can log in, if you boot your workstation in
the morning
and wait 2-3 minutes before trying to log in you can log in no problem.

I have replaced our switch, cabling, network cards, tried
many many
things......
I took this a step further. I got 3 machines rounded up
and built a
mini network with its own switch.
Only these 3 machines were on this switch.
Of these 3 machines I installed a fresh copy of windows xp
with sp2 on
two of them.
Took our current config and slapped it onto the third
machine running
gentoo + samba

These 3 machines had not been exposed to our main network...
what makes this all so interesting..... I was able to
join these 2
workstations no problem with default settings, no
registry patches,
nothing and it just worked.

I tried to reproduce this problem with this little test
network and
our smb.conf for hours on end.
It just never happened.

On our main network I can get this to occur every 2 minutes if I wanted to. Our samba machine is doing wins as well, and the
machines get this
wins server info with their dhcp info.


Any ideas? Anything at all? This issue is...... just too
hard to me to
figure out.
Also, no indication of an error in any logs.


--
To unsubscribe from this list go to the following URL
and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

--
Thanks!

Mark Rutherford
Maunz Electronics, Inc.
803-791-5860

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

--
Thanks!

Mark Rutherford
Maunz Electronics, Inc.
803-791-5860

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba




--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to