samba - Sep 2003 - samba3: need to wait 3 minutes before login

Hi,

at our local computer pool in the school we've a samba3
server and about 40 winnt-4.0 workstations. the main
problem is, that the workstations have to wait for
about 3 minutes after they started, before a user can
login. in other words: the computer starts and if you
try to login then immediatly you'll get "domain manos
not available" or something like this. but if you wait
approximatly 3 minutes you are able to login successfully.

does anyone know about this problem and how we could solve
it ?

thank you,

livius

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Do you have WINS enabled on the server, with the clients setup to ask it
for the Domain?

3 minutes sounds like the time it takes for a domain master browser
election to take place.

Livius Penter wrote:
| Hi,
|
| at our local computer pool in the school we've a samba3
| server and about 40 winnt-4.0 workstations. the main
| problem is, that the workstations have to wait for
| about 3 minutes after they started, before a user can
| login. in other words: the computer starts and if you
| try to login then immediatly you'll get "domain manos
| not available" or something like this. but if you wait
| approximatly 3 minutes you are able to login successfully.
|
| does anyone know about this problem and how we could solve
| it ?
|
| thank you,
|
| livius
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/XbB8RliD/69byygRAk+aAJ9NBuW2JYwDV4KzlEIP88pirywCCwCcCPAc
emMYLQztPEuAvVw0sFXUpQs=o3be
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 9 Sep 2003, Livius Penter wrote:
> Hi,
> 
> at our local computer pool in the school we've a samba3
> server and about 40 winnt-4.0 workstations. the main
> problem is, that the workstations have to wait for
> about 3 minutes after they started, before a user can
> login. in other words: the computer starts and if you
> try to login then immediatly you'll get "domain manos
> not available" or something like this. but if you wait
> approximatly 3 minutes you are able to login successfully.
> 
> does anyone know about this problem and how we could solve
> it ?
Sounds like a name resolution timeout issues.  Get a network trace
and see what the client is doing.  



cheers, jerry
 ----------------------------------------------------------------------
 Hewlett-Packard            ------------------------- http://www.hp.com
 SAMBA Team                 ---------------------- http://www.samba.org
 GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
 "You can never go home again, Oatman, but I guess you can shop
there."
                            --John Cusack - "Grosse Point Blank"
(1997)


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD4DBQE/XhEzIR7qMdg1EfYRAjViAJ9fYm0aVa8aVCAm6eDgCThqu8Wm4wCTBVn6
q9PUxyMQURLmRQwPwvU8Ww==7e8h
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Run ipconfig (windows nt, 2k,etc) or winipcfg (win 9x) from a command
window and see if it gives you a "WINS SERVER" ip address.

If it doesn't, look in the network settings and change the wins server
from "Allocate WINS through DHCP" (or something like that) to the IP
address of your Linux/Samba/Wins machine.

You can try nmblookup //linuxmachinenetbiosname to see if Samba knows
what's going on.

- -Tom

Livius Penter wrote:
|>Do you have WINS enabled on the server, with the clients setup to ask it
|>for the Domain?
|>
|>3 minutes sounds like the time it takes for a domain master browser
|>election to take place.
|>
|
|
| We did enable the wins support. Could this be a bug in the wins
| server? Someone suggested it could be because of the dhcpd we
| use. Is it the dhcp?
|
| thank you,
|
| livius
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/XlPPRliD/69byygRAs5yAJ9TwEvTP+u8KfdDN1RTR0rRs/nkoQCbBnbj
W9jgkD68aMqOw7ZsErajG5o=m5Uu
-----END PGP SIGNATURE-----