Hi Kurt,
thanks for that.
Our ping times are faster than that, I have now created the server without
any extra software running (we were running domino on the box as well), so
now it is purely a fileserver, running backup DNS, DHCP, NIS, NTP.
If I turn my PC off, and log on it executes the
John,
I have no success with packet sniffing, the netlogon share either works or
it doesn't.
Our boxes are not overly loaded, but I took your advice and tinkered with
the loading.
Over the passed week, it gets the netlogon share executed more times than
not (at the moment) but it still isn't
hello jason,
we are using successful netlogon over years. - at first we had similar
problems. the reason lied in the batch file:
1) the batch was written on linux, so the CR was missing at the end of
the line...
2) we used net use without the /y flag - windows did not rebind the
drive, but
John,
thanks for your help thus far.
I switched switches that the PDC is plugged into and it almost had me
believing that it worked, I managed to log in three times in quick
succession and each time it executed the netlogon script.
Alas, inconsistency reared its ugly head once more and now I
Jason,
Apologies for the dealy, I was at LinuxWorld Expo New York all week and
just got home.
You should use a network sniffer (like Ethereal) to capture a trace of a
logon that works correctly and one that does not. Then examine the
differences to find what went wrong. It should tell you where
Jason,
We have gone over a few things already. You are using WINS, that means
your MS Windows clients should not have any trouble finding your samba
server and the services that run on it.
The only time I have seen similar behaviour, given that everything is
correctly configured from a Samba and
