Russ was right. After waiting for the secstore to time out and booting the terminal, a snoopy on the server shows the AR tcp packets BUT a snoopy on the client does not!.
I don't know if it is qemu, windows firewall or the antivirus firewall. Windows firewall is not running and the antivirus firewall log do not show anything regarding this :( It seems I will have to install the secstore server after all :) On 2007-01-10 19:51, Alberto Cortés wrote: > Damn, my terminal is running on a qemu!, this can be the problem. > > Sorry for the private reply before. > > On 2007-01-10 13:43, Russ Cox wrote: > > It sounds like the server is doing the right thing > > but that the flags=AR packets are not getting > > back to the client. > > Are they on the same network or is there some > > kind of nat box inbetween? > > > > Russ > > > > > > On 1/10/07, Alberto Cortés <[EMAIL PROTECTED]> wrote: > > >On 2007-01-10 13:15, Russ Cox wrote: > > >> >I have a cpu/auth/fs server and a terminal. > > >> > > > >> >The terminal is booting with the server as auth and fs. > > >> > > > >> >When booting the terminal: > > >> > > > >> >- I am asked for a user name. > > >> >- 6 minutes waiting for the next prompt > > >> >- factotum ask me about my username and password for the fs > > >> > domain with proto p9sk1 > > >> >- I get a nice, working terminal > > >> > > > >> > > > >> >A snoopy running on the server during those 6 minutes of waiting > > >> >show some tcp traffic from the client to the server at the > > >> >secstore port. > > >> > > > >> >My server is not a secstore server. > > >> > > > >> >How can I tell factotum not to connect to my (nonexistent) > > >> >secstore server? > > >> > > > >> >I would like to do without a secstore server until I learn > > >> >something about it :). > > >> > > >> If you are not running secstore, then a connect to that > > >> port (5356) should just fail immediately. It sounds like something > > >> else is silently dropping the tcp connect packets or not > > >> letting the rejections come back. > > >> > > >> Russ > > > > > >"netstat -n" on the server do not show anything on port 5356. > > > > > >The "snoopy" dump is something like this (sorry I can't copy > > >& paste, I write the relevant info, ask for more if something is > > >missing): > > > > > >client -> server: source_port=XXXX dest_port=5356 tcp_flags=S > > >server -> client: source_port=5356 dest_port=XXXX tcp_flags=AR > > >client -> server: source_port=XXXX dest_port=5356 tcp_flags=S > > >server -> client: source_port=5356 dest_port=XXXX tcp_flags=AR > > >client -> server: source_port=XXXX dest_port=5356 tcp_flags=S > > >server -> client: source_port=5356 dest_port=XXXX tcp_flags=AR > > > > > >2 minutes of waiting... > > > > > >the same 3 tcp tries as before with other source_port > > > > > >2 minutes of waiting... > > > > > >the same 3 tcp tries as before with other source_port > > > > > >2 minutes of waiting... > > > > > >the same 3 tcp tries as before with other source_port > > > > > >secstore give up... 564 traffic here... > > > > > >-- > > > http://bach.gast.it.uc3m.es/~alcortes/index.html > > > > > > > > > > -- > http://bach.gast.it.uc3m.es/~alcortes/index.html > -- http://bach.gast.it.uc3m.es/~alcortes/index.html
