Re: [Samba] netlogon sometimes works (corrected with smb.confattached)
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 NETLOGON script each and every time (great!), alas, if I log out and log back in, chances are it won't work (not so great), if I persevere, it will eventually work again, for a while. So, even with less load, it occasionally works, though I am perplexed as to why it appears to always work when I reboot my PC, perhaps there is something in windows that it messing up? We run Windows 2000 at the moment and are waiting to launch Windows XP on the poor users in the near future. Jason Walton Nomad Software Ltd 186 Regent Street London W1B 5TN Tel. +44 (20) 7292 2459 Fax. +44 (20) 7292 2401 www.nomadsoft.com Kurt Weiss <[EMAIL PROTECTED]> 31/01/2003 07:00 To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject:Re: [Samba] netlogon sometimes works (corrected with smb.conf attached) 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 deleted the old link. (so onetimes the link was here, next times it missed...) hardware: if u have not the possibility/experience to look at the network packets, so u can test your stability in a simple way: use ping with a big packet size, and u will find out, if there is a problem with your network connection: in windows (stop with ctrl-c): ping -t -l 65000 XXX.XXX.XXX.XXX should look like this: == Ping wird ausgeführt für 192.168.10.1 mit 65000 Bytes Daten: Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit<10ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit<10ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Ping-Statistik für 192.168.10.1: Pakete: Gesendet = 10, Empfangen = 10, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 0ms, Maximum = 16ms, Mittelwert = 12ms == in linux (stop with ctrl-c): mail:~ # ping -fs 65000 XXX.XXX.XXX should look like this: == PING 192.168.10.10 (192.168.10.10) from 192.168.10.1 : 65000(65028) bytes of data. . --- 192.168.10.10 ping statistics --- 458 packets transmitted, 457 received, 0% loss, time 6461ms rtt min/avg/max/mdev = 12.748/12.875/17.226/0.242 ms, pipe 2, ipg/ewma 14.139/12.880ms == i hope it helped... gk -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] netlogon sometimes works (corrected with smb.confattached)
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 deleted the old link. (so onetimes the link was here, next times it missed...) hardware: if u have not the possibility/experience to look at the network packets, so u can test your stability in a simple way: use ping with a big packet size, and u will find out, if there is a problem with your network connection: in windows (stop with ctrl-c): ping -t -l 65000 XXX.XXX.XXX.XXX should look like this: == Ping wird ausgeführt für 192.168.10.1 mit 65000 Bytes Daten: Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=16ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit<10ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit<10ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Antwort von 192.168.10.1: Bytes=65000 Zeit=15ms TTL=255 Ping-Statistik für 192.168.10.1: Pakete: Gesendet = 10, Empfangen = 10, Verloren = 0 (0% Verlust), Ca. Zeitangaben in Millisek.: Minimum = 0ms, Maximum = 16ms, Mittelwert = 12ms == in linux (stop with ctrl-c): mail:~ # ping -fs 65000 XXX.XXX.XXX should look like this: == PING 192.168.10.10 (192.168.10.10) from 192.168.10.1 : 65000(65028) bytes of data. . --- 192.168.10.10 ping statistics --- 458 packets transmitted, 457 received, 0% loss, time 6461ms rtt min/avg/max/mdev = 12.748/12.875/17.226/0.242 ms, pipe 2, ipg/ewma 14.139/12.880ms == i hope it helped... gk [EMAIL PROTECTED] schrieb: 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 perfect (100% record is what I'd expect from a PDC). I suspect it is a problem within samba in terms of how fast it looks at certainincoming network packets, as the password logon works fine every single time, but connecting to the PDC and executing the NETLOGON share are problematic.. Anyway, thanks for your help. Hopefully, a bit more load balancing will get it working 100% of the time. Jason Walton Nomad Software Ltd 186 Regent Street London W1B 5TN Tel. +44 (20) 7292 2459 Fax. +44 (20) 7292 2401 www.nomadsoft.com John H Terpstra <[EMAIL PROTECTED]> 25/01/2003 05:05 To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject:Re: [Samba] netlogon sometimes works (corrected with smb.conf attached) 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 things broke down. If timing is the issue t hen your authentication server may be problematic. In this case you would need to either isolate the problem, or move the authentication (netlogon) service to another machine that is more responsive. - John T. On Wed, 22 Jan 2003 [EMAIL PROTECTED] wrote: 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 either get a successful logon (netlogon script runs) or a plain logon (validates my password, creates my profile share (z drive), but fails to run the netlogon share). Which brings me to ask the question, is the netlogon share affected by network acvtivity? The PDC server is running fileservices, domino, and other items. Password validation isn't a problem, but getting samba to process the netlogon, is a pain. Everything that did run on the NT server has been migrated to the solaris machine and works better and faster than before. The PDC is the last item left, I'm wondering if Samba needs a more dedicated host to invoke netlogon? Domino can be quite intensive on network activity when replicating between sites, so would this network deluge put samba off from the 'less critical' execution of the netlogon share? FYI our NT server
Re: [Samba] netlogon sometimes works (corrected with smb.confattached)
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 perfect (100% record is what I'd expect from a PDC). I suspect it is a problem within samba in terms of how fast it looks at certainincoming network packets, as the password logon works fine every single time, but connecting to the PDC and executing the NETLOGON share are problematic.. Anyway, thanks for your help. Hopefully, a bit more load balancing will get it working 100% of the time. Jason Walton Nomad Software Ltd 186 Regent Street London W1B 5TN Tel. +44 (20) 7292 2459 Fax. +44 (20) 7292 2401 www.nomadsoft.com John H Terpstra <[EMAIL PROTECTED]> 25/01/2003 05:05 To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject:Re: [Samba] netlogon sometimes works (corrected with smb.conf attached) 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 things broke down. If timing is the issue t hen your authentication server may be problematic. In this case you would need to either isolate the problem, or move the authentication (netlogon) service to another machine that is more responsive. - John T. On Wed, 22 Jan 2003 [EMAIL PROTECTED] wrote: > 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 either get a > successful logon (netlogon script runs) or a plain logon (validates my > password, creates my profile share (z drive), but fails to run the > netlogon share). > Which brings me to ask the question, is the netlogon share affected by > network acvtivity? The PDC server is running fileservices, domino, and > other items. Password validation isn't a problem, but getting samba to > process the netlogon, is a pain. > Everything that did run on the NT server has been migrated to the solaris > machine and works better and faster than before. The PDC is the last item > left, I'm wondering if Samba needs a more dedicated host to invoke > netlogon? Domino can be quite intensive on network activity when > replicating between sites, so would this network deluge put samba off from > the 'less critical' execution of the netlogon share? > > FYI our NT server is an old Pentium, 64Mb RAM, 10M network card. > our solaris PDC server is a dual PIII, 1Gb RAM, 100M network card. > > > Jason Walton > Nomad Software Ltd > 186 Regent Street > London W1B 5TN > Tel. +44 (20) 7292 2459 > Fax. +44 (20) 7292 2401 > www.nomadsoft.com > > > > > John H Terpstra <[EMAIL PROTECTED]> > 21/01/2003 03:46 > > > To: [EMAIL PROTECTED] > cc: [EMAIL PROTECTED] > Subject:Re: [Samba] netlogon sometimes works (corrected with smb.conf attached) > > > 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 MS Windows networking perspective, > has been where there has been a jabbering network card or a defective HUB. > > Have you tried replacing the NICs in a client and the server? Have you > tried a cross-over cable between the two to validate that you the network > login process correctly completes EVERY time. If with known working NICs > and a cross-over cable you can reproduce the failure to execute the > network logon process correctly, then it might be time to turn back to > blaming the Samba or MS Windows configuration. > > - John T. > > On Mon, 20 Jan 2003 [EMAIL PROTECTED] wrote: > > > Could anybody please help? I have tried all sorts and nothing will fix > the > > problem permamently. > > I have a samba PDC which on occasion happily logs a user on and > processes > > the NETLOGON share. However, it doesn't always run this service. > > I have placed preexec commands in both the profiles and netlogon shares, > > only the profiles preexec is executed. > > Reboots don't make any difference, only determed logout / logins will > > eventually get the netlogon share executed. > > I have included the full smb.conf file, samba is now running 2.2.7a, > each > > upgrade results in the same problem. > > > > We have two domains, one controlled by an old NT PDC (this is to be > > retired) and one by a new samba PDC (to be the mai
Re: [Samba] netlogon sometimes works (corrected with smb.confattached)
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 either get a successful logon (netlogon script runs) or a plain logon (validates my password, creates my profile share (z drive), but fails to run the netlogon share). Which brings me to ask the question, is the netlogon share affected by network acvtivity? The PDC server is running fileservices, domino, and other items. Password validation isn't a problem, but getting samba to process the netlogon, is a pain. Everything that did run on the NT server has been migrated to the solaris machine and works better and faster than before. The PDC is the last item left, I'm wondering if Samba needs a more dedicated host to invoke netlogon? Domino can be quite intensive on network activity when replicating between sites, so would this network deluge put samba off from the 'less critical' execution of the netlogon share? FYI our NT server is an old Pentium, 64Mb RAM, 10M network card. our solaris PDC server is a dual PIII, 1Gb RAM, 100M network card. Jason Walton Nomad Software Ltd 186 Regent Street London W1B 5TN Tel. +44 (20) 7292 2459 Fax. +44 (20) 7292 2401 www.nomadsoft.com John H Terpstra <[EMAIL PROTECTED]> 21/01/2003 03:46 To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject:Re: [Samba] netlogon sometimes works (corrected with smb.conf attached) 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 MS Windows networking perspective, has been where there has been a jabbering network card or a defective HUB. Have you tried replacing the NICs in a client and the server? Have you tried a cross-over cable between the two to validate that you the network login process correctly completes EVERY time. If with known working NICs and a cross-over cable you can reproduce the failure to execute the network logon process correctly, then it might be time to turn back to blaming the Samba or MS Windows configuration. - John T. On Mon, 20 Jan 2003 [EMAIL PROTECTED] wrote: > Could anybody please help? I have tried all sorts and nothing will fix the > problem permamently. > I have a samba PDC which on occasion happily logs a user on and processes > the NETLOGON share. However, it doesn't always run this service. > I have placed preexec commands in both the profiles and netlogon shares, > only the profiles preexec is executed. > Reboots don't make any difference, only determed logout / logins will > eventually get the netlogon share executed. > I have included the full smb.conf file, samba is now running 2.2.7a, each > upgrade results in the same problem. > > We have two domains, one controlled by an old NT PDC (this is to be > retired) and one by a new samba PDC (to be the main PDC for all machines, > once they are migrated). I have noticed that trying to join the samba > domain over a VPN is impossible, whereas joining the NT domain, works > first time. I don't know if this last bit is relevant to the problem or > not. > > > # This is the main Samba configuration file. You should read the > # smb.conf(5) manual page in order to understand the options listed > # here. Samba has a huge number of configurable options (perhaps too > # many!) most of which are not shown in this example > # > # Any line which starts with a ; (semi-colon) or a # (hash) > # is a comment and is ignored. In this example we will use a # > # for commentry and a ; for parts of the config file that you > # may wish to enable > # > # NOTE: Whenever you modify this file you should run the command > "testparm" > # to check that you have not many any basic syntactic errors. > # > #=== Global Settings > = > [global] > > ## > ## Basic Server Settings > ## > netbios name = PDC > netbios aliases = FILESERVER > # netbios name = PDCM > > # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 > workgroup = NOMAD > # workgroup = PDC1 > > # server string is the equivalent of the NT Description field > server string = Nomad PDC (Samba %v) > #JOWserver string = Samba Server 2.2.6 > > # This option is important for security. It allows you to restrict > # connections to machines which are on your local network. The > # following example restricts access to two C class networks and > # the "loopback" interface. For more examples of the syntax see > # the smb.conf man page > hosts allow = 192.168.2. 192.1
Re: [Samba] netlogon sometimes works (corrected with smb.confattached)
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 things broke down. If timing is the issue t hen your authentication server may be problematic. In this case you would need to either isolate the problem, or move the authentication (netlogon) service to another machine that is more responsive. - John T. On Wed, 22 Jan 2003 [EMAIL PROTECTED] wrote: > 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 either get a > successful logon (netlogon script runs) or a plain logon (validates my > password, creates my profile share (z drive), but fails to run the > netlogon share). > Which brings me to ask the question, is the netlogon share affected by > network acvtivity? The PDC server is running fileservices, domino, and > other items. Password validation isn't a problem, but getting samba to > process the netlogon, is a pain. > Everything that did run on the NT server has been migrated to the solaris > machine and works better and faster than before. The PDC is the last item > left, I'm wondering if Samba needs a more dedicated host to invoke > netlogon? Domino can be quite intensive on network activity when > replicating between sites, so would this network deluge put samba off from > the 'less critical' execution of the netlogon share? > > FYI our NT server is an old Pentium, 64Mb RAM, 10M network card. > our solaris PDC server is a dual PIII, 1Gb RAM, 100M network card. > > > Jason Walton > Nomad Software Ltd > 186 Regent Street > London W1B 5TN > Tel. +44 (20) 7292 2459 > Fax. +44 (20) 7292 2401 > www.nomadsoft.com > > > > > John H Terpstra <[EMAIL PROTECTED]> > 21/01/2003 03:46 > > > To: [EMAIL PROTECTED] > cc: [EMAIL PROTECTED] > Subject:Re: [Samba] netlogon sometimes works (corrected with >smb.conf attached) > > > 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 MS Windows networking perspective, > has been where there has been a jabbering network card or a defective HUB. > > Have you tried replacing the NICs in a client and the server? Have you > tried a cross-over cable between the two to validate that you the network > login process correctly completes EVERY time. If with known working NICs > and a cross-over cable you can reproduce the failure to execute the > network logon process correctly, then it might be time to turn back to > blaming the Samba or MS Windows configuration. > > - John T. > > On Mon, 20 Jan 2003 [EMAIL PROTECTED] wrote: > > > Could anybody please help? I have tried all sorts and nothing will fix > the > > problem permamently. > > I have a samba PDC which on occasion happily logs a user on and > processes > > the NETLOGON share. However, it doesn't always run this service. > > I have placed preexec commands in both the profiles and netlogon shares, > > only the profiles preexec is executed. > > Reboots don't make any difference, only determed logout / logins will > > eventually get the netlogon share executed. > > I have included the full smb.conf file, samba is now running 2.2.7a, > each > > upgrade results in the same problem. > > > > We have two domains, one controlled by an old NT PDC (this is to be > > retired) and one by a new samba PDC (to be the main PDC for all > machines, > > once they are migrated). I have noticed that trying to join the samba > > domain over a VPN is impossible, whereas joining the NT domain, works > > first time. I don't know if this last bit is relevant to the problem or > > not. > > > > > > # This is the main Samba configuration file. You should read the > > # smb.conf(5) manual page in order to understand the options listed > > # here. Samba has a huge number of configurable options (perhaps too > > # many!) most of which are not shown in this example > > # > > # Any line which starts with a ; (semi-colon) or a # (hash) > > # is a comment and is ignored. In this example we will use a # > > # for commentry and a ; for parts of the config file that you > > # may wish to enable > > # > > # NOTE: Whenever you modify this file you should run the command > > "testparm" > > # to check that you have not many any basic syntactic errors. > > # > > #=== Global Settings > > = > > [global] > > > > ## > > ## Basic Server
Re: [Samba] netlogon sometimes works (corrected with smb.confattached)
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 MS Windows networking perspective, has been where there has been a jabbering network card or a defective HUB. Have you tried replacing the NICs in a client and the server? Have you tried a cross-over cable between the two to validate that you the network login process correctly completes EVERY time. If with known working NICs and a cross-over cable you can reproduce the failure to execute the network logon process correctly, then it might be time to turn back to blaming the Samba or MS Windows configuration. - John T. On Mon, 20 Jan 2003 [EMAIL PROTECTED] wrote: > Could anybody please help? I have tried all sorts and nothing will fix the > problem permamently. > I have a samba PDC which on occasion happily logs a user on and processes > the NETLOGON share. However, it doesn't always run this service. > I have placed preexec commands in both the profiles and netlogon shares, > only the profiles preexec is executed. > Reboots don't make any difference, only determed logout / logins will > eventually get the netlogon share executed. > I have included the full smb.conf file, samba is now running 2.2.7a, each > upgrade results in the same problem. > > We have two domains, one controlled by an old NT PDC (this is to be > retired) and one by a new samba PDC (to be the main PDC for all machines, > once they are migrated). I have noticed that trying to join the samba > domain over a VPN is impossible, whereas joining the NT domain, works > first time. I don't know if this last bit is relevant to the problem or > not. > > > # This is the main Samba configuration file. You should read the > # smb.conf(5) manual page in order to understand the options listed > # here. Samba has a huge number of configurable options (perhaps too > # many!) most of which are not shown in this example > # > # Any line which starts with a ; (semi-colon) or a # (hash) > # is a comment and is ignored. In this example we will use a # > # for commentry and a ; for parts of the config file that you > # may wish to enable > # > # NOTE: Whenever you modify this file you should run the command > "testparm" > # to check that you have not many any basic syntactic errors. > # > #=== Global Settings > = > [global] > > ## > ## Basic Server Settings > ## > netbios name = PDC > netbios aliases = FILESERVER > # netbios name = PDCM > > # workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4 > workgroup = NOMAD > # workgroup = PDC1 > > # server string is the equivalent of the NT Description field > server string = Nomad PDC (Samba %v) > #JOWserver string = Samba Server 2.2.6 > > # This option is important for security. It allows you to restrict > # connections to machines which are on your local network. The > # following example restricts access to two C class networks and > # the "loopback" interface. For more examples of the syntax see > # the smb.conf man page > hosts allow = 192.168.2. 192.168.1. 127.0.0.1 > > # Uncomment this if you want a guest account, you must add this to > /etc/passwd > # otherwise the user "nobody" is used > ; guest account = pcguest > > # this tells Samba to use a separate log file for each machine > # that connects > log file = /var/log/samba/log.%m > > # How much information do you want to see in the logs? > # default is only to log critical messages > log level = 1 > > # Put a capping on the size of the log files (in Kb). > max log size = 10250 > > # Security mode. Most people will want user level security. See > # security_level.txt for details. > security = user > # JOW domain admin group = root @wheel > domain admin group = root administrator @sysadm > > # Using the following line enables you to customise your > configuration > # on a per machine basis. The %m gets replaced with the netbios > name > # of the machine that is connecting. > # Note: Consider carefully the location in the configuration file > of > # this line. The included file is read at that point. > ; include = /usr/local/samba/lib/smb.conf.%m > > # Most people will find that this option gives better performance. > # See speed.txt and the manual pages for details > # You may want to add the following on a Linux system: > # SO_RCVBUF=8192 SO_SNDBUF=8192 > ; socket options = TCP_NODELAY > > # Configure Samba to use multiple interfaces > # If you have multip
