-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Wilson wrote: > Ah excellent ! Thanks for your help Jerry. I came right. > > My only problem is that when a client connects to my > Samba, Samba first attempts to connect to the AD DC on port 445 > to authenticate the user - this times out after some seconds and > then successfully goes through on port 139. Must be something > on the AD DC that is stopping this ? Is there any way I can > try forcing Samba to only use port 139 in thatrequest to the AD DC ? > I've tried 'smb ports = 139' - this of course seems to be only > for the 'server' side of Samba.
If an AD server is rejecting connections on port 445, then something is wrong with the DC. Are you sure it's really an AD DC? Is this perhaps a mixed mode domain with NT4 BDCs? cheers, jerry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD/dyRIR7qMdg1EfYRAvkFAKCKwFjNHOzE3wtVfFT8JMe+1eP6mgCg3Gy/ 3QO/QnqSFXI98fv6XDQUbRo= =UjFn -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
