Strange Automount Behaviour

Hello everybody,

since i'm using the automounter of suse 10.3, i'm confronted with a very strange behaviour. I use it to mount user directories over nfs. The automounter maps are provided by NIS. The configuration of NIS ant automount i use worked propperly since suse 6.3 until suse 10.2. Now i encounter the following missbehaviour:
During the boot, automounter seems to start propperly, but if someone logins over the network into the client machine, the automounter ignores all mount requests. Even a 'rcautofs restart' changes nothing. But if someone logins on the client machine over the tty, everything works fine. Thatfor i started the automounter with debug mode verbosity, this is the output from /var/log/messages:

after "rcautomount start" or "rcautomount restart":
Jun 2 21:11:22 node061 automount[1910]: Starting automounter version 5.0.2, master map auto.master
Jun 2 21:11:22 node061 automount[1910]: using kernel protocol version 5.00
Jun 2 21:11:22 node061 automount[1910]: lookup_nss_read_master: reading master nis auto.master
Jun 2 21:11:22 node061 automount[1910]: lookup_init: lookup(yp): ctxt->mapname=auto.master
Jun 2 21:11:22 node061 automount[1910]: parse_init: parse(sun): init gathered global options: (null)
Jun 2 21:11:22 node061 automount[1910]: mount_init: mount(bind): bind_works = 1

after login per tty:
Jun 2 21:17:07 node061 automount[1910]: master_do_mount: mounting /users
Jun 2 21:17:07 node061 automount[1910]: lookup_nss_read_map: reading map yp auto.users
Jun 2 21:17:07 node061 automount[1910]: lookup_init: lookup(yp): ctxt->mapname=auto.users
Jun 2 21:17:07 node061 automount[1910]: parse_init: parse(sun): init gathered global options: (null)
Jun 2 21:17:07 node061 automount[1910]: mount_init: mount(bind): bind_works = 1
Jun 2 21:17:07 node061 automount[1910]: mounted indirect mount on /users with timeout 600, freq 150 seconds
Jun 2 21:17:07 node061 automount[1910]: ghosting enabled

It seems, that a login through tty sends an wake up event to the automount deamon, because all remote logins are ignored. This behaviour seems also to be independent of all different automounter and NIS configurations or options. I have tried a lot of different automounter configarations without any effect on this strange behaviour.

Any idea?